API Overview

Recurring Billing Upgrade Guide
- Recent Revisions to This Document

Introduction to Upgrading the Recurring Billing Service
- Recurring Billing Upgrade and Migration Overview
- Upgraded Recurring Billing
  - Plans
  - Subscriptions
- Legacy and Upgraded Recurring Billing Feature Comparison
- Legacy and Upgraded Business Center and API Service Feature Comparison
- Legacy and Upgraded Business Center and API Service Action Comparison
- Comparison of Business Center UI Sections and API Fields
- Upgraded Report Fields

Migration Activities
- Preparation
- Prerequisites
- Timeline
- Test Checklist Recommendations
- Updating Your Processes and Order Management System
  - Business Center User Interface
  - Business Center Virtual Terminal
  - Business Center Transaction Management
  - SCMP API and Simple Order API
  - Secure Acceptance Hosted Checkout Integration and Checkout API
  - Aura and Cold Fusion

Post-Migration Information
- Creating a Subscription Using the API
- Customer Notifications
- Migrated Subscription Payment History
- Subscription Details
- Stabilization Period
  - Creating a Subscription with a New Customer Flow Using the Business Center
  - Subscription Name Changes
  - Business Center Permissions

VISA Platform Connect: Specifications and Conditions for Resellers/Partners

On This Page

Preparation

Cybersource will inform you about migration timelines and expectations.

Cybersource will migrate all legacy Recurring Billing tokens to TMS.

Only active subscriptions will migrate to the upgraded Recurring Billing service. Canceled, On hold, and Completed subscriptions will not migrate. Cybersource will provide access to those subscriptions through the Business Center, the REST API, and TMS.

Cybersource offers training for the migration to the upgraded Recurring Billing.

After migrating to the new Recurring Billing platform, you cannot access historical data about the legacy subscriptions.

When migration begins, your current integration will fail. Prepare changes on your site in advance. Before migration, create customer tokens. After migration, create subscriptions associated with the tokens.

Back to top