Secure Acceptance

Hosted Checkout Integration

and

Checkout API

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
Business Center
.
Contact
Cybersource
client services to start the migration.