API Overview

Payouts Developer Guide
- Recent Revisions to This Document
- VISA Platform Connect: Specifications and Conditions for Resellers/Partners

Introduction to Payouts
- Overview of Payouts
- AFT Types
- Aggregator Support for Payouts
- Supported Card Types
- Payment Networks
- Requirements

Introduction to OCT
- Visa Card Types and Services for OCT

AFT Transactions
- Dual Message Account Funding Transactions (AFTs)
  - Required Fields for a Dual-Message AFT Request
  - Simple Order Example: Dual-Message AFT
- Dual Message Account Funding Transactions (AFTs) with Visa Secure
  - Required Fields for a Dual-Message AFT with Visa Secure Request
  - Simple Order Example: Dual-Message AFT with Visa Secure
- Dual Message Account Funding Transactions (AFTs) with Visa Secure for Merchant Aggregators
  - Required Fields for a Dual-Message AFT with Visa Secure for Merchant Aggregators Request
  - Simple Order Example: Dual-Message AFT with Visa Secure for Merchant Aggregators
- Dual Message Account Funding Transactions (AFTs) with Network Tokens
  - Required Fields for a Dual-Message AFT with Network Tokens Request
  - Simple Order Example: Dual-Message AFT with Network Tokens
- Dual Message Account Funding Transactions (AFTs) to Establish a Recurring Payout Transaction (CIT)
  - Required Fields for a Dual-Message AFT with a CIT Request
  - Simple Order Example: Dual-Message AFT with a CIT
- Dual Message Account Funding Transactions (AFTs) for a Recurring Payout Transaction (MIT)
  - Required Fields for a Dual-Message AFT with an MIT Request
  - Simple Order Example: Dual-Message AFT with an MIT

Original Credit Transactions (OCTs)
- Original Credit Transactions (OCTs)
  - Required Fields for an OCT
  - Simple Order Example: OCT Request
- Original Credit Transactions (OCTs) with Aggregators
  - Required Fields for an OCT with Aggregators
  - Simple Order Example: OCT Request with Aggregators
- Original Credit Transactions (OCTs) with Tokens
  - Required Fields for an OCT with Tokens
  - Simple Order Example: OCT with Tokens Request

Reference
- Business Application Identifier
- Business Application Identifier and Merchant Category Code Use Cases
- Sender Source
- Test Card Numbers

Required Fields for an OCT with Tokens

These fields are required in a request for an OCT with tokens:

These fields are required in a request for an OCT:

ccAuthService_merchantVerificationValue
invoiceHeader_businessApplicationID
invoiceHeader_merchantDescriptorContact: Required when the merchant descriptor field is included.
merchantID
purchaseTotals_currency
purchaseTotals_grandTotalAmount: Cannot exceed 50,000 USD.
recipient_countryOfBirth
recipient_dateOfBirth
recipient_email
recipient_firstName
recipient_lastName
recipient_middleName
recipient_name
recipient_nationality
recipient_occupation
sender_accountNumber
sender_dateOfBirth
sender_id
sender_firstName: First name of the sender when the sender is an individual. Required for original credit transactions (OCTs) that use the Payouts services and supported only for Mastercard card transactions.; If the sender is a business or government entity, use the
sender_name
field instead.
sender_lastName: Last name of the sender when the sender is an individual. Required for original credit transactions (OCTs) that use the Payouts services and supported only for Mastercard card transactions.; If the sender is a business or government entity, use the
sender_name
field instead.
sender_name: If the sender is an individual, use the
sender_firstName
and
sender_lastName
fields instead.
sender_middleName
sender_sourceOfFunds
sender_state: Required when the sender country is the US or Canada.

Related Information

API Field Reference for the Simple Order API