You must update your processes and order management system in order to upgrade to the new
Recurring Billing service.
Merchants are divided into six groups (action cohorts) according to the legacy Recurring
Billing integration method. Each of the six groups has its own set of upgrade steps:
Recurring Billing service to create and maintain
subscriptions, you can continue to do so after your existing subscription tokens are
migrated to the upgraded Recurring Billing and
TMS
in the
Business Center
. No API integration updates are required.
Follow these steps to prepare for your upgrade:
Become familiar with the new Recurring Billing service user interface in the
Business Center
.
Contact
Cybersource
client services to start the migration.
This image shows the upgraded Recurring Billing user interface for creating a new
subscription or maintaining an existing subscription.
If you use the Virtual Terminal to create tokens during one-time payments and to
create and maintain subscriptions, you can continue to do so after your existing
subscription tokens are migrated to the upgraded Recurring Billing service and
TMS
in the
Business Center
. No API integration updates are required.
Follow these steps to prepare for the migration:
Become familiar with the new Recurring Billing service user interface in the
Business Center
.
Become familiar with the new Recurring Billing two-step process for creating
subscriptions.
Transaction Management to create subscriptions,
select Action and then Create Subscription on the Transaction Details screen. The
system will direct you to the new Recurring Billing service user interface in the
Business Center
.
Follow these steps to prepare for the migration:
Become familiar with the new Recurring Billing service user interface in the
Business Center
.
Contact
Cybersource
client services to start the
migration.
This image shows the upgraded Recurring Billing user interface for creating a new
subscription or maintaining an existing subscription.
Figure:
Example Upgraded Manage Subscription User Interface
If you use the SCMP API or Simple Order API to create and manage
subscriptions, you must migrate to the Recurring Billing service that uses the REST
API.
After your existing
subscription tokens are migrated to the upgraded Recurring Billing and
TMS
in the
Business Center
, you can create and manage
subscriptions there.
Follow these steps to prepare for the migration:
Integrate to the new Recurring Billing service that uses the REST API.
Become familiar with the new Recurring Billing service user interface in the
After migration, you can no longer create subscriptions
using
Hosted Checkout Integration
or
Checkout API
. You must migrate
to these services in this order:
Unified Checkout, to collect customer information.
TMS
that uses the REST API, to create customer tokens
from transient tokens.
Recurring Billing service that uses the REST API.
During the transitional phase, you can still use the system to validate and create a
payment token. This process will replace the previous steps 1 and 2. To create a token
in this way, change the
recurring_frequency
request field value to
on-demand
. Also, remove any other subscription-related fields
(
recurring_*
) from the request.
After your existing subscription tokens are migrated to
the upgraded Recurring Billing service and
TMS
in the
Business Center
, you can create and manage subscriptions there.
Follow these steps to prepare for the migration:
Integrate to Unified Checkout to collect the payment instrument.
Integrate to Payments REST API to create the Customer Token from the Transient
Token.
Integrate to the new Recurring Billing service that uses the REST API.
Become familiar with the new Recurring Billing service user interface in the
