API Overview

Merchant Boarding
- 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 Organization
  - Required Fields for Boarding a Merchant Organization
  - REST Example: Creating a Merchant Organization
- Add a Transacting Organization to a New Merchant Organization
  - Required Fields for Adding a Transacting Organization to an Existing Organization
  - REST Example: Creating a Transacting Organization
- Add a Transacting Organization to an Existing Organization
  - Required Fields for Adding a Transacting Organization to an Existing Organization
  - REST Example: Creating a Transacting Organization

Manage Organizations
- Retrieve a List of Organizations
  - Using Query Parameters to Filter Results
  - REST Example: Retrieving a List of Organizations
- Retrieve Organization Details
  - REST Example: Retrieving an Organization
- Update an Organization's Information
  - REST Example: Updating an Organization's Information
- Change an Organization's Status
  - REST Example: Changing an Organization's Status

Product Enablement and Configuration Using the BRS API
- Payer Authentication
  - Enable Payer Authentication
    - Required Fields for Enabling Payer Authentication
    - REST Example: Enabling Payer Authentication
- 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
  - Enable Token Management Service Using a Template
    - Required Fields for Enabling TMS Using a Template
    - REST Example: Enabling TMS Using a Template
  - Enable TMS and Enroll in Network Tokenization for a New Merchant
    - Required Fields for Enabling TMS and Enrolling in Network Tokenization for a New Merchant
    - REST Example: Enabling TMS and Enrolling in Network Tokenization for a New Merchant
  - Enable TMS and Enroll in Network Tokenization for an Existing Merchant
    - Required Fields for Enabling TMS and Enrolling in Network Tokenization for an Existing Merchant
    - REST Example: Enabling TMS and Enrolling in Network Tokenization for an Existing Merchant

Product Enablement and Configuration Using the PECS API
- Add a New Product to an Existing Organization
  - Required Fields for Adding a New Products
  - Example: Adding a New Product to an Existing Organization Using the PECS API
- Update Batch Group Using the PECS API
  - Required Fields for Updating a Batch Group Using the PECS API
  - Example: Updating a Batch Group Using the API
- Add a Processor Using the PECS API
  - Required Fields for Adding a Processor Using the PECS API
  - Example: Adding a Processor Using the PECS API
- Delete a Processor Using the PECS API
  - Required Fields for Deleting a Processor Using the PECS API
  - Example: Deleting a Processor Using the PECS API
- Add and Delete a Processor Using the PECS API
  - Required Fields for Adding and Deleting a Processor Using the PECS API
  - Example: Adding and Deleting a Processor Using the PECS API
- Payer Authentication
  - Configure Payer Authentication Using the PECS API
    - Required Fields for Configuring Payer Authentication Using the PECS API
    - Example: Configuring Payer Authentication Using the PECS API
- Token Management Service
  - Enable TMS with a Template Using the PECS API
    - Required Fields for Enabling TMS with a Template Using the PECS API
    - REST Example: Enabling TMS with a Template Using the PECS API
  - Enable TMS and Enroll in Network Tokenization Using the PECS API
    - Required Fields for Enabling TMS and Enrolling in Network Tokenization Using the PECS API
    - REST Example: Enabling TMS and Enrolling in Network Tokenization Using the PECS API

Extending the Hierarchy
- Hierarchy Example
- Add a Structural Organization to a Merchant Organization
  - Required Fields for Boarding a Structural Organization
  - REST Example: Creating a Structural Organization

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

Product Enablement and Configuration Using the BRS API

You can enable and configure different products for merchants in the Business Center and the Product Enablement and Configuration Service (PECS) API.

You can use the PECS API to enable, subscribe, and configure products for a merchant. The PECS API is used during merchant onboarding and after merchant onboarding:

Merchant onboarding
: PECS is invoked by the Boarding Registration Service (BRS) API.

Post-merchant onboarding
: PECS is called to update the merchant's product subscriptions or configurations.

During merchant onboarding, products can be enabled and configured. PECS supports multiple products that can be assigned to a merchant. Some products are available only for enablement and there is no capability to update configurations for these products. Some products are available for both enablement and configuration:

Enablement-only products:: Acceptance Devices
Card Present Connect
Checkout API
Customer Invoicing
Digital Payment Suite
Installments
Pay by Link
Receivables Manager
Recurring Billing
Reporting
Tax Calculation
Transaction Search
Unified Checkout Integration
Enablement and configuration products:: Account Updater
Advanced Billing
Alternative Payment Methods
Card Processing
Decision Manager
eCheck
Fraud Management Essentials
Gift Cards
Payer Authentication
Service Orchestration
Payouts
Token Management Service
Virtual Terminal

Back to top