On This Page

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
.

Stabilization Period

For the first two weeks after you migrate from legacy Recurring Billing to the new Recurring Billing, these Recurring Billing functions are limited:

Creating a Subscription with a New Customer Flow Using the
Business Center

During the payment synchronization period, you cannot use the new customer flow.
To create a subscription for a new customer (without saved payment information), use the
Token Management Service
 interface in the
Cybersource
Business Center
.
Follow these steps to create a customer token in the
Business Center
:
  1. On the left navigation panel, click
    Token Management
    .
  2. Click
    Tokens
    . The Tokens page appears.
  3. Click
    New Profile
    .
  4. Enter the
    Merchant Reference Number
    ,
    Payment
    , and
    Shipping Address
     details.
  5. You can leave the
    Profile Information
     field blank for the system to perform a zero authorization. Alternatively, enter your own
    Amount and Set Up Fee
    .
  6. Click
    Save
    .
  7. A message at the top of the screen confirms that the profile is created and migration is in progress. The token is being added to TMS, so wait a moment.
  8. The screen refreshes, and you see the details of the new token you just created.
Use the existing customer flow with the token you just created. For more information, see Creating a Subscription with an Existing Customer Token section in the
Recurring Billing User Guide
.
Follow these steps to apply the token to an existing customer in the
Business Center
:
  1. On the left navigation panel, click
    Recurring Billing
    .
  2. Click
    Manage Subscriptions
    . The Manage Subscription page appears.
  3. Click
    Create Subscription
    .
  4. Select
    Existing Customer
    , and then click
    Continue
    .
  5. Enter the customer's first and last name to find the token you just created.
After this period (two weeks after your migration complete date), you can leverage all features within the
Business Center
 to create subscriptions. For more information, see Creating a Subscription with a New Customer Token in the
Recurring Billing User Guide
.

Subscription Name Changes

For improved security, additional restrictions or validations may be applied to legacy subscription names. If a legacy subscription name contains special characters not permitted by the new service, the migration process replaces those characters with a dash ('
-
'), which is allowed.
For example, any underscore ('
_
') in a legacy subscription name is replaced with a dash ('
-
').
When filtering and searching for subscription names, remember that legacy subscription names may have been modified during the migration to the new Recurring Billing.
These characters are allowed:
  • Lowercase letters: a-z
  • Uppercase letters: A-Z
  • Digits: 0-9
  • Special characters: ? . , $ / @ & ! : -
  • Space
These characters are restricted:
  • Special Characters:
    • #
       (hash)
    • %
       (percent)
    • ^
       (caret)
    • *
       (asterisk)
    • (
       (left parenthesis)
    • )
       (right parenthesis)
    • _
       (underscore)
    • +
       (plus)
    • =
       (equals)
    • {
       (left curly brace)
    • }
       (right curly brace)
    • [
       (left square bracket)
    • ]
       (right square bracket)
    • |
       (vertical bar)
    • \
       (backslash)
    • ;
       (semicolon)
    • '
       (single quote)
    • "
       (double quote)
    • <
       (less than)
    • >
       (greater than)
    • ~
       (tilde)
    • `
       (backtick)
  • Non-ASCII Characters:
    • é
       (accented e)
    • ç
       (cedilla)
    • ü
       (umlaut u)
    • ñ
       (tilde n)
    • Ω
       (Greek Omega)
    • Emojis:
    • 😊 (smiling face)
    • 🚀 (rocket)
    • 💡 (light bulb)
    • Control Characters:
    • \t
       (tab)
    • \n
       (newline)
    • \r
       (carriage return)