API Overview

Recurring Billing Developer Guide
- Recent Revisions to This Document

Introduction to Recurring Billing
- Prerequisites
- Account Validation (Pre-Authorization)

Subscriptions
- Subscription Prerequisites
- Subscription Statuses
- Zero Amount Authorizations
- Assigning a Subscription Code
- Subscription ID
- Overriding a Plan
- Creating a Subscription
  - Required Fields for Creating a Subscription
  - Optional Fields for Creating a Subscription
  - REST Examples: Creating a Subscription
- Retrieving a List of Subscriptions
  - REST Examples: Retrieving a List of Subscriptions
- Retrieving a Subscription
  - REST Examples: Retrieving a Subscription
- Retrieving the Next Subscription Code
  - REST Examples: Retrieving the Next Subscription Code
- Amending a Subscription
  - REST Examples: Amending a Subscription
- Re-activating a Suspended Subscription
  - REST Examples: Reactivating a Suspended Subscription
- Suspending a Subscription
  - REST Examples: Suspending a Subscription
- Cancelling a Subscription
  - REST Examples: Canceling a Subscription

Additional Features
- System Retry Logic
- Customer Notifications
- Decision Manager Integration

VISA Platform Connect: Specifications and Conditions for Resellers/Partners

On This Page

Introduction to Recurring Billing

The Recurring Billing service enables you to 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:

Token
: stores customer billing, shipping, and payment details.

Plan
: stores the billing schedule.

Subscription
: combines the token and plan and defines the subscription start date, name, and description.

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.

Back to top