Introduction

Use this article to migrate from Secure Storage to Token Management Service (TMS). Token Management Service (TMS) helps you manage payment tokens with new features, token formats, and improved controls. This article supports you if you use Secure Storage or Recurring Billing on demand and want to move to TMS.

Understanding Token Management Service

Token Management Service (TMS) is a tokenization platform that improves payment security and token management. TMS offers new token types, more integration options, and centralized token storage.

Completing the Migration Process

Contact your Cybersource or Visa representative to start the migration. Provide your Merchant Identification Number (MID) and confirm eligibility. Not all Merchant Identification Numbers (MIDs) are eligible for immediate migration. Eligibility depends on your current Secure Storage use, technical compatibility, and compliance with TMS requirements.

Cybersource or Visa will determine the migration timeframe based on your complexity, transaction volume, and readiness. Allow time for testing and validation. You can cancel a migration request before migration begins, following Cybersource or Visa policies.

Comparing Token Formats and Types

Token Management Service (TMS) supports new token types. Some Secure Storage token formats are not supported in TMS.

Using Token Sharing and Vault

Token Management Service (TMS) offers improved token sharing and a centralized vault for secure token storage. Some Secure Storage token sharing formats are not supported in TMS.

Integrating with Token Management Service

Review your current integration. Update your Application Programming Interface (API) calls to use Token Management Service (TMS) endpoints and request or response formats. Test token creation, lookup, update, and deletion. Update your systems to process new response fields from TMS.

Best Practices

• Engage your technology and compliance teams early.
• Test your migration end-to-end before using Token Management Service (TMS) in production.
• Identify and address unsupported token formats or sharing mechanisms.
• Train stakeholders on new processes and features.
• Keep migration records for compliance and future reference.

Frequently Asked Questions (FAQs)

• Are all Secure Storage token formats supported in Token Management Service (TMS)?
  No. Some Secure Storage token formats are not supported in TMS. Review the list of supported formats before migration.
• Can I cancel a migration request after submitting it?
  You can cancel a migration request before migration begins, following Cybersource or Visa policies.
• What integration methods are supported by Token Management Service (TMS)?
  Token Management Service (TMS) supports Simple Order Application Programming Interface (API), SOAP Toolkit Application Programming Interface (API), REST Application Programming Interface (API), and Secure Acceptance.
• How long does the migration process take?
  Migration timeframes depend on your complexity, transaction volume, and readiness. Allow time for testing and validation.
• Where can I find more information about upgrading to Token Management Service (TMS)?
  For information and details about upgrading to the new Token Management Service (TMS) from Secure Store, please refer to the attached guides.

Additional Resources

For information and details about upgrading to the new Token Management Service (TMS) from Secure Store, please refer to the attached guides.
Frequently Asked Questions (FAQs)

• Token Management Service General FAQ
• Token Management Service Merchant Migration FAQ
• Token Management Service Partner Migration FAQ
• Token Management Service Stored Credential Mandate FAQ