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 OCT with Cryptocurrency

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

clientReferenceInformation.code
merchantInformation.vatRegistrationNumber: Required only in Latin America.
orderInformation.amountDetails.currency
orderInformation.amountDetails.totalAmount: Cannot exceed 50,000 USD.
orderInformation.isCryptocurrencyPurchase: Set to
true
.
paymentInformation.card.expirationMonth: Not required when you are using a client token.
paymentInformation.card.expirationYear: Not required when you are using a customer token.
paymentInformation.card.number: Not required when you are using a customer token.
processingInformation.businessApplicationId: Not required when your account includes this value.
processingInformation.purposeOfPayment: Optional for India. For more information, contact your Cybersource technical account manager.
recipientInformation.address1: Required for cross-border transactions into and out of Canada. Otherwise, optional.
recipientInformation.country: Required for cross-border transactions into and out of Canada. Otherwise, optional.
recipientInformation.firstName
recipientInformation.lastName
recipientInformation.locality: Required for cross-border transactions into and out of Canada. Otherwise, optional.
recipientInformation.postalCode: Required for cross-border transactions into and out of Canada. Otherwise, optional.
senderInformation.account.fundsSource
senderInformation.account.number: Required for Mastercard transactions.
senderInformation.administrativeArea: Required when the sender country is the U.S. or Canada.
senderInformation.vatRegistrationNumber: Required only in Latin America.

Back to top