Recent Revisions to This Document

About This Guide

Introduction to Payouts
- Overview
- Supported Recipient Card Types
- Supporting Payment Networks
- Requirements

Services
- Original Credit Transactions (OCTs)
  - Required Fields for Performing an OCT
  - Performing an OCT
  - NVP Example: OCT Request Using the Simple Order API
  - XML Example: OCT Request Using the Simple Order API
  - Testing the OCT Service
    - Mastercard Test Payment Card Numbers
    - Visa Test Payment Card Numbers
- Original Credit Transactions (OCTs) with Cryptocurrency
  - Required Fields for Performing an OCT with Cryptocurrency
  - Performing an OCT with Cryptocurrency
  - Example: OCT with Cryptocurrency Request Using the Simple Order API
  - Testing the OCT Service with Cryptocurrency
    - Mastercard Test Payment Card Numbers
    - Visa Test Payment Card Numbers

Optional Features
- Aggregator Support for Payouts
  - Services and Cards Supported with Payment Aggregation
  - Aggregator Terminology
  - OCTs with Aggregator Support
    - Required Fields for Aggregator Support for an OCT
    - Required Fields for Performing an OCT
    - Performing an OCT with Aggregator Support
- BIN Lookup
  - Using the BIN Lookup Service
- Token Management Service

On This Page

Simple Order API | Visa Platform Connect

Required Fields for Aggregator Support for an OCT

For merchants that are payment facilitators, these fields are required in a request for an OCT:

invoiceHeader_submerchantID: ID that you assigned to the sub-merchant.
octService_aggregatorID: Value that identifies you as a payment aggregator. Get this value from the processor.
octService_aggregatorName: Payment aggregator business name.
octService_serviceProviderName: Name of the transfer service provider.