API Overview

Recurring Billing Subscription Data Migration Guide
- Recent Revisions to This Document
- VISA Platform Connect: Specifications and Conditions for Resellers/Partners

Introduction to Migrating Subscription Data to Cybersource Recurring Billing
- Migration Flow
- Migration Limitations
- Migration Prerequisites

Task 1: Enable Recurring Billing in Your Cybersource Account

Task 2: Integrate with the Cybersource API

Task 3: Export Current Subscriptions to a File

Task 4: Create New Subscriptions
- Requirements for the Subscription Creation Script
- Additional Fields Required for Card Subscriptions
  - Additional API Field Required for Any Credit or Debit Card Subscription
  - Additional API Field Required for a Diners or Discover Card
- Obtaining Additional Values Required for Card Subscriptions
  - Retrieve Original Subscription Data from the Cybersource TMS
  - Retrieve Original Subscription Data from the Original Provider
  - When Original Subscription Data Cannot Be Retrieved
- Construct Your Subscription Creation Script

Task 5: Validate the New Subscriptions in the Cybersource System
- Use the Business Center to Validate Migrated Subscriptions
- Use the REST API to Validate Migrated Subscriptions

Finalize the Migration

Reference Information
- Using the Interactive REST API Reference
  - Build a Request to Create a Recurring Billing Plan
  - Build a Request to Create a Recurring Billing Subscription
- Creating a Subscription with a One-Time Plan
  - Required and Optional Fields
  - REST Example: Create a Subscription with a One-Time Plan
- Creating a Subscription with an Existing Plan
  - Required and Optional Fields
  - REST Example: Create a Subscription with an Existing Plan
- Creating a Subscription with Plan Overrides
  - Required and Optional Fields
  - REST Example: Create a Subscription with Plan Overrides

On This Page

Additional API Field Required for Any Credit or Debit Card Subscription

If the subscription is for a credit or debit card, the subscription creation request must include the network transaction ID
of the transaction that originally initialized the subscription (and allowed for the storage of payment information).

Include the network transaction ID in this field of the subscription creation request message:

subscriptionInformation. originalTransactionId

For information about obtaining the network transaction ID, see Obtaining Additional Values Required for Card Subscriptions.

Continue to use this network transaction ID to uniquely identify future automatic payments for this subscription.

IMPORTANT

Including the network transaction ID in the subscription creation request obtains the payer's consent for you to make automatic (recurring) payments with the new subscription in the

Cybersource

system.

Back to top