API Overview

Token Management Service Developer Guide
- Recent Revisions to This Document
- VISA Platform Connect: Specifications and Conditions for Resellers/Partners
- TERMS OF USE APPLICABLE TO CARD NETWORK TOKENS

Introduction to the Token Management Service
- Types of Tokens

Token Management Service Workflows
- PAN Tokenization Process Using TMS
- Network Token Tokenization Process
- Push Provisioning Process
- Network Token Provisioning for Merchants
- Network Token CIT for Merchants
- Network Token MIT for Merchants
- Network Token Provisioning for Partners
- Network Token CIT for Partners
- Network Token MIT for Partners

Requesting the Token Management Service API
- HTTP Response Headers
- Case Sensitivity
- Metadata
- Patching Considerations
- Supported Processors
- Test Card Numbers

Token Management Service Onboarding
- Merchant ID Hierarchy
- Merchant ID Registration
- Portfolio MIDs for Partners
- Token Vault Management
- Message-Level Encryption Keys

Network Tokenization
- Network Token Enablement
- Network Token Onboarding—Partner Model
- Network Token Life-Cycle Management
- Network Token Life-Cycle Management Reports
- Token Requestor IDs

Manage Webhook Subscriptions
- Create Keys for Digital Signature
- Create Webhook Subscription
- Retrieve Webhook Subscription Details
- Update Webhook Subscription
- Delete Webhook Subscription

Customer Tokens
- Manage Customer Tokens
- Create a Customer
- Retrieve a Customer
- Update a Customer
- Delete a Customer
- Retrieve a Customer's Default Payment with an Unmasked Card Number
- Retrieve a Customer's Default Payment and Shipping Details
- Payments with Customer Tokens
- Create a Customer Token with Validated Payment Details
- Authorizing a Payment with a Customer Token
- Making a Credit with a Customer Token

Shipping Address Tokens
- Manage Shipping Address Tokens
- Create a Customer Shipping Address
- Add a Default Shipping Address
- Add a Non-Default Shipping Address
- Change a Default Shipping Address
- Retrieve a Customer Shipping Address
- Retrieve All Customer Shipping Addresses
- Update a Customer Shipping Address
- Delete a Customer Shipping Address
- Payments with Shipping Address Tokens
- Authorizing a Payment with a Non-Default Shipping Address

Customer Payment Instrument Tokens
- Manage Customer Payment Instrument Tokens
- Create a Customer Payment Instrument
- Add a Default Payment Instrument Using Instrument Identifier
- Add a Default Payment Instrument with Validated Payment
- Add a Non-Default Payment Instrument Using Instrument Identifier
- Add a Non-Default Payment Instrument with Validated Payment
- Change a Customer's Default Payment Instrument
- Retrieve a Customer Payment Instrument
- Retrieve a Customer Payment Instrument with an Unmasked Card Number
- List Payment Instruments for a Customer
- Update a Customer Payment Instrument
- Delete a Customer Payment Instrument
- Payments with Customer Payment Instrument Tokens
- Authorizing a Payment with a Non-Default Payment Instrument
- Making a Credit with a Non-Default Payment Instrument

Payment Instrument Tokens
- Manage Payment Instrument Tokens
- Create a Payment Instrument
- Retrieve a Payment Instrument
- Find Payment Instruments by Card Number
- Retrieve a Payment Instrument with an Unmasked Card Number
- Update a Payment Instrument
- Delete a Payment Instrument
- Payments with Payment Instrument Tokens
- Authorizing a Payment with a Payment Instrument
- Making a Credit with a Payment Instrument

Instrument Identifier Tokens
- Manage Instrument Identifier Tokens
- Create an Instrument Identifier
- Create an Instrument Identifier for Enrollable Network Tokens
- Retrieve an Instrument Identifier
- Update an Instrument Identifier
- Retrieve an Instrument Identifier's Payment Instruments
- Retrieve an Instrument Identifier with an Unmasked Card Number
- Delete an Instrument Identifier
- Payments with Instrument Identifier Tokens
- Create an Instrument Identifier Token with Validated Payment Details
- Authorize a Payment with an Instrument Identifier
- Making a Credit with an Instrument Identifier

Legacy Tokens
- Payments with Legacy Tokens
- Authorizing a Payment with a Legacy Token
- Making a Credit with a Legacy Token

Network Tokens for Merchants
- Payments with Network Tokens for Merchants
- Authorize a Payment While Ignoring Network Token
- Manage Merchant-Initiated Transactions and Network Tokens
- Update Merchant-Initiated Transaction Authorization Options

Network Tokens for Partners
- Manage Network Tokens for Partners
- Provision a Network Token for a Card Number
- Provision a Network Token for an Existing Instrument Identifier
- Provision a Network Token for a Consumer
- Provision a Network Token for a Token
- Retrieve a Standalone Network Token
- Delete a Standalone Network Token
- Retrieve Network Token Payment Credentials
- Retrieve Network Token AFT Payment Credentials
- Retrieve an Instrument Identifier
- Delete an Instrument Identifier
- Network Token Provision Failures

Push Provisioning for Network Tokens
- Provision a Network Token with Push Provisioning

Card Art
- Retrieve Card Art

BIN Lookup Service and TMS
- REST Example: Retrieving an Instrument Identifier with BIN Details

Using Token Management Service with Wallet Apps
- Manage Tokens with Wallet Apps
- Create a New Customer Account
- Add a New Shipping Address
- Edit or Delete a Shipping Address
- Create a New Payment Instrument with the Payments API
- Edit or Delete a Payment Method
- Change the Default Payment Method
- Add a New Payment Method Address
- View Wallet
- Payments with Tokens and Wallet Apps
- Authorize a Payment

Reference Information
- Encrypt and Decrypt Data
- HTTP Status Codes

Supported Processors

Network Token Onboarding—Partner Model

The workflow begins when the partner creates a merchant profile on the Cybersource platform using TMS templates.

Network Token Onboarding for Partners

The gateway sets up templates for TMS.

partner creates merchant profile using TMS templates.

The partner submits a request to Cybersource via API.

Cybersource creates a merchant based on the API request and confirms boarding success with partner.

The partner provides merchant details via email to enable network tokenization and submits email to Cybersource support.

Cybersource verifies the request, generates the onboarding request, and sends the request to the card brand.

The card brand completes the registration process and responds to Cybersource with the confirmation and token requestor ID (TRID).

Cybersource notifies the partner that onboarding is complete.

The partner completes merchant setup.