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
  - REST Example: Dual-Message AFT
- Dual Message Account Funding Transactions (AFTs) with Visa Secure
  - Required Fields for a Dual-Message AFT with Visa Secure Request
  - REST 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
  - REST 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
  - REST 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
  - REST 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
  - REST Example: Dual-Message AFT with an MIT

Original Credit Transactions (OCTs)
- Original Credit Transactions (OCTs)
  - Required Fields for an OCT
  - REST Example: OCT Request
- Original Credit Transactions (OCTs) with Aggregators
  - Required Fields for an OCT with Aggregators
  - REST Example: OCT Request with Aggregators
- Original Credit Transactions (OCTs) with Tokens
  - Required Fields for an OCT with Tokens
  - REST 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 a Dual-Message AFT with Network Tokens Request

These fields are required to process a dual-message AFT with network tokens request:

acquirerInformation.merchantId
aggregatorInformation.name
captureOptions.dateToCapture
clientReferenceInformation.code
consumerAuthenticationInformation.cavv
consumerAuthenticationInformation.xid: This field is only required when you have received an XID value in a previous transaction.
merchantInformation.merchantDescriptor.administrativeArea
merchantInformation.merchantDescriptor.locality
merchantInformation.merchantDescriptor.name
merchantInformation.merchantDescriptor.postalCode
merchantInformation.vatRegistrationNumber
orderInformation.amountDetails.anticipatedAmount
orderInformation.amountDetails.currency
orderInformation.amountDetails.surcharge.amount
orderInformation.amountDetails.totalAmount
orderInformation.billTo.address1
orderInformation.billTo.administrativeArea
orderInformation.billTo.country
orderInformation.billTo.email
orderInformation.billTo.firstName
orderInformation.billTo.lastName
orderInformation.billTo.locality
orderInformation.billTo.phoneNumber
orderInformation.billTo.postalCode
paymentInformation.tokenizedCard.card.cryptogram
paymentInformation.tokenizedCard.expirationMonth
paymentInformation.tokenizedCard.expirationYear
paymentInformation.tokenizedCard.number
paymentInformation.tokenizedCard.securityCode
paymentInformation.tokenizedCard.transactionType
paymentInformation.tokenizedCard.type

processingInformation.authorizationOptions.aftIndicator
processingInformation.authorizationOptions.initiator.storedCredentialUsed
processingInformation.authorizationOptions.initiator.type
processingInformation.businessApplicationId
processingInformation.commerceIndicator
processingInformation.fundingOptions.initiator.type
processingInformation.purposeOfPayment
recipientInformation.accountId
recipientInformation.accountType
recipientInformation.address1
recipientInformation.address2
recipientInformation.buildingNumber
recipientInformation.country
recipientInformation.firstName
recipientInformation.lastName
recipientInformation.locality
recipientInformation.middleName
recipientInformation.nationality: The value must be the standard three character ISO 3166 alpha country code. For more information, see ISO 3166 Country Codes.
recipientInformation.postalCode
recipientInformation.streetName
senderInformation.account.fundsSource
senderInformation.account.number
senderInformation.address1
senderInformation.administrativeArea
senderInformation.countryCode
senderInformation.firstName
senderInformation.identificationNumber
senderInformation.lastName
senderInformation.locality
senderInformation.middleName
senderInformation.name
senderInformation.personalIdType
senderInformation.phoneNumber
senderInformation.postalCode
senderInformation.referenceNumber
senderInformation.type

Related Information

REST API Field Reference Guide