On This Page

Introduction to Recurring Billing

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
the
Token Management Service
 (
TMS
)
.
National Australia Bank
 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.
For Information about Recurring Billing in the
Gateway Portal
, see the
Recurring Billing User Guide
.
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
Token Management Service
 (
TMS
)
. The customer token is the only token type that can be used with Recurring Billing.
For more information about
TMS
, see the
Token Management Service
 REST API Developer Guide
.

Getting Started with the REST API

If you have not already, you must register and obtain authentication credentials for the REST API.
See the Hello world sandbox in the
National Australia Bank
 Gateway Portal.
When your system is REST compliant, you can test your Recurring Billing integration by sending requests to the
National Australia Bank
 test server.