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
- 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
- Virtual Terminal Templates

ISO Standard Currency Codes

Reason Codes

On This Page

Pay By Link

Pay by Link provides merchants an easy and fast way to sell products or accept donations without any coding.

Prerequisites

Unified Checkout must be enabled for the merchant. Before Unified Checkout can be enabled for a merchant, it must be enabled at the portfolio level.

When you attempt to enable Pay by Link without enabling Unified Checkout, the boarding calls will fail with the error

<>

.

To enable Unified Checkout at the portfolio level, talk to your sales representative.

Pay by Link must be enabled at the portfolio level before in can be added to merchant accounts. To enable at Pay by Link the portfolio level, contact your sales representative.

Enabling `Pay by Link` on the Business Center

Before you can add Pay by Link, Unified Checkout must be added to the merchant account. To add Unified Checkout, see: Unified Checkout.

Navigate to the Merchant Details Page within Portfolio Management.

Click the

Add products

button.

Select

Pay by Link

, and click the

Add

button.

Pay by Link should appear on the Merchant's product list.

Enabling `Pay by Link` with the REST API

To enable Unified Checkout:

Set the

productInformation.selectedProducts.payments.payByLink.subscriptionInformation.enabled

field to

yes

When enabling both Pay by Link and Unified Checkout at the same time, you can include both products in the same request.

REST Example: Enabling `Pay by Link`

Production Endpoint:

POST https://api.cybersource.com/boarding/v1/registrations

Test Endpoint:

POST https://apitest.cybersource.com/boarding/v1/registrations

{
   "productInformation":{
      "selectedProducts":{
         "payments":{
            "unifiedCheckout":{
               "subscriptionInformation":{
                  "enabled":"true"
               }
            },
            "payByLink":{
               "subscriptionInformation":{
                  "enabled":"true"
               }
            }
         }
      }
   }
}

Back to top