Post-Migration Information

This section describes changes to how you use the new Recurring Billing service as compared to how you used the legacy system.

Creating a Subscription using the API

To create a subscription, you need a customer token. For more details, see to the
Cybersource
 API Developer Center Create a Subscription to create a test example API request.
After migration, a customer token is created in TMS for each active subscription in the legacy system. This token has the same ID as the subscription. You can use this token to create another subscription for the same customer.
To create a subscription for a new customer, you must generate a new customer token.
When capturing payment card data for future use, validate the payment card account by:
  • Using a payment for a zero amount, or
  • If your processor does not support zero amount, using a minimal amount.
Enable the Data Enrichment for Card Verification feature to automatically choose the minimal auth amount. Contact Customer Support for more details.
The best way to perform this transaction is via the REST API. For more information, see the Create a Customer Token with Validated Payment Details section in the
Token Management Service
 Developer Guide
.
If using Secure Acceptance Checkout or SCMP/SOAP API to create tokens, follow these steps:
  1. Change the request field
    recurring_frequency
     value to
    on-demand
    .
  2. Remove any other subscription-related fields (
    recurring_*
    ) from the request.
Your current integration will fail once migration starts. Prepare changes on your site in advance. Before migration, create tokens as described above. After migration, create subscriptions for them.
To create a subscription, use this data from the payment response:
Customer ID:
  • Payments REST API:
    tokenInformation.customer.id
  • Secure Acceptance Checkout:
    payment_token
  • SCMP API:
    pay_subscription_create_subscription_id
  • SOAP API:
    paySubscriptionCreateReply_subscriptionID
Original Transaction ID:
  • Payments REST API:
    processorInformation.networkTransactionId
  • Secure Acceptance Checkout:
    payment_network_transaction_id
  • SCMP API:
    auth_payment_network_transaction_id
  • SOAP API:
    ccAuthReply_paymentNetworkTransactionID
Original Transaction Authorized Amount:
 (Required only for Diners and Discover cards)
  • Payments REST API:
    orderInformation.amountDetails.authorizedAmount
  • Secure Acceptance Checkout:
    auth_amount
  • SCMP API:
    auth_auth_amount
  • SOAP API:
    ccAuthReply_amount
For more details on creating a subscription, see to the Create a Subscription section in the
Recurring Billing User Guide
.