On This Page

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:
An
Important
 statement contains information essential to successfully completing a task or learning a concept.

Related Documentation

Visit the
Cybersource
 documentation hub on the Cybersource Developer Center for links to further documentation resources.

Customer Support

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

Recent Revisions to This Document

24.11.01

Added new fields to list of required fields.

24.09.01

Added new fields to the list of required fields.

24.06.01

Reorganized the document.

VISA Platform Connect: Specifications and Conditions for Resellers/Partners

The following are specifications and conditions that apply to a Reseller/Partner enabling its merchants through
Cybersource for
Visa Platform Connect
 (“VPC”) processing
. Failure to meet any of the specifications and conditions below is subject to the liability provisions and indemnification obligations under Reseller/Partner’s contract with Visa/Cybersource.
  1. Before boarding merchants for payment processing on a VPC acquirer’s connection, Reseller/Partner and the VPC acquirer must have a contract or other legal agreement that permits Reseller/Partner to enable its merchants to process payments with the acquirer through the dedicated VPC connection and/or traditional connection with such VPC acquirer.
  2. Reseller/Partner is responsible for boarding and enabling its merchants in accordance with the terms of the contract or other legal agreement with the relevant VPC acquirer.
  3. Reseller/Partner acknowledges and agrees that all considerations and fees associated with chargebacks, interchange downgrades, settlement issues, funding delays, and other processing related activities are strictly between Reseller and the relevant VPC acquirer.
  4. Reseller/Partner acknowledges and agrees that the relevant VPC acquirer is responsible for payment processing issues, including but not limited to, transaction declines by network/issuer, decline rates, and interchange qualification, as may be agreed to or outlined in the contract or other legal agreement between Reseller/Partner and such VPC acquirer.
DISCLAIMER: NEITHER VISA NOR CYBERSOURCE WILL BE RESPONSIBLE OR LIABLE FOR ANY ERRORS OR OMISSIONS BY THE
Visa Platform Connect
 ACQUIRER IN PROCESSING TRANSACTIONS. NEITHER VISA NOR CYBERSOURCE WILL BE RESPONSIBLE OR LIABLE FOR RESELLER/PARTNER BOARDING MERCHANTS OR ENABLING MERCHANT PROCESSING IN VIOLATION OF THE TERMS AND CONDITIONS IMPOSED BY THE RELEVANT
Visa Platform Connect
 ACQUIRER.

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 of Payouts

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, however, 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 transfers funds between accounts owned by the same person.
  • A
    business-to-person
     payment transfers funds between a merchant and a cardholder.
  • A
    person-to-person
     payment transfers 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 known as a
Pull
 service. A subsequent OCT is authorized, and the funds are deposited into the recipient's account. This service is known as 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.
This guide explains only how to process AFTs.
You must receive approval from
Visa Platform Connect
before using the AFT service. Contact
Visa Platform Connect
to register for 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, such as 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.
Issuers can manage AFT refunds as credit adjustments instead of posting the transaction directly into the cardholder's account. Therefore, the time-frame for when the cardholder should expect the refund will vary by issuer.

Aggregator Support for
Payouts

A third-party agents can act as an
aggregator
, or
payment facilitator
, for supported types of
Payouts
 transactions. An aggregator is an organization that aggregates
Payouts
 transactions for a group of sub-merchants under a single account, processing card transactions and settling funds directly to sub-merchants' bank accounts. An aggregator can be a merchant, an independent sales organization (ISO), or a member service provider (MSP). When aggregation is enabled,
Cybersource
 can send payment facilitator information about a transaction that involves the facilitator.
To have your account configured for this feature, contact customer support.

Supported Card Types

Recipient card type for AFTs:
  • Mastercard
  • Visa
These card types are supported :
  • Mastercard
  • Visa

Payment
Networks

Visa Direct
The Visa Direct payment network provides these functions for
Payouts
:
  • Enhanced message types 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 process Payouts services, you must meet these requirements:
  • Obtain approval from your acquirer for requesting this type of transaction.
  • Use your merchant category code.
  • The amount must be less than or equal to 50,000 USD, unless otherwise noted. Amount limits might differ as required by local laws, local regulations, and limitations imposed by your acquirer. Contact your acquirer for more information.

Introduction to OCT

The Original Credit Transaction (OCT) is a VisaNet transaction that delivers funds directly to a recipient's eligible Visa card. You cannot use OCTs alone to buy goods or services, except in Request to Pay Consumer-to-Small-Business (C2B) cases. OCTs do not allow merchandise return credits or refunds, except by exception or according to Visa rule #0008771.
You must differentiate between OCT processing and merchandise credit refund processing. If you do not, it could lead to issues such as the reversal of reward points.
These are Visa Direct services that use OCT:
  • Money Transfer
  • Funds Disbursement
  • Merchant Settlement
  • Digital Wallets
  • Real-Time Deposit/Check Deposit
  • Loyalty and Offers
  • Prepaid Load
  • Credit Card Bill Payment

Money Transfer

This service enables customers to send funds to their Visa account or another customer's Visa account.

Funds Disbursement

This service allows you, government entities, or corporations to send funds to a Visa account. Examples include insurance claims, corporate and manufacturing rebates, affiliate and contractor payouts, expense reimbursements, government disbursements (such as value-added tax refunds), and online gambling and lottery payouts.
This service is available based on laws, current Visa policy, and the Visa rules.

Merchant Settlement

This services allows acquirers or third-party service providers to speed up settlement payments between acquirers or payment facilitators and you.

Digital Wallets

This service enables faster payments through digital or electronic wallet services. You can move funds out of a digital wallet and deliver them to a cardholder's Visa account. This is considered a Money Transfer transaction for risk-control purposes in the Visa processing network. A Staged Digital Wallet (SDW) functions as a brand acceptance mark.
Contact your Visa representative for more information and requirements on digital wallets. For more details on digital wallet transactions, visit the Staged Digital Wallet Operators (SDWO) section at Visa Access (Visa Online).

Real-Time Deposit/Check Deposit

This service converts a check into a digital payment delivered to a cardholder's Visa account.

Loyalty and Offers

This service pays a loyalty reward or merchant offer onto a card using OCT as part of a loyalty program.

Prepaid Load

This service enables customers to add value to an eligible Visa reloadable prepaid card.
The US market currently supports a separate prepaid load service called Visa ReadyLink. For more information on Visa ReadyLink, contact your Visa representative.

Credit Card Bill Payment

This service enables consumers to pay a credit card bill.
When using OCT supported by Visa Direct, you can only use Visa data, like transaction data, reports, and the Visa Direct Account Lookup (ACNL), to operate the Visa program. You cannot use this data for any other purpose.

Visa Card Types and Services for OCT

Visa card types include reloadable prepaid, deferred debit, debit, credit, and combo cards, each with specific OCT functionalities. OCTs can increase balances or serve as payments, depending on the card type and account setup. These services apply to both domestic and cross-border transactions, supporting money transfers, funds disbursement, prepaid loads, and credit card bill payments.

Visa Card Types

These are the different Visa card types, descriptions, and examples:
Visa Reloadable Prepaid
An OCT to an eligible Visa prepaid card increases the prepaid card balance.
If the prepaid card balance is 25 USD and the OCT received is for 100 USD, the new prepaid balance is 125 USD.
Visa Deferred Debit
Deferred Debit cards have a line of credit and an underlying bank account. An OCT to a Visa Deferred Debit card deposits funds into the underlying account when both the line of credit and underlying account are with the same bank. If the Deferred Debit card underlying account is with a different bank than the line of credit, post the funds to the card account.
If the underlying account has a balance of 800 USD and an OCT for 100 USD is received to the card, the new account balance is 900 USD. The credit balance owed on the card is not impacted by the receipt of the OCT. If the card has a balance owed of 200 USD and an OCT for 100 USD is received, the payment of USD 100 will be posted to the credit account. The new outstanding balance would be USD 100.
Visa Debit
An OCT to a Visa debit card increases the balance of the underlying bank account associated with the Visa debit card.
If the card balance is 800 USD and the OCT received is for 100 USD, the new account balance is 900 USD.
Visa Credit
An OCT to a Visa credit card serves as a payment to the account.
If the amount owed on the card is 800 USD and an OCT for 100 USD is received to the card, a payment of USD 100 will be posted to the account. The new outstanding balance is 700 USD.
Visa Combo Card (Brazil)
Combo cards allow cardholders to use credit or debit functionality during a transaction. An OCT to a Visa Combo card processed as debit increases the balance of the underlying deposit account linked to the card.
The credit balance owed on the card is not impacted by the receipt of the OCT. Funds are applied only to the debit balance in the deposit account. Do not present the OCT for combo cards as credit using the proper values.
If the deposit account linked to the card has a balance of 800 USD, and an OCT for 100 USD is received to the account, the new account balance is USD 900.

OCT Services

See the table for an overview of Visa's Original Credit Transaction (OCT) services, key features and benefits:
OCT Services
Destination Visa Account Types
Visa Credit
Destination Visa Account Types
Visa Debit
Destination Visa Account Types
Visa Prepaid
Geographic Scope
Domestic
Geographic Scope
Cross-Border
Money Transfer (includes digital wallet and instant deposits)
X
X
X
X
X
Funds Disbursement (includes merchant settlement and Loyalty and Offers)
X
X
X
X
X
Prepaid Load
X
X
Credit Card Bill Payment
X
X

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 to pay for goods and services, fund a merchant account, or repay debts.
You must receive approval from
Visa Platform Connect
before using the AFT services. Contact
Visa Platform Connect
to register in the AFT program.

Dual Message Account Funding Transactions (AFTs)

Account Funding Transactions allow a payment service provider to debit funds from a cardholder's Mastercard or Visa account to fund a non-merchant account. This is typically used to load funds onto prepaid cards and electronic wallets.
Dual Message Account Funding Transactions (AFTs) provide the following benefits:
  • Enables customers to identify Mastercard and Visa transactions during the authorization and settlement.
  • Allows acquiring partners to use Dual Message BINs when performing a payout transaction.

Endpoint

Set the
ccAuthService_run
 field to
true
.
Send the request to
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
.

Simple Order Example: Dual-Message AFT

Request
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Header>
        <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
            <wsse:UsernameToken>
                <wsse:Username>en_vdcuruguay_1_ccs</wsse:Username>
                <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">ygx8jlKyl6nZlY67dH4kKo4VZm6T9j3wV2WNA1j+44NoCkFlrJFFkklShtTCSAKG5xCbiFPZJwvuNlEO9zokZUhOOYNvYcKza+XT+O2ZlYhJ6EfkCsmAuVtHqpCXfIVoTOszxh64maLeO5fX0+FoVRuduB+83X0+82iQP2B0ObYPykL2MPZtlFcz4JmM9JAJGYqvo2llkZHPrQrkhoDddKBs5gcWZwZ/VugdvYmdTLZg3f2afiAc8DlTUQ7lwqck5wkVgitkBSJe3ZuhviPTE8zRL31pI+MP4AmV5ujuR+SAHtGFew9rWye9OKpig5mKgMDA+3r0vUbbGiaWbfo1mA==</wsse:Password>
            </wsse:UsernameToken>
        </wsse:Security>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
        <requestMessage xmlns="urn:schemas-cybersource-com:transaction-data-1.221">
            <merchantID>en_vdcuruguay_1_ccs</merchantID>
            <merchantReferenceCode>TC55255-1</merchantReferenceCode>
            <invoiceHeader>
                <merchantDescriptor>John</merchantDescriptor>
                <merchantDescriptorStreet>cr avenue</merchantDescriptorStreet>
                <merchantDescriptorState>CA</merchantDescriptorState>
                <merchantVATRegistrationNumber>15426476537657</merchantVATRegistrationNumber>
                <businessApplicationID>AA</businessApplicationID>
                <invoiceNumber>13490</invoiceNumber>
            </invoiceHeader>
            <billTo>
                <firstName>JHON</firstName>
                <lastName>SMITH</lastName>
                <street1>1-26-28 Nakashirane,</street1>
                <street2>Asahi-ku</street2>
                <street3>Suite 500</street3>
                <city>Yokohama-shi</city>
                <state>CA</state>
                <postalCode>602-8511</postalCode>
                <country>US</country>
                <phoneNumber>999-123-9999</phoneNumber>
                <email>test@visa.com</email>
            </billTo>
            <purchaseTotals>
                <currency>USD</currency>
                <grandTotalAmount>100</grandTotalAmount>
                <invoiceAmount>1234</invoiceAmount>
            </purchaseTotals>
            <card>
                <accountNumber>4111111111111111</accountNumber>
                <expirationMonth>12</expirationMonth>
                <expirationYear>2030</expirationYear>
                <cvNumber>123</cvNumber>
                <cardType>001</cardType>
            </card>
            <ccAuthService run="true">
                <commerceIndicator>internet</commerceIndicator>
                <aggregatorName>Test</aggregatorName>
                <captureDate>1231</captureDate>
                <purposeOfPayment>16</purposeOfPayment>
                <initiatorType>S</initiatorType>
            </ccAuthService>
            <surchargeAmount>5</surchargeAmount>
            <surchargeSign>c</surchargeSign>
            <recipient>
                <postalCode>222120</postalCode>
                <accountID>987654321</accountID>
                <accountType>33</accountType>
                <lastName>last</lastName>
                <firstName>firstname</firstName>
                <address>this is address1</address>
                <city>Newyork</city>
                <country>US</country>
                <buildingNumber>266</buildingNumber>
                <address2>this is address2</address2>
                <streetName>colourful Street</streetName>
            </recipient>
            <sender>
                <referenceNumber>REFNUM123</referenceNumber>
                <sourceOfFunds>02</sourceOfFunds>
                <name>justsenderName</name>
                <address>addressofthesender</address>
                <city>Newyork</city>
                <state>ca</state>
                <country>US</country>
                <accountNumber>154264765376576126571652675176</accountNumber>
                <firstName>Senderfirst</firstName>
                <lastName>Senderlast</lastName>
                <personalIDType>TXIN</personalIDType>
                <type>B</type>
                <identificationNumber>23506907642323235</identificationNumber>
            </sender>
            <aft>
                <indicator>true</indicator>
                <foreignExchangeFee>12</foreignExchangeFee>
            </aft>
        </requestMessage>
    </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Response
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Header>
        <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
            <wsu:Timestamp wsu:Id="TS-6cf9b37e-72df-4a5d-bc6e-d091ce9bb8a4">
                <wsu:Created>2024-06-26T05:21:10.390Z</wsu:Created>
            </wsu:Timestamp>
        </wsse:Security>
    </soap:Header>
    <soap:Body>
        <c:replyMessage xmlns:c="urn:schemas-cybersource-com:transaction-data-1.221">
            <c:merchantReferenceCode>TC55255-1</c:merchantReferenceCode>
            <c:requestID>7193792686247001309916</c:requestID>
            <c:decision>ACCEPT</c:decision>
            <c:reasonCode>100</c:reasonCode>
            <c:requestToken>Axj/7wSThfntrctjncLcAHgs3YuWbdyybOGzJo3YMGLNg5csWybWNLQsAAU2saWhYBpA6cQQUYZNv/sXFU8Q64E5OF+e2ty2OdwtwAAA5xPu</c:requestToken>
            <c:purchaseTotals>
                <c:currency>USD</c:currency>
            </c:purchaseTotals>
            <c:ccAuthReply>
                <c:reasonCode>100</c:reasonCode>
                <c:amount>100.00</c:amount>
                <c:authorizationCode>831000</c:authorizationCode>
                <c:avsCode>Y</c:avsCode>
                <c:avsCodeRaw>Y</c:avsCodeRaw>
                <c:cvCode>M</c:cvCode>
                <c:cvCodeRaw>M</c:cvCodeRaw>
                <c:authorizedDateTime>2024-06-26T05:21:10Z</c:authorizedDateTime>
                <c:processorResponse>00</c:processorResponse>
                <c:reconciliationID>7193792686247001309916</c:reconciliationID>
                <c:merchantAdviceCode>01</c:merchantAdviceCode>
                <c:merchantAdviceCodeRaw>M001</c:merchantAdviceCodeRaw>
                <c:cavvResponseCode>2</c:cavvResponseCode>
                <c:cavvResponseCodeRaw>2</c:cavvResponseCodeRaw>
                <c:paymentNetworkTransactionID>016153570198200</c:paymentNetworkTransactionID>
                <c:reconciliationReferenceNumber>417805815972</c:reconciliationReferenceNumber>
            </c:ccAuthReply>
            <c:receiptNumber>815972</c:receiptNumber>
            <c:additionalData>ABC</c:additionalData>
            <c:card>
                <c:cardType>001</c:cardType>
            </c:card>
            <c:reserved>
                <ics_message xmlns="urn:schemas-cybersource-com:transaction-data:ics">
                    <ics_decision_reason_code>100</ics_decision_reason_code>
                    <auth_payment_network_transaction_id>016153570198200</auth_payment_network_transaction_id>
                    <auth_rcode>1</auth_rcode>
                    <receipt_number>815972</receipt_number>
                    <ics_return_code>1000000</ics_return_code>
                    <auth_merchant_advice_code>01</auth_merchant_advice_code>
                    <ics_rcode>1</ics_rcode>
                    <auth_cavv_response_code>2</auth_cavv_response_code>
                    <auth_auth_response>00</auth_auth_response>
                    <auth_rmsg>Request was processed successfully.</auth_rmsg>
                    <merchant_ref_number>TC55255-1</merchant_ref_number>
                    <auth_merchant_advice_code_raw>M001</auth_merchant_advice_code_raw>
                    <currency>USD</currency>
                    <auth_auth_code>831000</auth_auth_code>
                    <auth_auth_amount>100.00</auth_auth_amount>
                    <auth_cv_result_raw>M</auth_cv_result_raw>
                    <auth_fee_program_indicator>123</auth_fee_program_indicator>
                    <card_type>001</card_type>
                    <auth_additional_token_response_information>0</auth_additional_token_response_information>
                    <ics_rmsg>Request was processed successfully.</ics_rmsg>
                    <auth_trans_ref_no>7193792686247001309916</auth_trans_ref_no>
                    <request_id>7193792686247001309916</request_id>
                    <auth.reason_code>100</auth.reason_code>
                    <auth_cavv_response_code_raw>2</auth_cavv_response_code_raw>
                    <auth_auth_time>2024-06-26T052110Z</auth_auth_time>
                    <auth_rflag>SOK</auth_rflag>
                    <auth_cv_result>M</auth_cv_result>
                    <auth_return_code>1010000</auth_return_code>
                    <auth_avs_raw>Y</auth_avs_raw>
                    <ics_rflag>SOK</ics_rflag>
                    <auth_reconciliation_reference_number>417805815972</auth_reconciliation_reference_number>
                    <auth_auth_avs>Y</auth_auth_avs>
                    <request_token>Axj/7wSThfntrctjncLcAHgs3YuWbdyybOGzJo3YMGLNg5csWybWNLQsAAU2saWhYBpA6cQQUYZNv/sXFU8Q64E5OF+e2ty2OdwtwAAA5xPu</request_token>
                    <additional_data>ABC</additional_data>
                </ics_message>
            </c:reserved>
            <c:additionalToken>
                <c:responseInformation>0</c:responseInformation>
            </c:additionalToken>
        </c:replyMessage>
    </soap:Body>
</soap:Envelope>

Dual Message Account Funding Transactions (AFTs) with Visa Secure

Account Funding Transactions allow a payment service provider to debit funds from a cardholder's Mastercard or Visa account to fund a non-merchant account. This is typically used to load funds onto prepaid cards and electronic wallets.
Dual Message Account Funding Transactions (AFTs) provide the following benefits:
  • Enables customers to identify Mastercard and Visa transactions during the authorization and settlement.
  • Allows acquiring partners to use Dual Message BINs when performing a payout transaction.
  • Enables users to safely validate their identity and safely store their personal identity.

Endpoint

Set the
ccAuthService_run
 field to
true
.
Send the request to
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
.

Required Fields for a Dual-Message AFT with Visa Secure Request

These fields are required to process a dual-message AFT with Visa Secure request:
invoiceHeader_invoiceNumber
purchaseTotals_invoiceAmount

Simple Order Example: Dual-Message AFT with Visa Secure

Request
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Header>
        <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
            <wsse:UsernameToken>
                <wsse:Username>en_vdcuruguay_1_ccs</wsse:Username>
                <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">ygx8jlKyl6nZlY67dH4kKo4VZm6T9j3wV2WNA1j+44NoCkFlrJFFkklShtTCSAKG5xCbiFPZJwvuNlEO9zokZUhOOYNvYcKza+XT+O2ZlYhJ6EfkCsmAuVtHqpCXfIVoTOszxh64maLeO5fX0+FoVRuduB+83X0+82iQP2B0ObYPykL2MPZtlFcz4JmM9JAJGYqvo2llkZHPrQrkhoDddKBs5gcWZwZ/VugdvYmdTLZg3f2afiAc8DlTUQ7lwqck5wkVgitkBSJe3ZuhviPTE8zRL31pI+MP4AmV5ujuR+SAHtGFew9rWye9OKpig5mKgMDA+3r0vUbbGiaWbfo1mA==</wsse:Password>
            </wsse:UsernameToken>
        </wsse:Security>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
        <requestMessage xmlns="urn:schemas-cybersource-com:transaction-data-1.221">
            <merchantID>en_vdcuruguay_1_ccs</merchantID>
            <merchantReferenceCode>TC55255-1</merchantReferenceCode>
            <invoiceHeader>
                <merchantDescriptor>John</merchantDescriptor>
                <merchantDescriptorStreet>cr avenue</merchantDescriptorStreet>
                <merchantDescriptorState>CA</merchantDescriptorState>
                <merchantVATRegistrationNumber>15426476537657</merchantVATRegistrationNumber>
                <businessApplicationID>WT</businessApplicationID>
                <invoiceNumber>13490</invoiceNumber>
            </invoiceHeader>
            <billTo>
                <firstName>JHON</firstName>
                <lastName>SMITH</lastName>
                <street1>1-26-28 Nakashirane,</street1>
                <street2>Asahi-ku</street2>
                <street3>Suite 500</street3>
                <city>Yokohama-shi</city>
                <state>CA</state>
                <postalCode>602-8511</postalCode>
                <country>US</country>
                <phoneNumber>999-123-9999</phoneNumber>
                <email>test@visa.com</email>
            </billTo>
            <purchaseTotals>
                <currency>USD</currency>
                <grandTotalAmount>100</grandTotalAmount>
                <invoiceAmount>1234</invoiceAmount>
            </purchaseTotals>
            <card>
                <accountNumber>4111111111111111</accountNumber>
                <expirationMonth>12</expirationMonth>
                <expirationYear>2030</expirationYear>
                <cvNumber>123</cvNumber>
                <cardType>001</cardType>
            </card>
            <ccAuthService run="true">
                <cavv>ABCDEabcde12345678900987654321abcdeABCDE</cavv>
                <commerceIndicator>vbv</commerceIndicator>
                <xid>12345678909876543210ABCDEabcdeABCDEF1234</xid>
                <aggregatorName>Test</aggregatorName>
                <captureDate>1231</captureDate>
                <purposeOfPayment>16</purposeOfPayment>
                <initiatorType>S</initiatorType>
            </ccAuthService>
            <surchargeAmount>5</surchargeAmount>
            <surchargeSign>c</surchargeSign>
            <recipient>
                <postalCode>222120</postalCode>
                <accountID>987654321</accountID>
                <accountType>33</accountType>
                <lastName>last</lastName>
                <firstName>firstname</firstName>
                <middleName>middlename</middleName>
                <address>this is address1</address>
                <city>Newyork</city>
                <country>US</country>
                <buildingNumber>266</buildingNumber>
                <address2>this is address2</address2>
                <streetName>colourful Street</streetName>
            </recipient>
            <sender>
                <referenceNumber>REFNUM123</referenceNumber>
                <sourceOfFunds>02</sourceOfFunds>
                <name>justsenderName</name>
                <address>addressofthesender</address>
                <city>Newyork</city>
                <state>ca</state>
                <country>US</country>
                <accountNumber>154264765376576126571652675176</accountNumber>
                <firstName>Senderfirst</firstName>
                <middleName>SenderMiddle</middleName>
                <lastName>Senderlast</lastName>
                <personalIDType>TXIN</personalIDType>
                <type>B</type>
                <identificationNumber>23506907642323235</identificationNumber>
            </sender>
            <aft>
                <indicator>true</indicator>
                <foreignExchangeFee>12</foreignExchangeFee>
            </aft>
            <subsequentAuthStoredCredential>false</subsequentAuthStoredCredential>
        </requestMessage>
    </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Response
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Header>
        <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
            <wsu:Timestamp wsu:Id="TS-bd54e9f8-d34b-4ed7-86ea-82d57d621f81">
                <wsu:Created>2024-06-26T04:59:00.800Z</wsu:Created>
            </wsu:Timestamp>
        </wsse:Security>
    </soap:Header>
    <soap:Body>
        <c:replyMessage xmlns:c="urn:schemas-cybersource-com:transaction-data-1.221">
            <c:merchantReferenceCode>TC55255-1</c:merchantReferenceCode>
            <c:requestID>7193779389647000909916</c:requestID>
            <c:decision>ACCEPT</c:decision>
            <c:reasonCode>100</c:reasonCode>
            <c:requestToken>Axj/7wSThfm+cJtz3zhcAHgs3YuWbdu5ZuHLZo3YMGDlg5csWybWNLQr8AU2saWhX5pA6cQQUYZNv/sXFU8Q64E5OF+b5wm3PfOFwAAAwSA7</c:requestToken>
            <c:purchaseTotals>
                <c:currency>USD</c:currency>
            </c:purchaseTotals>
            <c:ccAuthReply>
                <c:reasonCode>100</c:reasonCode>
                <c:amount>100.00</c:amount>
                <c:authorizationCode>831000</c:authorizationCode>
                <c:avsCode>Y</c:avsCode>
                <c:avsCodeRaw>Y</c:avsCodeRaw>
                <c:cvCode>M</c:cvCode>
                <c:cvCodeRaw>M</c:cvCodeRaw>
                <c:authorizedDateTime>2024-06-26T04:59:00Z</c:authorizedDateTime>
                <c:processorResponse>00</c:processorResponse>
                <c:reconciliationID>7193779389647000909916</c:reconciliationID>
                <c:merchantAdviceCode>01</c:merchantAdviceCode>
                <c:merchantAdviceCodeRaw>M001</c:merchantAdviceCodeRaw>
                <c:cavvResponseCode>2</c:cavvResponseCode>
                <c:cavvResponseCodeRaw>2</c:cavvResponseCodeRaw>
                <c:paymentNetworkTransactionID>016153570198200</c:paymentNetworkTransactionID>
                <c:reconciliationReferenceNumber>417804815945</c:reconciliationReferenceNumber>
            </c:ccAuthReply>
            <c:receiptNumber>815945</c:receiptNumber>
            <c:additionalData>ABC</c:additionalData>
            <c:card>
                <c:cardType>001</c:cardType>
            </c:card>
            <c:reserved>
                <ics_message xmlns="urn:schemas-cybersource-com:transaction-data:ics">
                    <ics_decision_reason_code>100</ics_decision_reason_code>
                    <auth_payment_network_transaction_id>016153570198200</auth_payment_network_transaction_id>
                    <auth_rcode>1</auth_rcode>
                    <receipt_number>815945</receipt_number>
                    <ics_return_code>1000000</ics_return_code>
                    <auth_merchant_advice_code>01</auth_merchant_advice_code>
                    <ics_rcode>1</ics_rcode>
                    <auth_cavv_response_code>2</auth_cavv_response_code>
                    <auth_auth_response>00</auth_auth_response>
                    <auth_rmsg>Request was processed successfully.</auth_rmsg>
                    <merchant_ref_number>TC55255-1</merchant_ref_number>
                    <auth_merchant_advice_code_raw>M001</auth_merchant_advice_code_raw>
                    <currency>USD</currency>
                    <auth_auth_code>831000</auth_auth_code>
                    <auth_auth_amount>100.00</auth_auth_amount>
                    <auth_cv_result_raw>M</auth_cv_result_raw>
                    <auth_fee_program_indicator>123</auth_fee_program_indicator>
                    <card_type>001</card_type>
                    <auth_additional_token_response_information>0</auth_additional_token_response_information>
                    <ics_rmsg>Request was processed successfully.</ics_rmsg>
                    <auth_trans_ref_no>7193779389647000909916</auth_trans_ref_no>
                    <request_id>7193779389647000909916</request_id>
                    <auth.reason_code>100</auth.reason_code>
                    <auth_cavv_response_code_raw>2</auth_cavv_response_code_raw>
                    <auth_auth_time>2024-06-26T045900Z</auth_auth_time>
                    <auth_rflag>SOK</auth_rflag>
                    <auth_cv_result>M</auth_cv_result>
                    <auth_return_code>1010000</auth_return_code>
                    <auth_avs_raw>Y</auth_avs_raw>
                    <ics_rflag>SOK</ics_rflag>
                    <auth_reconciliation_reference_number>417804815945</auth_reconciliation_reference_number>
                    <auth_auth_avs>Y</auth_auth_avs>
                    <request_token>Axj/7wSThfm+cJtz3zhcAHgs3YuWbdu5ZuHLZo3YMGDlg5csWybWNLQr8AU2saWhX5pA6cQQUYZNv/sXFU8Q64E5OF+b5wm3PfOFwAAAwSA7</request_token>
                    <additional_data>ABC</additional_data>
                </ics_message>
            </c:reserved>
            <c:additionalToken>
                <c:responseInformation>0</c:responseInformation>
            </c:additionalToken>
        </c:replyMessage>
    </soap:Body>
</soap:Envelope>

Dual Message Account Funding Transactions (AFTs) with Visa Secure for Merchant Aggregators

Account Funding Transactions allow a payment service provider to debit funds from a cardholder's Mastercard or Visa account to fund a non-merchant account. This is typically used to load funds onto prepaid cards and electronic wallets.
Dual Message Account Funding Transactions (AFTs) provide the following benefits:
  • Enables customers to identify Mastercard and Visa transactions during the authorization and settlement.
  • Allows acquiring partners to use Dual Message BINs when performing a payout transaction.
  • Enables users to safely validate their identity and safely store their personal identity.

Endpoint

Set the
ccAuthService_run
 field to
true
.
Send the request to
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
.

Required Fields for a Dual-Message AFT with Visa Secure for Merchant Aggregators Request

These fields are required to process a dual-message AFT with Visa Secure for merchant aggregators request:
invoiceHeader_invoiceNumber
purchaseTotals_invoiceAmount

Simple Order Example: Dual-Message AFT with Visa Secure for Merchant Aggregators

Request
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Header>
        <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
            <wsse:UsernameToken>
                <wsse:Username>en_vdcuruguay_1_ccs</wsse:Username>
                <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">ygx8jlKyl6nZlY67dH4kKo4VZm6T9j3wV2WNA1j+44NoCkFlrJFFkklShtTCSAKG5xCbiFPZJwvuNlEO9zokZUhOOYNvYcKza+XT+O2ZlYhJ6EfkCsmAuVtHqpCXfIVoTOszxh64maLeO5fX0+FoVRuduB+83X0+82iQP2B0ObYPykL2MPZtlFcz4JmM9JAJGYqvo2llkZHPrQrkhoDddKBs5gcWZwZ/VugdvYmdTLZg3f2afiAc8DlTUQ7lwqck5wkVgitkBSJe3ZuhviPTE8zRL31pI+MP4AmV5ujuR+SAHtGFew9rWye9OKpig5mKgMDA+3r0vUbbGiaWbfo1mA==</wsse:Password>
            </wsse:UsernameToken>
        </wsse:Security>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
        <requestMessage xmlns="urn:schemas-cybersource-com:transaction-data-1.221">
            <merchantID>en_vdcuruguay_1_ccs</merchantID>
            <merchantReferenceCode>TC55255-1</merchantReferenceCode>
            <invoiceHeader>
                <merchantDescriptor>John</merchantDescriptor>
                <merchantDescriptorStreet>cr avenue</merchantDescriptorStreet>
                <merchantDescriptorState>CA</merchantDescriptorState>
                <merchantVATRegistrationNumber>15426476537657</merchantVATRegistrationNumber>
                <businessApplicationID>AA</businessApplicationID>
                <submerchantID>1212345444</submerchantID>
                <submerchantName>Vibin</submerchantName>
                <submerchantCity>Mumbai</submerchantCity>
                <invoiceNumber>13490</invoiceNumber>
            </invoiceHeader>
            <billTo>
                <firstName>JHON</firstName>
                <lastName>SMITH</lastName>
                <street1>1-26-28 Nakashirane,</street1>
                <street2>Asahi-ku</street2>
                <street3>Suite 500</street3>
                <city>Yokohama-shi</city>
                <state>CA</state>
                <postalCode>602-8511</postalCode>
                <country>US</country>
                <phoneNumber>999-123-9999</phoneNumber>
                <email>test@visa.com</email>
            </billTo>
            <purchaseTotals>
                <currency>USD</currency>
                <grandTotalAmount>100</grandTotalAmount>
                <invoiceAmount>1234</invoiceAmount>
            </purchaseTotals>
            <card>
                <accountNumber>4111111111111111</accountNumber>
                <expirationMonth>12</expirationMonth>
                <expirationYear>2030</expirationYear>
                <cvNumber>123</cvNumber>
                <cardType>001</cardType>
            </card>
            <ccAuthService run="true">
                <cavv>ABCDEabcde12345678900987654321abcdeABCDE</cavv>
                <commerceIndicator>vbv</commerceIndicator>
                <xid>12345678909876543210ABCDEabcdeABCDEF1234</xid>
                <aggregatorID>123456789</aggregatorID>
                <aggregatorName>aggregatorname</aggregatorName>
                <captureDate>1231</captureDate>
                <purposeOfPayment>16</purposeOfPayment>
                <initiatorType>S</initiatorType>
            </ccAuthService>
            <surchargeAmount>5</surchargeAmount>
            <surchargeSign>c</surchargeSign>
            <recipient>
                <postalCode>222120</postalCode>
                <accountID>987654321</accountID>
                <accountType>33</accountType>
                <lastName>last</lastName>
                <firstName>firstname</firstName>
                <middleName>recmiddle</middleName>
                <address>this is address1</address>
                <city>westb</city>
                <country>IN</country>
                <buildingNumber>266</buildingNumber>
                <address2>this is address2</address2>
                <streetName>colourful Street</streetName>
            </recipient>
            <sender>
                <referenceNumber>REFNUM123</referenceNumber>
                <sourceOfFunds>02</sourceOfFunds>
                <name>justsenderName</name>
                <address>addressofthesender</address>
                <city>frankfort</city>
                <state>GR</state>
                <country>GERMANY</country>
                <accountNumber>154264765376576126571652675176</accountNumber>
                <firstName>vibin</firstName>
                <middleName>andy</middleName>
                <lastName>vibin</lastName>
                <personalIDType>TXIN</personalIDType>
                <type>B</type>
                <identificationNumber>23506907642323235</identificationNumber>
            </sender>
            <aft>
                <indicator>true</indicator>
                <foreignExchangeFee>12</foreignExchangeFee>
            </aft>
            <subsequentAuthStoredCredential>false</subsequentAuthStoredCredential>
        </requestMessage>
    </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Response
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Header>
        <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
            <wsu:Timestamp wsu:Id="TS-3615fe53-22ac-4176-8643-ab44ba96a150">
                <wsu:Created>2024-06-26T09:30:07.396Z</wsu:Created>
            </wsu:Timestamp>
        </wsse:Security>
    </soap:Header>
    <soap:Body>
        <c:replyMessage xmlns:c="urn:schemas-cybersource-com:transaction-data-1.221">
            <c:merchantReferenceCode>TC55255-1</c:merchantReferenceCode>
            <c:requestID>7193942058427002309916</c:requestID>
            <c:decision>ACCEPT</c:decision>
            <c:reasonCode>100</c:reasonCode>
            <c:requestToken>Axj/7wSThfwAWwAz5s0cAHgs3YuWbloyYNXDRk3YMGTNg5csWybWNLREYAU2saWiIxpA6cQQUoZNv/sXFU8Q64E5OF/ABbADPmzRwAAAXxOW</c:requestToken>
            <c:purchaseTotals>
                <c:currency>USD</c:currency>
            </c:purchaseTotals>
            <c:ccAuthReply>
                <c:reasonCode>100</c:reasonCode>
                <c:amount>100.00</c:amount>
                <c:authorizationCode>831000</c:authorizationCode>
                <c:avsCode>Y</c:avsCode>
                <c:avsCodeRaw>Y</c:avsCodeRaw>
                <c:cvCode>M</c:cvCode>
                <c:cvCodeRaw>M</c:cvCodeRaw>
                <c:authorizedDateTime>2024-06-26T09:30:07Z</c:authorizedDateTime>
                <c:processorResponse>00</c:processorResponse>
                <c:reconciliationID>7193942058427002309916</c:reconciliationID>
                <c:merchantAdviceCode>01</c:merchantAdviceCode>
                <c:merchantAdviceCodeRaw>M001</c:merchantAdviceCodeRaw>
                <c:cavvResponseCode>2</c:cavvResponseCode>
                <c:cavvResponseCodeRaw>2</c:cavvResponseCodeRaw>
                <c:paymentNetworkTransactionID>016153570198200</c:paymentNetworkTransactionID>
                <c:reconciliationReferenceNumber>417809816229</c:reconciliationReferenceNumber>
            </c:ccAuthReply>
            <c:receiptNumber>816229</c:receiptNumber>
            <c:additionalData>ABC</c:additionalData>
            <c:card>
                <c:cardType>001</c:cardType>
            </c:card>
            <c:reserved>
                <ics_message xmlns="urn:schemas-cybersource-com:transaction-data:ics">
                    <ics_decision_reason_code>100</ics_decision_reason_code>
                    <auth_payment_network_transaction_id>016153570198200</auth_payment_network_transaction_id>
                    <auth_rcode>1</auth_rcode>
                    <receipt_number>816229</receipt_number>
                    <ics_return_code>1000000</ics_return_code>
                    <auth_merchant_advice_code>01</auth_merchant_advice_code>
                    <ics_rcode>1</ics_rcode>
                    <auth_cavv_response_code>2</auth_cavv_response_code>
                    <auth_auth_response>00</auth_auth_response>
                    <auth_rmsg>Request was processed successfully.</auth_rmsg>
                    <merchant_ref_number>TC55255-1</merchant_ref_number>
                    <auth_merchant_advice_code_raw>M001</auth_merchant_advice_code_raw>
                    <currency>USD</currency>
                    <auth_auth_code>831000</auth_auth_code>
                    <auth_auth_amount>100.00</auth_auth_amount>
                    <auth_cv_result_raw>M</auth_cv_result_raw>
                    <auth_fee_program_indicator>123</auth_fee_program_indicator>
                    <card_type>001</card_type>
                    <auth_additional_token_response_information>0</auth_additional_token_response_information>
                    <ics_rmsg>Request was processed successfully.</ics_rmsg>
                    <auth_trans_ref_no>7193942058427002309916</auth_trans_ref_no>
                    <request_id>7193942058427002309916</request_id>
                    <auth.reason_code>100</auth.reason_code>
                    <auth_cavv_response_code_raw>2</auth_cavv_response_code_raw>
                    <auth_auth_time>2024-06-26T093007Z</auth_auth_time>
                    <auth_rflag>SOK</auth_rflag>
                    <auth_cv_result>M</auth_cv_result>
                    <auth_return_code>1010000</auth_return_code>
                    <auth_avs_raw>Y</auth_avs_raw>
                    <ics_rflag>SOK</ics_rflag>
                    <auth_reconciliation_reference_number>417809816229</auth_reconciliation_reference_number>
                    <auth_auth_avs>Y</auth_auth_avs>
                    <request_token>Axj/7wSThfwAWwAz5s0cAHgs3YuWbloyYNXDRk3YMGTNg5csWybWNLREYAU2saWiIxpA6cQQUoZNv/sXFU8Q64E5OF/ABbADPmzRwAAAXxOW</request_token>
                    <additional_data>ABC</additional_data>
                </ics_message>
            </c:reserved>
            <c:additionalToken>
                <c:responseInformation>0</c:responseInformation>
            </c:additionalToken>
        </c:replyMessage>
    </soap:Body>
</soap:Envelope>

Dual Message Account Funding Transactions (AFTs) with Network Tokens

Account Funding Transactions allow a payment service provider to debit funds from a cardholder's Mastercard or Visa account to fund a non-merchant account. This is typically used to load funds onto prepaid cards and electronic wallets.
Dual Message Account Funding Transactions (AFTs) with Network Tokens provide the following benefits:
  • Enables customers to identify Mastercard and Visa transactions during the authorization and settlement.
  • Allows acquiring partners to use Dual Message BINs when performing a payout transaction.
  • Increases the security with payout transactions.
  • Decreases the chances of fraudulent transactions

Endpoint

Set the
ccAuthService_run
 field to
true
.
Send the request to
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
.

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:
This field is only required when you have received an XID value in a previous transaction.
invoiceHeader_invoiceNumber
purchaseTotals_invoiceAmount

Simple Order Example: Dual-Message AFT with Network Tokens

Request
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Header>
        <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
            <wsse:UsernameToken>
                <wsse:Username>en_vdcuruguay_1_ccs</wsse:Username>
                <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">ygx8jlKyl6nZlY67dH4kKo4VZm6T9j3wV2WNA1j+44NoCkFlrJFFkklShtTCSAKG5xCbiFPZJwvuNlEO9zokZUhOOYNvYcKza+XT+O2ZlYhJ6EfkCsmAuVtHqpCXfIVoTOszxh64maLeO5fX0+FoVRuduB+83X0+82iQP2B0ObYPykL2MPZtlFcz4JmM9JAJGYqvo2llkZHPrQrkhoDddKBs5gcWZwZ/VugdvYmdTLZg3f2afiAc8DlTUQ7lwqck5wkVgitkBSJe3ZuhviPTE8zRL31pI+MP4AmV5ujuR+SAHtGFew9rWye9OKpig5mKgMDA+3r0vUbbGiaWbfo1mA==</wsse:Password>
            </wsse:UsernameToken>
        </wsse:Security>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
        <requestMessage xmlns="urn:schemas-cybersource-com:transaction-data-1.221">
            <merchantID>en_vdcuruguay_1_ccs</merchantID>
            <merchantReferenceCode>TC55255-1</merchantReferenceCode>
            <invoiceHeader>
                <merchantDescriptor>John</merchantDescriptor>
                <merchantDescriptorStreet>cr avenue</merchantDescriptorStreet>
                <merchantDescriptorState>CA</merchantDescriptorState>
                <merchantVATRegistrationNumber>15426476537657</merchantVATRegistrationNumber>
                <businessApplicationID>WT</businessApplicationID>
                <invoiceNumber>13490</invoiceNumber>
            </invoiceHeader>
            <billTo>
                <firstName>JHON</firstName>
                <lastName>SMITH</lastName>
                <street1>1-26-28 Nakashirane,</street1>
                <street2>Asahi-ku</street2>
                <street3>Suite 500</street3>
                <city>Yokohama-shi</city>
                <state>CA</state>
                <postalCode>602-8511</postalCode>
                <country>US</country>
                <phoneNumber>999-123-9999</phoneNumber>
                <email>test@visa.com</email>
            </billTo>
            <purchaseTotals>
                <currency>USD</currency>
                <grandTotalAmount>1000</grandTotalAmount>
                <invoiceAmount>1234</invoiceAmount>
            </purchaseTotals>
            <card>
                <accountNumber>4111111111111111</accountNumber>
                <expirationMonth>12</expirationMonth>
                <expirationYear>2030</expirationYear>
                <cvNumber>123</cvNumber>
                <cardType>001</cardType>
            </card>
            <ccAuthService run="true">
                <cavv>ABCDEabcde12345678900987654321abcdeABCDE</cavv>
                <networkTokenCryptogram>ABCDE12345ABCED12345ABCDE123</networkTokenCryptogram>
                <commerceIndicator>vbv</commerceIndicator>
                <xid>12345678909876543210ABCDEabcdeABCDEF1234</xid>
                <captureDate>1231</captureDate>
                <initiatorType>S</initiatorType>
            </ccAuthService>
            <paymentNetworkToken>
                <transactionType>1</transactionType>
            </paymentNetworkToken>
            <recipient>
                <postalCode>222120</postalCode>
                <accountID>987654321</accountID>
                <accountType>33</accountType>
                <lastName>recla</lastName>
                <firstName>recfirhgfhtfh</firstName>
                <middleName>recmiddle</middleName>
                <address>this is address1</address>
                <city>westb</city>
                <country>IN</country>
                <buildingNumber>266</buildingNumber>
                <address2>this is address2</address2>
                <streetName>colourful Street</streetName>
            </recipient>
            <sender>
                <referenceNumber>REFNUM123</referenceNumber>
                <sourceOfFunds>02</sourceOfFunds>
                <name>justsenderName</name>
                <address>addressofthesender</address>
                <city>blr</city>
                <state>ka</state>
                <country>India</country>
                <accountNumber>154264765376576126571652675176</accountNumber>
                <firstName>senderfirstname</firstName>
                <middleName>middle</middleName>
                <lastName>last</lastName>
                <personalIDType>TXIN</personalIDType>
                <type>B</type>
                <identificationNumber>23506907642323235</identificationNumber>
            </sender>
            <aft>
                <indicator>true</indicator>
            </aft>
        </requestMessage>
    </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Response
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Header>
        <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
            <wsu:Timestamp wsu:Id="TS-8d8472ec-1a61-4b29-bab0-732050b705e1">
                <wsu:Created>2024-06-26T09:53:04.785Z</wsu:Created>
            </wsu:Timestamp>
        </wsse:Security>
    </soap:Header>
    <soap:Body>
        <c:replyMessage xmlns:c="urn:schemas-cybersource-com:transaction-data-1.221">
            <c:merchantReferenceCode>TC55255-1</c:merchantReferenceCode>
            <c:requestID>7193955837287005009916</c:requestID>
            <c:decision>ACCEPT</c:decision>
            <c:reasonCode>100</c:reasonCode>
            <c:requestToken>Axj/7wSThfwxTs0Lxbf8AHgs3YuWblq1cM27Jw3YMGrBg5csWybWNLUe8AU2saWo95pBHDUCClDJt/9i4qniHXAnJwv4Yp2aF4tv+AAAhh1B</c:requestToken>
            <c:purchaseTotals>
                <c:currency>USD</c:currency>
            </c:purchaseTotals>
            <c:ccAuthReply>
                <c:reasonCode>100</c:reasonCode>
                <c:amount>1000.00</c:amount>
                <c:authorizationCode>831000</c:authorizationCode>
                <c:avsCode>Y</c:avsCode>
                <c:avsCodeRaw>Y</c:avsCodeRaw>
                <c:cvCode>M</c:cvCode>
                <c:cvCodeRaw>M</c:cvCodeRaw>
                <c:authorizedDateTime>2024-06-26T09:53:04Z</c:authorizedDateTime>
                <c:processorResponse>00</c:processorResponse>
                <c:reconciliationID>7193955837287005009916</c:reconciliationID>
                <c:merchantAdviceCode>01</c:merchantAdviceCode>
                <c:merchantAdviceCodeRaw>M001</c:merchantAdviceCodeRaw>
                <c:cavvResponseCode>2</c:cavvResponseCode>
                <c:cavvResponseCodeRaw>2</c:cavvResponseCodeRaw>
                <c:paymentNetworkTransactionID>016153570198200</c:paymentNetworkTransactionID>
                <c:reconciliationReferenceNumber>417809816260</c:reconciliationReferenceNumber>
            </c:ccAuthReply>
            <c:receiptNumber>816260</c:receiptNumber>
            <c:card>
                <c:cardType>001</c:cardType>
            </c:card>
            <c:reserved>
                <ics_message xmlns="urn:schemas-cybersource-com:transaction-data:ics">
                    <auth_rflag>SOK</auth_rflag>
                    <ics_return_code>1000000</ics_return_code>
                    <auth_reconciliation_reference_number>417809816260</auth_reconciliation_reference_number>
                    <auth_cv_result>M</auth_cv_result>
                    <auth_auth_amount>1000.00</auth_auth_amount>
                    <payment_network_token_transaction_type>1</payment_network_token_transaction_type>
                    <card_type>001</card_type>
                    <ics_rmsg>Request was processed successfully.</ics_rmsg>
                    <auth_merchant_advice_code>01</auth_merchant_advice_code>
                    <auth_trans_ref_no>7193955837287005009916</auth_trans_ref_no>
                    <request_token>Axj/7wSThfwxTs0Lxbf8AHgs3YuWblq1cM27Jw3YMGrBg5csWybWNLUe8AU2saWo95pBHDUCClDJt/9i4qniHXAnJwv4Yp2aF4tv+AAAhh1B</request_token>
                    <request_id>7193955837287005009916</request_id>
                    <merchant_ref_number>TC55255-1</merchant_ref_number>
                    <auth_auth_response>00</auth_auth_response>
                    <auth_merchant_advice_code_raw>M001</auth_merchant_advice_code_raw>
                    <auth_payment_network_transaction_id>016153570198200</auth_payment_network_transaction_id>
                    <auth_return_code>1010000</auth_return_code>
                    <ics_rflag>SOK</ics_rflag>
                    <auth.reason_code>100</auth.reason_code>
                    <auth_cavv_response_code>2</auth_cavv_response_code>
                    <auth_rcode>1</auth_rcode>
                    <receipt_number>816260</receipt_number>
                    <auth_additional_token_response_information>0</auth_additional_token_response_information>
                    <auth_cv_result_raw>M</auth_cv_result_raw>
                    <auth_rmsg>Request was processed successfully.</auth_rmsg>
                    <auth_auth_time>2024-06-26T095304Z</auth_auth_time>
                    <ics_decision_reason_code>100</ics_decision_reason_code>
                    <auth_cavv_response_code_raw>2</auth_cavv_response_code_raw>
                    <auth_auth_code>831000</auth_auth_code>
                    <currency>USD</currency>
                    <auth_avs_raw>Y</auth_avs_raw>
                    <auth_auth_avs>Y</auth_auth_avs>
                    <ics_rcode>1</ics_rcode>
                </ics_message>
            </c:reserved>
            <c:additionalToken>
                <c:responseInformation>0</c:responseInformation>
            </c:additionalToken>
        </c:replyMessage>
    </soap:Body>
</soap:Envelope>

Dual Message Account Funding Transactions (AFTs) to Establish a Recurring Payout Transaction (CIT)

Account Funding Transactions allow a payment service provider to debit funds from a cardholder's Mastercard or Visa account to fund a non-merchant account. This is typically used to load funds onto prepaid cards and electronic wallets.
Dual Message Account Funding Transactions (AFTs) provide the following benefits:
  • Enables customers to identify Mastercard and Visa transactions during the authorization and settlement.
  • Allows acquiring partners to use Dual Message BINs when performing a payout transaction.
Using the credential-on-file transactions, customers can set up recurring transfers, for example transferring USD 50 to the customer's wallet each month. To set up such a transaction, the customer needs to create a Customer Inititated Transaction (CIT) that establishes the frequency, amount and duration of the recurring transfer. This information is then saved so that follow on Merchant Initiated Transactions (MITs) can occur on the customer's behalf.

Endpoint

Set the
ccAuthService_run
 field to
true
.
Send the request to
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
.

Required Fields for a Dual-Message AFT with a CIT Request

These fields are required to process a dual-message AFT with a CIT request:
This field is only required when you have received an XID value in a previous transaction.
invoiceHeader_invoiceNumber
purchaseTotals_invoiceAmount

Simple Order Example: Dual-Message AFT with a CIT

Request
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Header>
        <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
            <wsse:UsernameToken>
                <wsse:Username>en_vdcuruguay_1_ccs</wsse:Username>
                <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">ygx8jlKyl6nZlY67dH4kKo4VZm6T9j3wV2WNA1j+44NoCkFlrJFFkklShtTCSAKG5xCbiFPZJwvuNlEO9zokZUhOOYNvYcKza+XT+O2ZlYhJ6EfkCsmAuVtHqpCXfIVoTOszxh64maLeO5fX0+FoVRuduB+83X0+82iQP2B0ObYPykL2MPZtlFcz4JmM9JAJGYqvo2llkZHPrQrkhoDddKBs5gcWZwZ/VugdvYmdTLZg3f2afiAc8DlTUQ7lwqck5wkVgitkBSJe3ZuhviPTE8zRL31pI+MP4AmV5ujuR+SAHtGFew9rWye9OKpig5mKgMDA+3r0vUbbGiaWbfo1mA==</wsse:Password>
            </wsse:UsernameToken>
        </wsse:Security>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
        <requestMessage xmlns="urn:schemas-cybersource-com:transaction-data-1.221">
            <merchantID>en_vdcuruguay_1_ccs</merchantID>
            <merchantReferenceCode>TC55255-1</merchantReferenceCode>
            <invoiceHeader>
                <merchantDescriptor>John</merchantDescriptor>
                <merchantDescriptorStreet>cr avenue</merchantDescriptorStreet>
                <merchantDescriptorState>CA</merchantDescriptorState>
                <merchantVATRegistrationNumber>15426476537657</merchantVATRegistrationNumber>
                <businessApplicationID>WT</businessApplicationID>
                <invoiceNumber>13490</invoiceNumber>
            </invoiceHeader>
            <billTo>
                <firstName>JHON</firstName>
                <lastName>SMITH</lastName>
                <street1>1-26-28 Nakashirane,</street1>
                <street2>Asahi-ku</street2>
                <street3>Suite 500</street3>
                <city>Yokohama-shi</city>
                <state>CA</state>
                <postalCode>602-8511</postalCode>
                <country>US</country>
                <phoneNumber>999-123-9999</phoneNumber>
                <email>test@visa.com</email>
            </billTo>
            <purchaseTotals>
                <currency>USD</currency>
                <grandTotalAmount>500</grandTotalAmount>
                <invoiceAmount>1234</invoiceAmount>
            </purchaseTotals>
            <card>
                <accountNumber>4111111111111111</accountNumber>
                <expirationMonth>12</expirationMonth>
                <expirationYear>2030</expirationYear>
                <cvNumber>123</cvNumber>
                <cardType>001</cardType>
            </card>
            <ccAuthService run="true">
                <cavv>ABCDEabcde12345678900987654321abcdeABCDE</cavv>
                <networkTokenCryptogram>ABCDE12345ABCED12345ABCDE123</networkTokenCryptogram>
                <commerceIndicator>vbv</commerceIndicator>
                <xid>12345678909876543210ABCDEabcdeABCDEF1234</xid>
                <aggregatorName>Test</aggregatorName>
                <captureDate>1231</captureDate>
                <purposeOfPayment>16</purposeOfPayment>
                <initiatorType>s</initiatorType>
            </ccAuthService>
            <surchargeAmount>5</surchargeAmount>
            <surchargeSign>c</surchargeSign>
            <recipient>
                <postalCode>222120</postalCode>
                <accountID>987654321</accountID>
                <accountType>33</accountType>
                <lastName>recla</lastName>
                <firstName>recfirhgfhtfh</firstName>
                <middleName>recmiddle</middleName>
                <address>this is address1</address>
                <city>westb</city>
                <country>IN</country>
                <buildingNumber>266</buildingNumber>
                <address2>this is address2</address2>
                <streetName>colourful Street</streetName>
            </recipient>
            <sender>
                <referenceNumber>REFNUM123</referenceNumber>
                <sourceOfFunds>02</sourceOfFunds>
                <name>justsenderName</name>
                <address>addressofthesender</address>
                <city>blr</city>
                <state>ka</state>
                <country>India</country>
                <accountNumber>154264765376576126571652675176</accountNumber>
                <firstName>Sachin</firstName>
                <middleName>andy</middleName>
                <lastName>poov</lastName>
                <personalIDType>TXIN</personalIDType>
                <type>B</type>
                <identificationNumber>23506907642323235</identificationNumber>
            </sender>
            <aft>
                <indicator>true</indicator>
                <foreignExchangeFee>12</foreignExchangeFee>
            </aft>
            <subsequentAuthStoredCredential>false</subsequentAuthStoredCredential>
        </requestMessage>
    </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Response
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Header>
        <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
            <wsu:Timestamp wsu:Id="TS-c3c104ec-1bae-4231-9d11-eb5e89c62bb8">
                <wsu:Created>2024-06-26T10:12:59.688Z</wsu:Created>
            </wsu:Timestamp>
        </wsse:Security>
    </soap:Header>
    <soap:Body>
        <c:replyMessage xmlns:c="urn:schemas-cybersource-com:transaction-data-1.221">
            <c:merchantReferenceCode>TC55255-1</c:merchantReferenceCode>
            <c:requestID>7193967786057005809916</c:requestID>
            <c:decision>ACCEPT</c:decision>
            <c:reasonCode>100</c:reasonCode>
            <c:requestToken>Axj/7wSThfxbwiTbLED8AHgs3YuWbls3buGzBq3YMGrhg5csWybWNLU08AU2saWpp5pBDDUEFKGTb/7FxVPEOuBOThfxbwiTbLED8AAAyRo1</c:requestToken>
            <c:purchaseTotals>
                <c:currency>USD</c:currency>
            </c:purchaseTotals>
            <c:ccAuthReply>
                <c:reasonCode>100</c:reasonCode>
                <c:amount>500.00</c:amount>
                <c:authorizationCode>831000</c:authorizationCode>
                <c:avsCode>Y</c:avsCode>
                <c:avsCodeRaw>Y</c:avsCodeRaw>
                <c:cvCode>M</c:cvCode>
                <c:cvCodeRaw>M</c:cvCodeRaw>
                <c:authorizedDateTime>2024-06-26T10:12:59Z</c:authorizedDateTime>
                <c:processorResponse>00</c:processorResponse>
                <c:reconciliationID>7193967786057005809916</c:reconciliationID>
                <c:merchantAdviceCode>01</c:merchantAdviceCode>
                <c:merchantAdviceCodeRaw>M001</c:merchantAdviceCodeRaw>
                <c:cavvResponseCode>2</c:cavvResponseCode>
                <c:cavvResponseCodeRaw>2</c:cavvResponseCodeRaw>
                <c:paymentNetworkTransactionID>016153570198200</c:paymentNetworkTransactionID>
                <c:reconciliationReferenceNumber>417810816287</c:reconciliationReferenceNumber>
            </c:ccAuthReply>
            <c:receiptNumber>816287</c:receiptNumber>
            <c:additionalData>ABC</c:additionalData>
            <c:card>
                <c:cardType>001</c:cardType>
            </c:card>
            <c:reserved>
                <ics_message xmlns="urn:schemas-cybersource-com:transaction-data:ics">
                    <ics_decision_reason_code>100</ics_decision_reason_code>
                    <auth_payment_network_transaction_id>016153570198200</auth_payment_network_transaction_id>
                    <auth_rcode>1</auth_rcode>
                    <receipt_number>816287</receipt_number>
                    <ics_return_code>1000000</ics_return_code>
                    <auth_merchant_advice_code>01</auth_merchant_advice_code>
                    <ics_rcode>1</ics_rcode>
                    <auth_cavv_response_code>2</auth_cavv_response_code>
                    <auth_auth_response>00</auth_auth_response>
                    <auth_rmsg>Request was processed successfully.</auth_rmsg>
                    <merchant_ref_number>TC55255-1</merchant_ref_number>
                    <auth_merchant_advice_code_raw>M001</auth_merchant_advice_code_raw>
                    <currency>USD</currency>
                    <auth_auth_code>831000</auth_auth_code>
                    <auth_auth_amount>500.00</auth_auth_amount>
                    <auth_cv_result_raw>M</auth_cv_result_raw>
                    <auth_fee_program_indicator>123</auth_fee_program_indicator>
                    <card_type>001</card_type>
                    <auth_additional_token_response_information>0</auth_additional_token_response_information>
                    <ics_rmsg>Request was processed successfully.</ics_rmsg>
                    <auth_trans_ref_no>7193967786057005809916</auth_trans_ref_no>
                    <request_id>7193967786057005809916</request_id>
                    <auth.reason_code>100</auth.reason_code>
                    <auth_cavv_response_code_raw>2</auth_cavv_response_code_raw>
                    <auth_auth_time>2024-06-26T101259Z</auth_auth_time>
                    <auth_rflag>SOK</auth_rflag>
                    <auth_cv_result>M</auth_cv_result>
                    <auth_return_code>1010000</auth_return_code>
                    <auth_avs_raw>Y</auth_avs_raw>
                    <ics_rflag>SOK</ics_rflag>
                    <auth_reconciliation_reference_number>417810816287</auth_reconciliation_reference_number>
                    <auth_auth_avs>Y</auth_auth_avs>
                    <request_token>Axj/7wSThfxbwiTbLED8AHgs3YuWbls3buGzBq3YMGrhg5csWybWNLU08AU2saWpp5pBDDUEFKGTb/7FxVPEOuBOThfxbwiTbLED8AAAyRo1</request_token>
                    <additional_data>ABC</additional_data>
                </ics_message>
            </c:reserved>
            <c:additionalToken>
                <c:responseInformation>0</c:responseInformation>
            </c:additionalToken>
        </c:replyMessage>
    </soap:Body>
</soap:Envelope>

Dual Message Account Funding Transactions (AFTs) for a Recurring Payout Transaction (MIT)

Account Funding Transactions allow a payment service provider to debit funds from a cardholder's Mastercard or Visa account to fund a non-merchant account. This is typically used to load funds onto prepaid cards and electronic wallets.
Dual Message Account Funding Transactions (AFTs) provide the following benefits:
  • Enables customers to identify Mastercard and Visa transactions during the authorization and settlement.
  • Allows acquiring partners to use Dual Message BINs when performing a payout transaction.
Using the credential-on-file transactions, customers can set up recurring transfers, for example transferring USD 50 to the customer's wallet each month. To set up such a transaction, the customer needs to create a Customer Inititated Transaction (CIT) that establishes the frequency, amount and duration of the recurring transfer. This information is then saved so that follow on Merchant Initiated Transactions (MITs) can occur on the customer's behalf.

Endpoint

Set the
ccAuthService_run
 field to
true
.
Send the request to
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
.

Simple Order Example: Dual-Message AFT with an MIT

Request
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Header>
        <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
            <wsse:UsernameToken>
                <wsse:Username>en_vdcuruguay_1_ccs</wsse:Username>
                <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">ygx8jlKyl6nZlY67dH4kKo4VZm6T9j3wV2WNA1j+44NoCkFlrJFFkklShtTCSAKG5xCbiFPZJwvuNlEO9zokZUhOOYNvYcKza+XT+O2ZlYhJ6EfkCsmAuVtHqpCXfIVoTOszxh64maLeO5fX0+FoVRuduB+83X0+82iQP2B0ObYPykL2MPZtlFcz4JmM9JAJGYqvo2llkZHPrQrkhoDddKBs5gcWZwZ/VugdvYmdTLZg3f2afiAc8DlTUQ7lwqck5wkVgitkBSJe3ZuhviPTE8zRL31pI+MP4AmV5ujuR+SAHtGFew9rWye9OKpig5mKgMDA+3r0vUbbGiaWbfo1mA==</wsse:Password>
            </wsse:UsernameToken>
        </wsse:Security>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
        <requestMessage xmlns="urn:schemas-cybersource-com:transaction-data-1.221">
            <merchantID>en_vdcuruguay_1_ccs</merchantID>
            <merchantReferenceCode>TC55255-1</merchantReferenceCode>
            <invoiceHeader>
                <merchantDescriptor>John</merchantDescriptor>
                <merchantDescriptorStreet>cr avenue</merchantDescriptorStreet>
                <merchantDescriptorState>CA</merchantDescriptorState>
                <merchantVATRegistrationNumber>15426476537657</merchantVATRegistrationNumber>
                <businessApplicationID>AA</businessApplicationID>
                <invoiceNumber>13490</invoiceNumber>
            </invoiceHeader>
            <billTo>
                <firstName>JHON</firstName>
                <lastName>SMITH</lastName>
                <street1>1-26-28 Nakashirane,</street1>
                <street2>Asahi-ku</street2>
                <street3>Suite 500</street3>
                <city>Yokohama-shi</city>
                <state>CA</state>
                <postalCode>602-8511</postalCode>
                <country>US</country>
                <phoneNumber>999-123-9999</phoneNumber>
                <email>test@visa.com</email>
            </billTo>
            <purchaseTotals>
                <currency>USD</currency>
                <grandTotalAmount>100</grandTotalAmount>
                <invoiceAmount>1234</invoiceAmount>
            </purchaseTotals>
            <card>
                <accountNumber>4111111111111111</accountNumber>
                <expirationMonth>12</expirationMonth>
                <expirationYear>2030</expirationYear>
                <cvNumber>123</cvNumber>
                <cardType>001</cardType>
            </card>
            <ccAuthService run="true">
                <commerceIndicator>recurring</commerceIndicator>
                <aggregatorName>Test</aggregatorName>
                <captureDate>1231</captureDate>
                <purposeOfPayment>16</purposeOfPayment>
                <initiatorType>r</initiatorType>
            </ccAuthService>
            <surchargeAmount>5</surchargeAmount>
            <surchargeSign>c</surchargeSign>
            <recipient>
                <postalCode>222120</postalCode>
                <accountID>987654321</accountID>
                <accountType>33</accountType>
                <lastName>last</lastName>
                <firstName>firstname</firstName>
                <middleName>middlename</middleName>
                <address>this is address1</address>
                <city>Newyork</city>
                <country>US</country>
                <buildingNumber>266</buildingNumber>
                <address2>this is address2</address2>
                <streetName>colourful Street</streetName>
            </recipient>
            <sender>
                <referenceNumber>REFNUM123</referenceNumber>
                <sourceOfFunds>02</sourceOfFunds>
                <name>justsenderName</name>
                <address>addressofthesender</address>
                <city>Newyork</city>
                <state>ca</state>
                <country>US</country>
                <accountNumber>154264765376576126571652675176</accountNumber>
                <firstName>Senderfirst</firstName>
                <middleName>SenderMiddle</middleName>
                <lastName>Senderlast</lastName>
                <personalIDType>TXIN</personalIDType>
                <type>B</type>
                <identificationNumber>23506907642323235</identificationNumber>
            </sender>
            <aft>
                <indicator>true</indicator>
                <foreignExchangeFee>12</foreignExchangeFee>
            </aft>
            <subsequentAuthTransactionID>1234567890</subsequentAuthTransactionID>
            <subsequentAuthStoredCredential>true</subsequentAuthStoredCredential>
        </requestMessage>
    </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Response
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Header>
        <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
            <wsu:Timestamp wsu:Id="TS-f0eb2a10-c584-46c4-88cc-66b1e611de99">
                <wsu:Created>2024-06-26T05:31:53.491Z</wsu:Created>
            </wsu:Timestamp>
        </wsse:Security>
    </soap:Header>
    <soap:Body>
        <c:replyMessage xmlns:c="urn:schemas-cybersource-com:transaction-data-1.221">
            <c:merchantReferenceCode>TC55255-1</c:merchantReferenceCode>
            <c:requestID>7193799125697001709916</c:requestID>
            <c:decision>ACCEPT</c:decision>
            <c:reasonCode>100</c:reasonCode>
            <c:requestToken>Axj/7wSThfoEjnCtcGFcAHgs3YuWbdy5YsmrZy3YMGLdg5csWybWNLRESAU2saWiIlpA6cQQUYZNv/sXFU8Q64E5OF+gSOcK1wYVwAAAyhWl</c:requestToken>
            <c:purchaseTotals>
                <c:currency>USD</c:currency>
            </c:purchaseTotals>
            <c:ccAuthReply>
                <c:reasonCode>100</c:reasonCode>
                <c:amount>100.00</c:amount>
                <c:authorizationCode>831000</c:authorizationCode>
                <c:avsCode>Y</c:avsCode>
                <c:avsCodeRaw>Y</c:avsCodeRaw>
                <c:cvCode>M</c:cvCode>
                <c:cvCodeRaw>M</c:cvCodeRaw>
                <c:authorizedDateTime>2024-06-26T05:31:53Z</c:authorizedDateTime>
                <c:processorResponse>00</c:processorResponse>
                <c:reconciliationID>7193799125697001709916</c:reconciliationID>
                <c:merchantAdviceCode>01</c:merchantAdviceCode>
                <c:merchantAdviceCodeRaw>M001</c:merchantAdviceCodeRaw>
                <c:cavvResponseCode>2</c:cavvResponseCode>
                <c:cavvResponseCodeRaw>2</c:cavvResponseCodeRaw>
                <c:paymentNetworkTransactionID>016153570198200</c:paymentNetworkTransactionID>
                <c:reconciliationReferenceNumber>417805815985</c:reconciliationReferenceNumber>
            </c:ccAuthReply>
            <c:receiptNumber>815985</c:receiptNumber>
            <c:additionalData>ABC</c:additionalData>
            <c:card>
                <c:cardType>001</c:cardType>
            </c:card>
            <c:reserved>
                <ics_message xmlns="urn:schemas-cybersource-com:transaction-data:ics">
                    <auth_return_code>1010000</auth_return_code>
                    <auth_fee_program_indicator>123</auth_fee_program_indicator>
                    <merchant_ref_number>TC55255-1</merchant_ref_number>
                    <auth_merchant_advice_code>01</auth_merchant_advice_code>
                    <auth_cv_result_raw>M</auth_cv_result_raw>
                    <auth_auth_time>2024-06-26T053153Z</auth_auth_time>
                    <auth_rcode>1</auth_rcode>
                    <receipt_number>815985</receipt_number>
                    <auth_rflag>SOK</auth_rflag>
                    <auth_trans_ref_no>7193799125697001709916</auth_trans_ref_no>
                    <ics_rcode>1</ics_rcode>
                    <request_token>Axj/7wSThfoEjnCtcGFcAHgs3YuWbdy5YsmrZy3YMGLdg5csWybWNLRESAU2saWiIlpA6cQQUYZNv/sXFU8Q64E5OF+gSOcK1wYVwAAAyhWl</request_token>
                    <ics_rflag>SOK</ics_rflag>
                    <ics_return_code>1000000</ics_return_code>
                    <auth_auth_avs>Y</auth_auth_avs>
                    <auth_payment_network_transaction_id>016153570198200</auth_payment_network_transaction_id>
                    <card_type>001</card_type>
                    <auth_merchant_advice_code_raw>M001</auth_merchant_advice_code_raw>
                    <ics_rmsg>Request was processed successfully.</ics_rmsg>
                    <additional_data>ABC</additional_data>
                    <currency>USD</currency>
                    <auth_cavv_response_code>2</auth_cavv_response_code>
                    <auth.reason_code>100</auth.reason_code>
                    <auth_auth_amount>100.00</auth_auth_amount>
                    <auth_additional_token_response_information>0</auth_additional_token_response_information>
                    <ics_decision_reason_code>100</ics_decision_reason_code>
                    <auth_cv_result>M</auth_cv_result>
                    <auth_auth_response>00</auth_auth_response>
                    <auth_rmsg>Request was processed successfully.</auth_rmsg>
                    <request_id>7193799125697001709916</request_id>
                    <auth_reconciliation_reference_number>417805815985</auth_reconciliation_reference_number>
                    <auth_auth_code>831000</auth_auth_code>
                    <auth_cavv_response_code_raw>2</auth_cavv_response_code_raw>
                    <auth_payment_type_indicator>R</auth_payment_type_indicator>
                    <auth_avs_raw>Y</auth_avs_raw>
                </ics_message>
            </c:reserved>
            <c:paymentTypeIndicator>R</c:paymentTypeIndicator>
            <c:additionalToken>
                <c:responseInformation>0</c:responseInformation>
            </c:additionalToken>
        </c:replyMessage>
    </soap:Body>
</soap:Envelope>

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

Set the
ccAuthService_run
 field to
true
.
Send the request to
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
.

Required Fields for an OCT

These fields are required in a request for an OCT:
These fields are required in a request for an OCT:
Required when the merchant descriptor contact field is included.
ccAuthService_merchantVerificationValue
Cannot exceed 50,000 USD.
sender_id
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.
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.
If the sender is an individual, use the
sender_firstName
 and
sender_lastName
 fields instead.
Required when the sender country is the US or Canada.

Simple Order Example: OCT Request

Request: Authorization Service for an OCT 
<requestMessage xmlns="urn:schemas-cybersource-com:transaction-data-1.115">
    <merchantID>pa_oct_sg101_ccs</merchantID>
<merchantReferenceCode>TC-23456$</merchantReferenceCode>
<clientReferenceInformation>
    <requestID>6642672790803228323604</requestID>
</clientReferenceInformation>
<billTo>
    <firstName>rfirstName</firstName>
    <middleName>rmiddlename</middleName>
    <lastName>rlastname</lastName>
    <street1>test</street1>
    <street2>test</street2>
    <buildingNumber>test</buildingNumber>
    <city>test</city>
    <state>1</state>
    <postalCode>9440</postalCode>
    <country>US</country>
    <email>RecepientNameRecepientNameName</email>
</billTo>
<amountDetails>
    <totalAmount>0.01</totalAmount>
    <currency>USD</currency>
</amountDetails>
<card>
    <accountNumber>411111111111XXXX</accountNumber>
    <expirationMonth>12</expirationMonth>
    <expirationYear>2026</expirationYear>
    <cardType>001</cardType>
</card>
<processingInformation>
    <businessApplicationId>aa</businessApplicationId>
    <icsApplications>ics_oct</icsApplications>
</processingInformation>
<recipientInformation>
    <recipientName>RecepientNameRecepientNameName</recipientName>
    <recipientFirstName>rfirstName</recipientFirstName>
    <recipientMiddleName>rmiddlename</recipientMiddleName>
    <recipientLastName>rlastname</recipientLastName>
    <recipientAddress1>test</recipientAddress1>
    <recipientAddress2>test</recipientAddress2>
    <recipientBuildingNumber>test</recipientBuildingNumber>
    <recipientCity>test</recipientCity>
    <recipientCountry>US</recipientCountry>
    <recipientPostalCode>9440</recipientPostalCode>
    <recipientStreetName>test</recipientStreetName>
    <recipientState>1</recipientState>
</recipientInformation>
<senderInformation>
    <senderAccountNumber>1234</senderAccountNumber>
    <senderFundsSource>03</senderFundsSource>
    <senderAddress>abc</senderAddress>
    <senderCity>SenderCitySenderCitySende</senderCity>
    <senderCountry>Zim</senderCountry>
    <senderID>ms_user</senderID>
    <senderReferenceNumber>1</senderReferenceNumber>
    <senderState>AZ</senderState>
</senderInformation>
</requestMessage>
Response: Authorization Service for an OCT
<c:replyMessage xmlns:c="urn:schemas-cybersource-com:transaction-data-1.115">
    <c:merchantReferenceCode>TC-23456$</c:merchantReferenceCode>
    <c:requestID>7465072232626783103812</c:requestID>
    <c:decision>ACCEPTED</c:decision>
    <c:reasonCode>100</c:reasonCode>
    <c:purchaseTotals>
        <c:currency>USD</c:currency>
        <c:grandTotalAmount>0.01</c:grandTotalAmount>
    </c:purchaseTotals>
    <c:ccAuthReply>
        <c:reasonCode>100</c:reasonCode>
        <c:amount>0.01</c:amount>
        <c:authorizationCode>888888</c:authorizationCode>
        <c:processorResponse>100</c:processorResponse>
        <c:reconciliationID>610954017ABE1KUI</c:reconciliationID>
    </c:ccAuthReply>
    <c:submitTimeUtc>2025-05-06T045343Z</c:submitTimeUtc>
</c:replyMessage>

Original Credit Transactions (OCTs) with Aggregators

Required Fields for an OCT with Aggregators

These fields are required in a request for an OCT with aggregators:
These fields are required in a request for an OCT:
Not required when you are using a customer token.
Not required when you are using a customer token.
Not required when you are using a customer token.
ccAuthService_merchantVerificationValue
Not required when your account includes this value.
Required when the merchant descriptor contact field is included.
Cannot exceed 50,000 USD.
Required for cross-border transactions into and out of Canada. Otherwise, optional.
Required with Visa for Canada.
recipient_name
sender_id
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.
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.
If the sender is an individual, use the
sender_firstName
 and
sender_lastName
 fields instead.
Required when the sender country is the US or Canada.

Simple Order Example: OCT Request with Aggregators

Request: Authorization Service for an OCT with Aggregators
<requestMessage xmlns="urn:schemas-cybersource-com:transaction-data-1.115">
         <!-- START GENAI -->
<requestMessage xmlns="urn:schemas-cybersource-com:transaction-data-1.115">
    <merchantReferenceCode>TC-23456$</merchantReferenceCode>
    <clientReferenceInformation>
        <requestID>6642672790803228323604</requestID>
    </clientReferenceInformation>
    <aggregatorInformation>
        <aggregatorCity>Bally</aggregatorCity>
        <aggregatorCountry>US</aggregatorCountry>
        <aggregatorPostalCode>560037</aggregatorPostalCode>
        <serviceProviderName>YourServiceProvider</serviceProviderName>
        <aggregatorState>CD</aggregatorState>
        <aggregatorStreetAddress>11 Elvine Street</aggregatorStreetAddress>
    </aggregatorInformation>
    <merchantInformation>
        <merchantID>pa_oct_sg101_ccs</merchantID>
        <merchantDescriptor>
            <merchantStreet>test</merchantStreet>
            <merchantState>CA</merchantState>
        </merchantDescriptor>
    </merchantInformation>
    <purchaseTotals>
        <currency>USD</currency>
        <grandTotalAmount>0.01</grandTotalAmount>
    </purchaseTotals>
    <card>
        <accountNumber>411111111111XXXX</accountNumber>
        <expirationMonth>12</expirationMonth>
        <expirationYear>2026</expirationYear>
        <cardType>001</cardType>
    </card>
    <processingInformation>
        <businessApplicationID>aa</businessApplicationID>
        <icsApplications>ics_oct</icsApplications>
    </processingInformation>
    <billTo>
        <name>RecepientNameRecepientNameName</name>
        <firstName>rfirstName</firstName>
        <middleName>rmiddlename</middleName>
        <lastName>rlastname</lastName>
        <street1>test</street1>
        <street2>test</street2>
        <buildingNumber>test</buildingNumber>
        <city>test</city>
        <state>1</state>
        <postalCode>9440</postalCode>
        <country>US</country>
    </billTo>
    <shipTo>
        <street1>abc</street1>
        <city>SenderCitySenderCitySende</city>
        <state>AZ</state>
        <country>Zim</country>
    </shipTo>
    <account>
        <accountNumber>1234</accountNumber>
        <fundsSource>03</fundsSource>
    </account>
    <senderInformation>
        <id>ms_user</id>
        <referenceNumber>1</referenceNumber>
    </senderInformation>
</requestMessage>
Response: Authorization Service for an OCT
<c:replyMessage xmlns:c="urn:schemas-cybersource-com:transaction-data-1.115">
   <c:merchantReferenceCode>TC-23456$</c:merchantReferenceCode>
    <c:requestID>7465072232626783103812</c:requestID>
    <c:decision>ACCEPTED</c:decision>
    <c:reasonCode>100</c:reasonCode>
    <c:purchaseTotals>
        <c:currency>USD</c:currency>
        <c:grandTotalAmount>0.01</c:grandTotalAmount>
    </c:purchaseTotals>
    <c:ccAuthReply>
        <c:reasonCode>100</c:reasonCode>
        <c:amount>0.01</c:amount>
        <c:authorizationCode>888888</c:authorizationCode>
        <c:processorResponse>100</c:processorResponse>
        <c:reconciliationID>610954017ABE1KUI</c:reconciliationID>
    </c:ccAuthReply>
</c:replyMessage>

Original Credit Transactions (OCTs) with Tokens

An OCT with a token deposits funds into a recipient’s account.

Endpoint

Set the
ccAuthService_run
 field to
true
.
Send the request to
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
.

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
Required when the merchant descriptor field is included.
Cannot exceed 50,000 USD.
sender_id
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.
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.
If the sender is an individual, use the
sender_firstName
 and
sender_lastName
 fields instead.
Required when the sender country is the US or Canada.

Simple Order Example: OCT with Tokens Request

Request: Authorization Service for an OCT 
<requestMessage xmlns="urn:schemas-cybersource-com:transaction-data-1.115">
    <merchantReferenceCode>TC-23456$</merchantReferenceCode>
    <clientReferenceInformation>
        <requestID>6642672790803228323604</requestID>
    </clientReferenceInformation>
    <merchantInformation>
        <merchantID>pa_oct_sg101_ccs</merchantID>
        <merchantDescriptor>
            <merchantStreet>test</merchantStreet>
            <merchantState>CA</merchantState>
        </merchantDescriptor>
    </merchantInformation>
    <purchaseTotals>
        <currency>USD</currency>
        <grandTotalAmount>0.01</grandTotalAmount>
    </purchaseTotals>
    <customer>
        <customerID>F39732BE4BDA9A1EE053AF598E0A4081</customerID>
    </customer>
    <processingInformation>
        <businessApplicationID>aa</businessApplicationID>
        <icsApplications>ics_oct</icsApplications>
    </processingInformation>
    <billTo>
        <name>RecepientNameRecepientNameName</name>
        <firstName>rfirstName</firstName>
        <middleName>rmiddlename</middleName>
        <lastName>rlastname</lastName>
        <street1>test</street1>
        <street2>test</street2>
        <buildingNumber>test</buildingNumber>
        <city>test</city>
        <state>1</state>
        <postalCode>9440</postalCode>
        <country>US</country>
    </billTo>
    <shipTo>
        <street1>abc</street1>
        <city>SenderCitySenderCitySende</city>
        <state>AZ</state>
        <country>Zim</country>
    </shipTo>
    <account>
        <accountNumber>1234</accountNumber>
        <fundsSource>03</fundsSource>
    </account>
    <senderInformation>
        <id>ms_user</id>
        <referenceNumber>1</referenceNumber>
    </senderInformation>
</requestMessage>
Response: Authorization Service for an OCT
<c:replyMessage xmlns:c="urn:schemas-cybersource-com:transaction-data-1.115">
    <c:merchantReferenceCode>TC-23456$</c:merchantReferenceCode>
    <c:requestID>7465072232626783103812</c:requestID>
    <c:decision>ACCEPTED</c:decision>
    <c:reasonCode>100</c:reasonCode>
    <c:purchaseTotals>
        <c:currency>USD</c:currency>
        <c:grandTotalAmount>0.01</c:grandTotalAmount>
    </c:purchaseTotals>
    <c:ccAuthReply>
        <c:reasonCode>100</c:reasonCode>
        <c:amount>0.01</c:amount>
        <c:authorizationCode>888888</c:authorizationCode>
        <c:processorResponse>100</c:processorResponse>
        <c:reconciliationID>610954017ABE1KUI</c:reconciliationID>
    </c:ccAuthReply>
    <c:submitTimeUtc>2025-05-06T045343Z</c:submitTimeUtc>
</c:replyMessage>

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
invoiceHeader_businessApplicationID
.
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.
If you are funding a prepaid account, use the
TU
 value. Do not use the
AA
 value.
BI
Financial institution offered Bank-initiated P2P money transfer
P2P (person-to-person) money transfer is initiated from an online banking system, making it a bank-initiated transaction. This category is only used for specific scenarios and only available in limited markets. For more information, contact your Visa representative.
FD
Funds Disbursement
FT
Funds Transfer
If the funds will be used for a high-brand risk transaction, the applicable high-brand risk MCC must be used. If a wallet is used to purchase liquid and cryptocurrency assets, the applicable special condition indicator must be used.
PD
Payroll Disbursement
PP
Person-to-Person (P2P) money transfer
P2P Money Transfer is initiated from an online banking system, making it a bank-initiated transaction. This category is used only when both AFTs and OCTs are supported. When an AFT is only supported, use the
FT
 category.
TU
Prepaid Card Load or Top-up
WT
Staged Digital Wallet (SDW) Transfer
If the funds will be used for a high-brand risk transaction, the applicable high-brand risk MCC must be used. If the funds are used for a gambling transaction, the applicable gambling MCC must be used. If a wallet is used to purchase liquid and cryptocurrency assets, the applicable special condition indicator must be used. An AFT is not intended for debt repayment.

Business Application Identifier and Merchant Category Code Use Cases

Acquirers, service providers, and you must use the correct Business Application Identifier (BAI) and Merchant Category Code (MCC) in the OCT authorization request message. These codes also be used in the clearing and settlement messages. This helps identify the type of OCT and the merchant or business that started the transaction.
Both the BAI and the MCC help the issuer identify the business purpose of the OCT. The MCC should represent you, the acquirer, or the service provider/payment facilitator involved in the OCT transaction. Acquirers receive instructions during program approval on which BAI to use for their OCTs. The BAI and MCC Usage – Money Transfer table lists the available BAIs and provides examples of relevant use cases.
Certain industries, such as healthcare, insurance, payroll, and gambling, are regulated by federal, provincial, and local laws. You, acquirers, and service providers are responsible for ensuring that your Visa Direct program complies with all applicable laws. This includes making required disclosures, obtaining necessary consents, and ensuring that OCTs are not sent to or from countries where gambling is illegal.
The table shows MCCs based on specific use cases. This is not a full list of all MCCs used with OCT.
Starting April 16, 2023,
Cybersource
 requires the merchant name field in a stand-alone tipping transaction to include the word "tip" for tipping use-cases.
BAI and MCC Usage – Money Transfer
BAI
Use Case
MCC
Examples of Use
AA
Account-to-Account
Remote Deposit Check (RDC) capture
Consumer funding of their own account
4829
 Non-financial Institution Wire Transfer Money Orders (WTMOs) (Not applicable to the US with BAI
AA
)
6012
 Financial Institutions: Merchandise and services
6211
 Security Brokers/Dealers
For OCT, this is a sender moving money from their own account to their card account. Me-to-Me money transfer.
BI
Bank-Initiated Money Transfer
Important:
 BAI
BI
 is used for very specific scenarios and is enabled only in limited markets. Contact your Visa representative for information on:
  • The availability of BAI
    BI
     in your market, and
  • Applicability of BAI
    BI
     to your program.
6012
 Financial Institutions: Merchandise and services
BAI
BI
 should only be used in combination with MCC
6012
.
Money transfer is initiated from an online banking system, making it a bank-initiated transaction. Usage of this BAI applies to money transfer offered in a closed-loop solution.
CD
Cash Deposit
6012
 or Retail Merchant MCC
Deposit of cash using an OCT to add funds to a debit account at a bank branch or retail location.
FT
Funds Transfer
6540
 Non-financial Institutions: Stored value card purchase/load
4829
 Non-financial Institution Wire Transfer Money Orders (WTMOs)
6012
 Financial Institutions: Merchandise and services
Cashing out a Stored Value Digital Wallet (SVDW) account.
Liquid and cryptocurrency asset as a general purpose wallet, proceeds from a sale or cash out, are paid out with an OCT with BAI
FT
. Cryptocurrency transactions must include the Special Condition Indicator (Field 60.4) =
7
.
Wallet providers must use BAI
LA
 instead of
FT
/
WT
 for cashing out funds if it is a general-purpose wallet, and 50 percent or more of their annual sales volume comes from liquid or cryptocurrency assets.
LA
Effective 19 October 2024
Liquid Assets
A new BAI for Visa Direct transactions involving wallet pre-funding or the direct purchase of liquid and cryptocurrency assets.
In Canada and the US the new BAI value will not be applicable for origination of domestic OCTs. Issuers and issuer processors must be ready to receive new BAI value of
LA
 for cross-border OCTs originating outside of Canada and the U.S.
Any originating entity identified as a foreign currency exchange or cryptocurrency merchant, broker, or platform.
6012
 – Financial Institutions: Merchandise, services, and debt repayment
6051
 – Non-Financial Institutions: Foreign currency, liquid and cryptocurrency assets (cryptocurrency), money orders (not money transfer), account funding (not stored value load), travelers cheques, and debt repayment; must identify Visa Direct transactions under the BAI value of
LA
.
6211
 – Security Brokers/Dealers Brokerage. If greater than 50 percent of client annual sales volume, measured in the client’s local fiat currency comes from noncryptocurrency (for example, stocks, bonds, and so on).
Liquid and cryptocurrency asset, proceeds from a sale or cash out, are paid out with an OCT with BAI
LA
. Cryptocurrency transactions must include the Special Condition Indicator (Field 60.4) = 7.
Wallet providers must use BAI LA instead of
FT
/
WT
 for cashing out funds if it is a general-purpose wallet, and 50 percent or more of their annual sales volume comes from liquid or cryptocurrency assets.
PP
P2P Money Transfer
4829
 Non-Financial Institution Wire Transfer Money Orders (WTMOs)
6012
 Financial Institutions: Merchandise and services
Based on the type of services, combine MCC
6012
 with a valid BAI. Bank-initiated P2P programs must use a BAI of
BI
 and MCC
6012
 or a BAI of
PP
 and MCC
6012
. Non bank-offered services must use a combination of PP and
4829
.
For OCT, this is a sender sending money to someone else’s account.
WT
Wallet Transfer-Staged Digital Wallet (SDW) Transfer
6051
 Non-financial Institutions: Foreign currency, liquid and cryptocurrency assets (for example: cryptocurrency), money orders (not money transfer), account funding (not stored value load), travelers checks, and debt repayment
4829
 Non-Financial Institution Wire Transfer Money Orders (WTMOs)
6012
 Financial Institutions: Merchandise and services
For OCT this is the withdrawal or cash out of funds from a staged digital wallet to a card account.
Wallet providers must use BAI
LA
 instead of
FT
/
WT
 for cashing out funds if it is a general-purpose wallet, and 50 percent or more of their annual sales volume comes from Liquid or Cryptocurrency assets.
If the wallet supports cryptocurrency, this must be communicated by setting the Special Condition indicator (Field 60.4) =
7
.
Acquirers and originators in Europe, India, and Brazil are not required to submit a business application identifier of
WT
 for staged digital wallet transactions.
BAI and MCC Usage – Funds Disbursement/Non-Money Transfer
BAI
Use Case
MCC
Example of Use
BB
 (Not applicable to the US)
Business-to-business Supplier Payments
Any MCC associated to the merchant, acquirer, or service provider business (example:
5812
 = restaurant,
5311
 = department store)
Business-to-business payments for business-related supplies.
BP
Non-card Bill Pay
MCC associated to the recipient business
For non-card bill payment.
CP
Credit Card Bill Pay
4829
 Non-financial Institution Wire Transfer Money Orders (WTMOs)
6012
 Financial Institutions: Merchandise and services
Pushing funds to a credit card account as a payment.
FD
If requesting to use FD for a subuse case not listed, it must be described in detail in the PIF for approval.
General Funds Disbursement: All other funds disbursements not listed.
Examples:
  • Commission payments
  • Digital goods – games
  • Insurance payments
  • Loan disbursements
  • Alternative/online lending or peer-to-peer lending
  • Shared economy
  • Tax refund services: non-government initiated (for example, tax preparation businesses)
  • VAT tax reclamation
  • Earned wage access
  • Gig worker payouts
  • Marketplace payouts
  • Contractor payouts
  • Tip payouts
  • Corporate expense reimbursement
  • “Bad customer experience” payouts (for example, airline payment to disgruntled passenger)
  • Rebates
  • Education disbursements
  • Security deposit refunds
  • Reimbursement of over payments to billers (for example, Business owes me USD 50 after I cancel service mid-month)
Any MCC associated to the merchant, acquirer, or service provider business (example:
5812
 = restaurant,
5311
 = department store)
Funds disbursements not covered by other BAI use cases listed above. If the program supports cryptocurrency, this must be communicated by setting the Special Condition indicator (Field 60.4) =
7
.
GD
Government Disbursements and Government Initiated Tax Refunds
9399
 Government services (not elsewhere classified)
9402
 Postal services – government only
9405
 U.S. Federal government agencies or departments 9222 fines; government administered
9211
 Court costs, including alimony and child support 9311 tax payments
Government payments, including social security payments, unemployment, disability, jury duty, and disaster relief/emergency.
GP
Gambling/Gaming Payouts (other than online gambling)
7800
 Government owned lottery (US only)
7801
 Government-licensed casinos (US only)
7802
 Government-licensed horse/dog racing (U.S. only).
7800
,
7801
, and
7802
 are US only MCCs that also require the use of a valid Merchant Verification Value (MVV). Merchants must register with Visa to obtain an MVV.
7995
 Betting, including lottery tickets, casino gaming chips, off-track betting, and wagers at racetracks
9406
 Government-owned lottery (non-US only)
Casino payouts at gaming floor counter and sports books.
Advanced deposit wagering.
Gambling that is not considered online gambling.
LO
Loyalty Payments
Any MCC associated to the merchant, acquirer, or service provider business
Examples:
  • 5812
     = restaurant
  • 5311
     = department store
Payment for a canceled loyalty program/service, deposit refunds, employee rewards, and purchase rebate payments.
MD
Merchant Settlement
6012
 Acquirers sending settlement payments to merchants
4829
 Payment facilitator (includes sponsored processors, and ISOs) sending settlement payments to merchants
Merchant payments for purchase transaction processing where the processor sends settlement payments to a Visa card account using OCT.
MI
Effective January 2024
Faster Refunds
Any MCC associated with the merchant, acquirer, or service provider business.
Refund purchases of goods and services made on a Visa Card using OCT.
OG
Online Gambling Payouts
7800
 Government-owned lottery (US only)
7801
 Government-licensed Casinos (US only)
7802
 Government-licensed horse/dog racing (US only)
7995
 Betting, including lottery tickets, casino gaming chips, off-track betting, and wagers at racetracks
9406
 Government-owned lottery (non-US only)
Payout of winnings from online gambling merchants, including casinos, horse/dog racing wagers, lottery, digital, and social gaming payouts.
PD
Payroll and Pensions Disbursements
8931
 Accounting, auditing, and bookkeeping services
Independent contractor works for temporary staffing agency or directly with an employer, submits time sheet or completes project, and is paid to bank account by using a debit card.
RP
Request-to-Pay Service
Refer to
Visa Direct Request to Pay Implementation Guide
 for information on eligible MCC.
Visa's Request-to-Pay (R2P) service is a secure messaging framework built on APIs that enable client to request payment and communicate about a payment obligation, enabling bill splitting, and funds collection functionality for mobile banking applications.
Limited geographic scope to Ukraine and Kazakhstan.
TU
Prepaid Card Load
6012
 Financial Institutions – merchandise and services
6540
 Non-financial Institutions: Stored-value card purchase/load
Loads, reloads, and top-ups to prepaid card accounts.
Restricts use to Prepaid card only. VisaNet edit declines the transaction if the card product is not prepaid and BAI is
TU
.
Money transfer velocity limits apply.
Visa issuers/issuer processors are required to receive and process all types of OCTs.

Sender Source

The Sender Source field identifies the source of funds. Provide one of the values when you send field
sender_sourceOfFunds
.
All acquirers, service providers, and merchants are required to submit a valid sender source value when submitting an AFT.
Sender Source Values
Value
Definition
01
Credit card
02
Debit card
03
Prepaid card
04
Cash
05
Debit or deposit accounts that are not linked to a Visa card such checking accounts, savings accounts, proprietary Cybersource
sender_sourceOfFunds
 debit or ATM card account, and digital wallet account.
06
Credit accounts that is not linked to a Visa card such as credit cards and proprietary lines of credit.

Test Card Numbers

Use the
Cybersource
 test card numbers for OCTs validate your transactions. These numbers help you mimic real-life situations, find problems, and improve transaction safety and efficiency.
Test Card Numbers for OCTs
Request
Test Card Number
4111111111111111
4111111111111111
4111111111111111