Recent Revisions to This Document

About This Guide

Token Management Service
- Types of Tokens
  - Customer Tokens
  - Shipping Address Tokens
  - Payment Instrument Tokens
  - Instrument Identifier Tokens
  - Network Tokens
- Token Life-Cycle Management

Token Management Service Workflows
- PAN Tokenization Process Using TMS
- Network Token Tokenization Process
- Network Token Provisioning—Merchant Model
- Network Token Authorizations (CIT)—Merchant Model
- Network Token Authorizations (MIT)—Merchant Model
- Network Token Provisioning—Partner Model
- Network Token Authorizations (CIT)—Partner Model
- Network Token Authorizations (MIT)—Partner Model

Requesting the Token Management Service API
- HTTP Headers
- Case Sensitivity
- Metadata
- Patching Considerations
  - Pagination
- Supported Processors
- Test Cards

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

Network Tokenization
- Network Token Enablement
- Network Token Onboarding—Partner Model
- Token Requestor IDs

Manage Webhook Subscriptions
- Create Keys for Digital Signature
  - tms-net-tkn-webhook-create-key-reqfields
- Create Webhook Subscription
  - tms-net-tkn-webhook-create-sub-reqfields
- Retrieve Webhook Subscription Details
  - tms-net-tkn-webhook-retrieve-sub-reqfields
- Update Webhook Subscription
  - tms-net-tkn-webhook-update-sub-reqfields
- Delete Webhook Subscription
  - tms-net-tkn-webhook-delete-sub-reqfields

Customer Payment Instrument Tokens
- Manage Customer Payment Instrument Tokens
  - Create a Customer Payment Instrument
    - tms-cust-pi-tkn-create-reqfields
    - tms-cust-pi-tkn-create-optfields
  - Add a Default Payment Instrument Using Instrument Identifier
    - tms-cust-pi-tkn-add-default-pi-ii-reqfields
    - tms-cust-pi-tkn-add-default-pi-ii-optfields
  - Add a Default Payment Instrument with Validated Payment
    - tms-cust-pi-tkn-add-default-pi-valid-reqfields
  - Add a Non-Default Payment Instrument Using Instrument Identifier
    - tms-cust-pi-tkn-add-nondefault-pi-ii-reqfields
    - tms-cust-pi-tkn-add-nondefault-pi-ii-optfields
  - Add a Non-Default Payment Instrument with Validated Payment
    - tms-cust-pi-tkn-add-nondefault-pi-valid-reqfields
  - Change a Customer's Default Payment Instrument
    - tms-cust-pi-tkn-change-default-pi-reqfields
  - Retrieve a Customer Payment Instrument
    - tms-cust-pi-tkn-retrieve-reqfields
  - Retrieve a Customer Payment Instrument with Unmasked Card Number
    - tms-cust-pi-tkn-retrieve-unmasked-reqfields
  - List Payment Instruments for a Customer
    - tms-cust-pi-tkn-retrieve-mult-reqfields
  - Update a Customer Payment Instrument
    - tms-cust-pi-tkn-update-reqfields
    - tms-cust-pi-tkn-update-optfields
  - Delete a Customer Payment Instrument
    - tms-cust-pi-tkn-delete-reqfields
- Payments with Customer Payment Instrument Tokens
  - Authorize a Payment with Non-Default Payment Instrument
    - tms-cust-pi-tkn-pay-nondefault-pi-reqfields
    - tms-cust-pi-tkn-pay-nondefault-pi-optfields
  - Make a Credit with Non-Default Payment Instrument
    - tms-cust-pi-tkn-credit-nondefault-pi-reqfields
    - tms-cust-pi-tkn-credit-nondefault-pi-optfields

Instrument Identifier Tokens
- Manage Instrument Identifier Tokens
  - Create an Instrument Identifier
    - tms-ii-tkn-create-reqfields
    - tms-ii-tkn-create-optfields
  - Retrieve an Instrument Identifier
    - tms-ii-tkn-retrieve-reqfields
  - Update an Instrument Identifier
    - tms-ii-tkn-update-reqfields
    - tms-ii-tkn-update-optfields
  - Retrieve an Instrument Identifier's Payment Instruments
    - tms-ii-tkn-retrieve-pi-reqfields
  - Retrieve an Instrument Identifier with Unmasked Card Number
    - tms-ii-retrieve-unmasked-card-reqfields
  - Delete an Instrument Identifier
    - tms-ii-tkn-delete-reqfields
- Payments with Instrument Identifier Tokens
  - Create an Instrument Identifier Token with Validated Payment Details
    - tms-ii-create-valid-pay-reqfields
  - Authorize a Payment with an Instrument Identifier
    - tms-ii-tkn-pay-reqfields
  - Make a Credit with an Instrument Identifier
    - tms-ii-tkn-credit-reqfields

Legacy Tokens
- Payments with Legacy Tokens
  - Authorize a Payment with Legacy Token
    - tms-legacy-tkn-pay-reqfields
  - Make a Credit with Legacy Token
    - tms-legacy-tkn-credit-reqfields

Network Tokens for Merchants
- Payments with Network Tokens for Merchants
  - Authorize a Payment Ignoring Network Token
    - tms-net-tkn-direct-merch-pay-reqfields
- Manage Merchant-Initiated Transactions and Network Tokens
  - Update Merchant-Initiated Transaction Authorization Options
    - tms-mit-update-auth-opt-reqfields

Network Tokens for Partners
- Manage Network Tokens for Partners
  - Provision a Network Token for a Card Number
    - tms-net-tkn-partner-card-reqfields
    - tms-net-tkn-partner-card-optfields
  - Provision a Network Token for an Existing Instrument Identifier
    - tms-net-tkn-partner-ii-reqfields
    - tms-net-tkn-partner-ii-optfields
  - Retrieve a Network Token for Payment Credentials
    - tms-net-tkn-partner-retrieve-pay-cred-reqfields
  - Retrieve an Instrument Identifier
    - tms-ii-tkn-retrieve-reqfields
  - Delete an Instrument Identifier
    - tms-ii-tkn-delete-reqfields
- tms-net-tkn-fail-ex-rest

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

On This Page

Simple Order API | Visa Platform Connect

Network Token Onboarding—Partner Model

This workflow shows the merchant onboarding process using the Cybersource boarding API.

The workflow begins when the partner creates a merchant 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 TRID.

Cybersource updates the partner on completion of onboarding.

The partner completes merchant setup.