Recent Revisions to This Document

About This Guide

VISA Platform Connect: Specifications and Conditions for Resellers/Partners

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

Services
- Account Funding Transactions (AFTs)
  - Required Fields for Performing an AFT
  - Optional Fields for Performing an AFT
- Dual Message Account Funding Transactions (AFTs)
  - Required Fields for Performing an AFT
  - Example: Dual-Message AFT Request Using the REST API
- Dual Message Account Funding Transactions (AFTs) with Visa Secure
  - Required Fields for Performing an AFT using Visa Secure
  - Example: Dual-Message AFT Request with Visa Secure Using the REST API
- Dual Message Account Funding Transactions (AFTs) with Network Tokens
  - Required Fields for Performing an AFT using Tokens
  - Example: Dual-Message AFT Request with Visa Secure Using the REST API
- Dual Message Account Funding Transactions (AFTs) to Establish a Recurring Payout Transaction (CIT)
  - Required Fields for Performing an AFT using Tokens
  - Example: Dual-Message AFT Request with Visa Secure Using the REST API
- Dual Message Account Funding Transactions (AFTs) for a Recurring Payout Transaction (MIT)
  - Required Fields for Performing an AFT using Tokens
  - Example: Dual-Message AFT Request with Visa Secure Using the REST API
- Original Credit Transactions (OCTs)
  - Required Fields for Performing an OCT
  - Optional Fields for Performing an OCT
  - 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
  - Example: OCT with Cryptocurrency Request Using the REST 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
- BIN Lookup
  - Using the BIN Lookup Service
- Token Management Service

On This Page

REST API | Visa Platform Connect

Required Fields for Performing an AFT using Tokens

These fields are required in a request for an authorization for an AFT with a token:

merchantInformation.merchantDescriptor.name
merchantInformation.vatRegistrationNumber
orderInformation.amountDetails.anticipatedAmount
orderInformation.amountDetails.surcharge.amount
processingInformation.authorizationOptions.aftIndicator
processingInformation.businessApplicationId
processingInformation.fundingOptions.initiator.type
recipientInformation.accountId
recipientInformation.accountType
recipientInformation.address1
recipientInformation.address2
recipientInformation.buildingNumber
recipientInformation.firstName
recipientInformation.lastName
recipientInformation.middleName
recipientInformation.postalCode
recipientInformation.streetName
senderInformation.account.fundsSource
senderInformation.account.number
senderInformation.address1
senderInformation.administrativeArea
senderInformation.countryCode
senderInformation.firstName
senderInformation.identificationNumber
senderInformation.locality
senderInformation.name
senderInformation.personalIdType
senderInformation.referenceNumber
senderInformation.type

Back to top