API Overview

Merchant Boarding User Guide
- Recent Revisions to This Document
- VISA Platform Connect: Specifications and Conditions for Resellers/Partners

Introduction to the Boarding Registration Service
- Requirements
- Understanding Accounts and Organizations
- Understanding Organization IDs
- Configure a Single Merchant
- Configure Multiple Merchants
- Configure Multiple Merchants with an Extended Hierarchy

Product Templates
- Template Components
- Products

Using Templates
- Retrieving Templates
- Add Templates
- Editing Templates
- Deleting Templates
- Setting the Default Template

Product Boarding Template Reference
- Account Updater Templates
- Card Processing Templates
  - Configuring a Card Processing Template
  - Processor-Specific Fields
- Customer Invoicing
- ACH Templates
- Fraud Management Essentials Templates
- Gift Card Templates
- Payer Authentication Templates
- Pay By Link
- Secure Acceptance Templates
- Token Management Service Templates
- Unified Checkout Integration
- Virtual Terminal Templates

Create Organizations
- Create a Merchant Account
  - Add Merchant Account Information
  - Set Up the Transacting Organization and Products
- Add an Additional Transacting Organization to an Existing Merchant Organization
  - Configure the Transacting Organization and Products

Search for Organizations
- Search Results
- Sort and Filter Search Results
- View an Organization's Hierarchy

Manage Organization Information
- View and Edit an Organization's Business Details
- View and Edit an Organization's Processor Details

Update an Organization's Products
- Add a Product to an Organization
- Modify a Product for an Organization
- Remove a Product from an Organization

Change an Organization's Status

Product Enablement and Configuration
- Enablement-Only Products
  - Add an Enablement-Only Product to an Organization
- Alternative Payments
  - Add Alternative Payments to a Merchant Account
  - Add Alternative Payments with Self-Enablement to an Organization
  - Add Alternative Payments to an Existing Organization
  - Modify an Alternative Payment Methods Configuration for an Organization
- Payer Authentication
  - Add Payer Authentication to a Merchant Account
  - Add Payer Authentication to an Existing Organization
  - Modify a Payer Authentication Configuration for an Organization
- Token Management Service
  - Token Vault Management
    - Token Requestor IDs
    - Configure the Token Vault Settings Using the Business Center
    - Configure the Token Vault Access Using the Business Center
  - Add TMS to a Merchant Account
  - Add TMS to an Existing Organization

Switch Merchants

Send a Registration Email

Extend the Hierarchy
- Hierarchy Example
- Add a Structural Organization to an Existing Merchant
  - Add a Structural Organization
  - Create a Transacting Organization and Products

Product Boarding Template Reference
- Account Updater Templates
- Card Processing Templates
  - Configuring a Card Processing Template
  - Processor-Specific Fields
- Customer Invoicing
- ACH Templates
- Fraud Management Essentials Templates
- Gift Card Templates
- Payer Authentication Templates
- Pay By Link
- Secure Acceptance Templates
- Token Management Service Templates
- Unified Checkout Integration
- Virtual Terminal Templates

ISO Standard Currency Codes

Reason Codes

On This Page

`Token Management Service`

The Token Management Service (TMS) links tokens across service providers, payment types, and channels for sellers, acquirers, and technology partners. TMS tokenizes, securely stores, and manages the primary account number (PAN), the payment card expiration date, electronic check details, and customer data. TMS also enables merchants to create a network token of a customer's payment card.

IMPORTANT

When you board a merchant and enable TMS and network tokenization, the token requestor ID is enrolled at the merchant account organization level where the token vault is configured. You must include the merchant business information during token requestor ID enrollment and when you create the TMS token vault. This ensures that the network tokens that are provisioned are assigned to the merchant that owns the tokens.

Back to top