Payouts Developer Guide

This section describes how to use this guide and where to find further information.

Audience and Purpose

This document is written for developers who want to use the Cybersource APIs to integrate Cybersource Payouts services into their transaction management system.

Conventions

This statement is used in this document:

IMPORTANT

An Important
statement contains information essential to successfully completing a task or learning a concept.

Customer Support

For support information about any service, visit the Support Center:

http://support.visaacceptance.com

Recent Revisions to This Document

25.05.01

Added new fields to list of required fields for AFT and OCT sections. See Required Fields for an AFT Request and Required Fields for an OCT.

22.06

Initial release.

Introduction to `Payouts`

This introduction contains an overview of the Payouts service and describes the supported sender card types, payment networks, requirements, and limitations.

Overview

The Payouts service transfers funds from one account to another using a two-step transaction process:

An account funding transaction (AFT) withdraws funds from a sender’s account using standard credit card processing.

An original credit transaction (OCT) deposits funds into a recipient’s account.

An AFT and OCT are independent transactions, though an AFT often precedes a corresponding OCT.

In typical payment transactions, you initiate debits and credits to receive payments from cardholders for your goods and services. With Payouts, you provide a money transfer service by initiating AFT and OCT transactions that move funds between accounts. These are the money transfer types:

An account-to-account payment moves funds between accounts owned by the same person.

A business-to-person payment moves funds between a merchant and a cardholder.

A person-to-person payment moves funds between two cardholders.

For a person-to-person funds transfer, Pull and Push services are executed. When an AFT is authorized for a person-to-person transaction, the funds are available and can be withdrawn from the sender's account. This service is referred to as a Pull service. A subsequent OCT is authorized, and the funds can deposited into the recipient's account. This service is referred to a Push service.

The Payouts system ensures that both Pull and Push services are executed efficiently, providing a seamless experience for users. By leveraging Payouts, businesses and individuals can streamline their financial operations, making transactions more efficient and reliable.

No merchant goods are involved in Payouts transactions.

IMPORTANT

You must receive approval from

Chase Paymentech Solutions

before using the AFT service. Contact

Chase Paymentech Solutions

to register in the AFT program.

AFT Types

The Account Funding Transaction (AFT) is a specific type of transaction that moves funds from a Visa account to another Visa or non-Visa account. It is primarily used for loading or topping up prepaid card accounts, transferring funds into another financial account (like a savings account), acting as a funding source for person-to-person (P2P) money transfers, or loading third-party digital wallets. AFTs cannot be used for purchasing goods or services or transferring funds to a merchant account.

AFTs are the required transactions to load or top-up prepaid cards in all regions. An AFT is the required pull transaction to be used for disbursing payroll funds, P2P or me-to-me transactions, and pre-funding a customer's digital wallet in a card-not-present environment. When used independently to fund another Visa or non-Visa account, AFTs must be used only to fund an account belonging to the same individual or entity holding the Visa account.

Reversal and Adjustment Transactions

You can reverse an AFT within the first 24 hours of the original transaction before the transaction settles.

You can refund an AFT back to the sender's card within 30 days of the original AFT back to the sender's card. You cannot originate a refund if the original transaction is over 30 days old. The system accepts a refund after the original AFT settles.

IMPORTANT

Issuers can manage AFT refunds as credit adjustments instead of posting the transaction directly into the cardholder's account. Therefore, the timeframe for when the cardholder should expect the refund will vary by issuer.

Relaxed Requirements for Address Data and Expiration Date for AFTs

You can have your Cybersource account configured to enable relaxed requirements for address data and expiration date in your AFT request.

Relaxed Requirements for Address Data: Address Verification Service (AVS) compares portions of the billing address from the request message with address data on file at the issuing bank. Results are returned for the street address and for the postal code. Relaxed requirements for address data allow you to make address fields that are normally required, such as billing address, optional in your transaction request.
Relaxed Requirements for Expiration Date: The card expiration month and year from the request message are compared with the card expiration date on file at the issuing bank. Relaxed requirements for expiration date allow you to make expiration date fields optional in your transaction request.

To enable relaxed requirements for address data and expiration date, contact customer support to configure your account for this feature.

Supported Recipient Card Types, Currencies, Transactions, and BAIs

These are recipient card types :

Mastercard—debit cards and prepaid cards only

Visa—debit cards and prepaid cards only

These currencies are supported: USD

These transactions are supported :

Disbursements

Fast Funds. A Fast Funds transaction makes funds available to the recipient within 30 minutes. Use the BIN lookup service to find out whether a payment card is enabled for Fast Funds.

Money transfers

These business application identifiers (BAIs) are supported :

Account to account (AA)

Person to person (PP)

Payment
Networks

Visa Direct: The Visa Direct payment network provides these functions for Payouts:
Enhanced message types for OCTs.
Account funding transactions (AFTs), which provide funds for OCTs.
Processes, policies, and underlying operating regulations and mandates for issuers and acquirers.
Mastercard Send: The Mastercard Send payment network transfers funds to Mastercard products. Mastercard Send enables customers to move funds quickly and safely and receive disbursements from businesses and governments.

Requirements

To use Payouts services, you must meet these requirements:

You must obtain a license from your processor for requesting this type of transaction.

The acquirer and issuer must be in the US

Risk management requirements for AFTs:

You must conduct a comprehensive risk assessment of your business policies and practices, fraud prevention and detection techniques, anti-money-laundering program, and risk controls. In addition to implementing fraud prevention tools, you must implement business practices to minimize fraud losses.

You must comply with the Visa Core Rules and Visa Product and Service Rules
, local regulations, applicable sanctions, anti-money laundering laws, and anti-terrorist financing laws.

Cardholder data authentication requirements for AFTs:

For each AFT, you must collect and verify data about the sender. You must also screen sender data against relevant watch lists in accordance with local laws and regulations for the purposes of risk management, sanctions enforcement, and anti-money-laundering and anti-terrorist financing control.

The method you use to authenticate sender data must follow regulatory and industry standards and best practices as well as applicable local laws and regulations. Examples are the use of government-issued photo identification, PINs, Visa Secure, Internet banking identification, telephone banking identification, and consumer device cardholder verification method.

Transaction monitoring requirements for AFTs:

You must implement transaction monitoring and screening procedures to flag high-risk transactions for review prior to submission. These procedures must include these activities:

Modulus 10 checks

Count, amount, and rolling limits

Checks to determine whether the sender is on any applicable government or bank-specific blocked lists

You must implement processes to identify signs of fraud or misuse, including money laundering and terrorist financing.

You must make sure that Payouts transactions are not being used to pay for goods and services. For example, you can check for a high number or variety of senders to a single recipient.

AFT Transactions

The Account Funding Transaction (AFT) allows the transfer of funds between a payment card and another account, including other payment cards. When used independently, an AFT can only transfer funds between accounts owned by the same person or business entity. An AFT is not intended for paying goods and services, funding a merchant account, or repaying debts.

IMPORTANT

You must receive approval from

Chase Paymentech Solutions

before using the AFT services. Contact

Chase Paymentech Solutions

to register in the AFT program.

Account Funding Transactions (AFTs)

Payouts uses the authorization service to support AFTs. An AFT withdraws funds from a sender’s account.

IMPORTANT

You must receive prior approval from

Chase Paymentech Solutions

before using the AFT services. Contact

Chase Paymentech Solutions

to register with the AFT program.

Endpoint

Production:

POST https://api.cybersource.com/pts/v2/payments

Test:

POST https://apitest.cybersource.com/pts/v2/payments

Required Fields for an AFT Request

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

clientReferenceInformation.code
merchantInformation.categoryCode: Set this field to one of the merchant category code (MCC) values in this table.

Supported MCCs for each Business Application Identifier (BAI)

BAI
BAI MCCs with Mastercard
MCCs with Visa

AA
4829
4829
,
6012

PP
4829
4829
,
6012
orderInformation.amountDetails.currency
orderInformation.amountDetails.foreignExchangeFee
orderInformation.amountDetails.serviceFee
orderInformation.amountDetails.totalAmount: The
orderInformation.amountDetails.totalAmount
must be included in the request.

Maximum amount per customer account in one day: 10,000 USD.

Maximum amount per customer account in seven days: 25,000 USD.

Maximum amount per customer account in thirty days: 50,000 USD.
orderInformation.billTo.address1: Required except when your account is configured for relaxed requirements for address data and expiration date.
orderInformation.billTo.administrativeArea: Required when the billing country is the US or Canada except when your account is configured for relaxed requirements for address data and expiration date.
orderInformation.billTo.country: Required except when your account is configured for relaxed requirements for address data and expiration date.
orderInformation.billTo.email: Required except when your account is configured for relaxed requirements for address data and expiration date.
orderInformation.billTo.firstName: Required except when your account is configured for relaxed requirements for address data and expiration date.
orderInformation.billTo.lastName: Required except when your account is configured for relaxed requirements for address data and expiration date.
orderInformation.billTo.locality: Required except when your account is configured for relaxed requirements for address data and expiration date.
orderInformation.billTo.postalCode: Required when the billing country is the US or Canada except when your account is configured for relaxed requirements for address data and expiration date.
paymentInformation.card.expirationMonth: Required except when your account is configured for relaxed requirements for address data and expiration date.
paymentInformation.card.expirationYear: Required except when your account is configured for relaxed requirements for address data and expiration date.
paymentInformation.card.number
processingInformation.businessApplicationId: Required when this value is not included in your account.

These are the values when using a Mastercard card type:

AA
: Account-to-account.
PP
: Person to person.
senderInformation.account.number
senderInformation.firstName
senderInformation.lastName

Supported MCCs for each Business Application Identifier (BAI)
BAI	BAI MCCs with Mastercard	MCCs with Visa
AA	4829	4829 , 6012
PP	4829	4829 , 6012

Related Information

REST API Field Reference Guide

Optional Fields for an AFT

You can include these optional fields in an authorization request for an AFT:

orderInformation.amountDetails.foreignExchangeFee: This field is supported only for cross-border transactions. A cross-border transaction is a transaction for which the payment card is issued in one country and accepted by a merchant in another country.
orderInformation.amountDetails.serviceFee: This field is supported only for cross-border transactions. A cross-border transaction is a transaction for which the payment card is issued in one country and accepted by a merchant in another country.
paymentInformation.card.type: Set this field to
001
for Visa or
002
for Mastercard.
processingInformation.authorizationOptions.ignoreAvsResult: To ignore AVS results, set this field to
true
to ignore the results of AVS checking. The capture service is run even when the authorization receives an AVS decline. An AVS decline is indicated by a response flag value of
DAVSNO
.
processingInformation.commerceIndicator: Set this field to
internet
.
senderInformation.firstName: If the sender is a business or government entity, use the
senderInformation.name
field instead.
senderInformation.lastName: If the sender is a business or government entity, use the
senderInformation.name
field instead.
senderInformation.name: If the sender is an individual, use the
senderInformation.firstName
and
senderInformation.lastName
fields instead.

Related Information

REST API Field Reference Guide

REST Example: AFT Request

Request: Authorization Service for an AFT

This example is for an account that is configured for relaxed requirements for address data and expiration date.

{
    "clientReferenceInformation": {
        "code": "123456789"
    },
    "merchantInformation": {
        "categoryCode": "4829"
    },
    "orderInformation": {
        "amountDetails": {
            "totalAmount": "10.00",
            "currency": "USD"
        }
    },
    "processingInformation": {
        "businessApplicationId": "AA"
    },
    "paymentInformation": {
        "card": {
            "number": "4111111111111111",
        }
    }
}

Response: Authorization Service for an OCT

{
    "clientReferenceInformation": {
        "code": "123456789"
    },
    "id": "6227448498206943503001",
    "orderInformation": {
        "amountDetails": {
            "totalAmount": "10.00",
            "currency": "USD"
        }
    },
    "processorInformation": {
        "approvalCode": "888888",
        "responseCode": "100"
    },
    "reconciliationId": "737824012PCK87SH",
    "status": "ACCEPTED",
    "submitTimeUtc": "2021-06-03T182730Z"
}

Original Credit Transactions (OCTs)

Original Credit Transactions deliver funds to a recipient's eligible accounts in real-time. OCTs are the second step in transferring funds from an sender to a receiver.

Original Credit Transactions (OCTs)

An OCT deposits funds into a recipient’s account.

Endpoint

Production:

POST https://api.cybersource.com/pts/v2/payments

Test:

POST https://apitest.cybersource.com/pts/v2/payments

Required Fields for an OCT

These fields are required in a request for an OCT:

clientReferenceInformation.code
merchantInformation.merchantDescriptor.contact: Required when the merchant descriptor field is included.; Required for Chase Paymentech Solutions.
merchantInformation.merchantDescriptor.name: Required when the merchant descriptor contact field is included.; Required for Chase Paymentech Solutions.
orderInformation.amountDetails.currency
orderInformation.amountDetails.totalAmount: Cannot exceed 50,000 USD.
paymentInformation.card.expirationMonth
paymentInformation.card.expirationYear
paymentInformation.card.number
processingInformation.businessApplicationId
recipientInformation.firstName
recipientInformation.lastName
senderInformation.account.fundsSource
senderInformation.administrativeArea
senderInformation.lastName: Last name of 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
senderInformation.name
field instead.
senderInformation.locality
senderInformation.name: If the sender is an individual, use the
senderInformation.firstName
and
senderInformation.lastName
fields instead.
senderInformation.postalCode
senderInformation.referenceNumber

REST Example: OCT Request

Request: Authorization Service for an OCT

{
    "clientReferenceInformation": {
        "code": "TC-23456$",
        "requestId": "6642672790803228323604"
    },
    "merchantInformation": {
        "merchantId": "pa_oct_sg101_ccs",
        "merchantDescriptor": {
            "street": "test",
            "state": "CA"
        }
    },
    "orderInformation": {
        "amountDetails": {
            "totalAmount": "0.01",
            "currency": "USD"
        }
    },
    "paymentInformation": {
        "card": {
            "number": "411111111111XXXX",
            "expirationMonth": "12",
            "expirationYear": "2026",
            "type": "001"
        }
    },
    "processingInformation": {
        "businessApplicationId": "aa",
        "icsApplications": "ics_oct"
    },
    "recipientInformation": {
        "name": "RecepientNameRecepientNameName",
        "firstName": "rfirstName",
        "middleName": "rmiddlename",
        "lastName": "rlastname",
        "address": {
            "address1": "test",
            "address2": "test",
            "buildingNumber": "test",
            "city": "test",
            "country": "US",
            "postalCode": "9440",
            "streetName": "test",
            "state": "1"
        }
    },
    "senderInformation": {
        "account": {
            "number": "1234",
            "fundsSource": "03"
        },
        "address": "abc",
        "city": "SenderCitySenderCitySende",
        "country": "Zim",
        "id": "ms_user",
        "referenceNumber": "1",
        "state": "AZ"
    }
}

Response: Authorization Service for an OCT

{
    "clientReferenceInformation": {
        "code": "TC-23456$"
    },
    "id": "7465072232626783103812",
    "orderInformation": {
        "amountDetails": {
            "totalAmount": "0.01",
            "currency": "USD"
        }
    },
    "processorInformation": {
        "approvalCode": "888888",
        "responseCode": "100"
    },
    "reconciliationId": "610954017ABE1KUI",
    "status": "ACCEPTED",
    "submitTimeUtc": "2025-05-06T045343Z"
}

Reference

This section provides helpful reference information for using Payouts services.

Business Application Identifier

The Business Application Identifier (BAI) identifies the category of the Account Funding Transaction (AFT).

All acquirers, service providers, and merchants must submit a valid BAI value when submitting an AFT.

Provide one of the values when you send field

processingInformation.businessApplicationId

.

IMPORTANT

Ensure that your acquirer has a Merchant Category Code (MCC) that corresponds with the BAI value you are using. For more information, contact your acquirer.

Business Application Identifier Values
BAI Value	Category	Requirements
AA	Account-to-Account Money transfer. This value is for funding the cardholder's own account at the same or a different financial institution. Both accounts must be owned by the same person or entity.	NOTE If funding a prepaid account, do not use this value. Use TU instead.
PP	Person-to-Person (P2P) Money Transfer	P2P Money transfer is started from an online banking system, making it a bank-initiated transaction. This category is only used when both AFTs and OCTs are supported. When only AFT is supported, use the FT category.

Payouts Developer Guide

Audience and Purpose

Conventions

Related Documentation

Customer Support

Recent Revisions to This Document

25.05.01

22.06

Introduction to Payouts

Overview

AFT Types

Reversal and Adjustment Transactions

Relaxed Requirements for Address Data and Expiration Date for AFTs

Supported Recipient Card Types, Currencies, Transactions, and BAIs

Payment Networks

Requirements

AFT Transactions

Account Funding Transactions (AFTs)

Endpoint

Required Fields for an AFT Request

Related Information

Optional Fields for an AFT

Related Information

REST Example: AFT Request

Original Credit Transactions (OCTs)

Original Credit Transactions (OCTs)

Endpoint

Required Fields for an OCT

REST Example: OCT Request

Reference

Business Application Identifier

Introduction to `Payouts`

Payment
Networks