web
You’re offline. This is a read only version of the page.
close

What can we help you with?


KA-04113


497

06/17/2025 20:36 PM

4.0

 

Instructions

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

Overview of Token Management Service

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

Migration Process

Contact your Cybersource or Visa representative to start the migration. Provide your Merchant ID and confirm eligibility. Not all Merchant IDs 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.

Token Formats and Types

AspectSecure StorageToken Management Service
Supported FormatsLegacy formatsNew and enhanced formats
Unsupported FormatsNot applicableSome legacy formats not supported
Token TypeDescription
Customer TokenIdentifies a customer across transactions
Payment InstrumentRepresents a specific payment method
Instrument IdentifierIdentifies a unique payment instrument

TMS supports new token types. Some Secure Storage token formats are not supported in TMS.

Token Sharing and Vault

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

Integration with Token Management Service

Integration MethodFormat/ProtocolNotes
Simple Order APINVPSupported
SOAP Toolkit APIXMLSupported
REST APIRESTSupported
Secure AcceptanceWeb interfaceSupported

Review your current integration. Update your API calls to use 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 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.

FAQs

Are all Secure Storage token formats supported in 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 TMS?
TMS supports Simple Order API, SOAP Toolkit API, REST 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.

TMS Migration Guide.pdf


Was this article helpful?


Articles Recommended for You