On This Page

{#jumplink-list}  
[Markdown](/docs/vas/en-us/recurring-billing/developer/all/rest/recurring-billing-dev/recur-bill-dev-intro.md)  
Filter  
FILTER BY TAG

Introduction to Recurring Billing {#recur-bill-dev-intro}
=========================================================

This guide explains how to integrate to the Recurring Billing REST API.  
The Recurring Billing service enables you to create and manage payment plans and subscriptions for recurring payment schedules. It automates the storage and handling of your customer's payment information and personal data within secure Visa data centers in compliance with credentials-on-file (COF) best practices. Storage risks and the PCI DSS scope are reduced through the use of .  
`Visa Acceptance Solutions` Recurring Billing consists of these three elements:

* **Plan:** Stores the billing schedule.
* **Subscription:** Combines the token and plan and defines the subscription start date, name, and description.
* **Token:** Stores customer billing, shipping, and payment details.

> IMPORTANT Do not use this document if you are using the payments API to process recurring payments. When using payments API for MITs, you must capture and store the customer's payment credentials manually. Also, you send the payments API MIT requests to different endpoints than you send the recurring billing requests.

Prerequisites
-------------

Your account must be enabled for Recurring Billing and configured for . The customer token is the only token type that can be used with Recurring Billing.  
RELATED TO THIS PAGE