Account Funding Transactions Developer Guide

This section provides you with information about the
Simple Order API
guide
for
Visa Platform Connect
.

Audience and Purpose

This document is written for developers who want to use the
Cybersource
Simple Order API
to integrate
Cybersource
Account Funding Transaction services into their transaction management system.

Conventions

This special statement is used in this document:
An
Important
statement contains information essential to successfully completing a task or learning a concept.

Related Documentation

For further technical documentation, visit the
Cybersource
Technical Documentation Portal:

Customer Support

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

Recent Revisions to This Document

24.02

Added new fields to the list of required fields.

24.01

Initial release.

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.

AFT Transactions

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

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.
You must receive prior approval from
Visa Platform Connect
before using the AFT services. Contact
Visa Platform Connect
to register in the AFT program.

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 $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 $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>

Appendix A: Business Application Identifier Values

The Business Application Identifier (BAI) is used to identify the category of the Account Funding Transaction (AFT). Provide one of the values when you send field
invoiceHeader_businessApplicationID
.
All acquirers, service providers, and merchants are required to submit a valid BAI value when submitting AFTs.
Business Application Identifier Values
BAI Value
Category
Requirements
AA
Account-to-Account Money Transfer. The funding of the cardholder's own account at the same or a different financial institution
Both accounts must be owned by the same person/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 only used when both AFTs and OCTs are supported. When only AFT is 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.

Appendix
B
: Sender Source

The Sender Source 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 AFTs.
Sender Source Values
Value
Definition
01
Credit Card
02
Debit Card
03
Prepaid Card
04
Cash
05
Debit or deposit account that is not linked to a Visa card. This includes checking accounts, savings accounts, proprietary Cybersource
sender_sourceOfFunds
debit or ATM card accounts, and digital wallet accounts.
06
Credit account that is not linked to a Visa card. This includes credit cards and proprietary lines of credit.

Appendix C: Visa BAI to Mastercard TTI Mapping

These are the Visa BAI to Mastercard TTI mapping and their descriptions for different regions and transaction types.

Handling Wallet Transfer MCC Across All Regions

Visa Business Application Identifier (BAI)
:
WT
: Wallet transfer
Mastercard Transaction Type Indicator (TTI)
:
F61
Description
:
Mastercard specifies Merchant Category Codes (MCC) to retain Account Funding Wallet Transfers.
These are the MCCs:
  • 6051
    (Quasi-Cash: Merchant): The account provider’s primary activity is buying and selling cryptocurrency.
  • 6211
    (Securities-Brokers/Dealers): The account provider’s primary activity is purchasing, selling, or brokering high-risk securities.
  • 7800
    /
    7801
    /
    7994
    /
    7995
    /
    9406
    (gaming and gambling): The account provider’s primary activity is gaming or gambling.
  • 6540
    (Default
    WT
    MCC): Participants use the mentioned MCC for all other use cases for Transfers to Own Staged Digital Wallet Accounts.
Acquirers must adjust the mapping accordingly to clear the file to align with the Auth MCC, and ensure accurate clearing and compliance.
The system will automatically overwrite the MCC in these scenarios if mapping is not adjusted:
  • When the client includes BAI as
    WT
    and MCC as
    6051
    , and the Transaction Purpose is
    16
    (securities), the system will set the TTI to
    F61
    and the MCC to
    6211
    .
  • When the client includes BAI as
    WT
    and MCC as
    6051
    , and the Transaction Purpose is
    11
    (cryptocurrency), the system will set the TTI to
    F61
    and retain the MCC as
    6051
    .
  • When the merchant sends
    6051
    for any other transaction purpose, the system will replace the MCC with
    6540
    .
  • When you send MCCs other than the ones mentioned above, the system will overwrite them to
    6540
    .

Handling Account to Account and Funds Transfer MCC for Non-Asia Pacific Region

Visa Business Application Identifier (BAI)
:
FT
: Funds Transfer
Mastercard Transaction Type Indicator (TTI)
:
F52
Description
:
Mastercard specifies MCCs to retain for Account to Account and Funds Transfer for the Non-Asia Pacific region.
These are the MCCs:
  • 6051
    (Quasi-Cash: Merchant): The account provider’s primary activity is buying and selling cryptocurrency.
  • 6211
    (Securities-Brokers/Dealers): The account provider’s primary activity is purchasing, selling, or brokering high-risk securities.
  • 7800
    /
    7801
    /
    7994
    /
    7995
    /
    9406
    (Gaming and Gambling): The account provider’s primary activity is gaming or gambling.
  • 4829
    (Default Funding Transactions): Participants use the mentioned MCC for all other use cases for Account to Account and Funds Transfer.
Acquirers must adjust the mapping accordingly to clear the file to align with the Auth MCC, and ensure accurate clearing and compliance.
The system will automatically overwrite the MCC if mapping is not adjusted when you send MCCs other than the ones mentioned above. The system will overwrite them to
4829
.

Handling Account to Account and Funds Transfer MCC for Asia Pacific Region

Visa Business Application Identifier (BAI)
:
FT
: Funds Transfer
Mastercard Transaction Type Indicator (TTI)
:
F52
Description
:
Mastercard specifies MCCs to retain for Account to Account and Funds Transfer for the Asia Pacific region.
These are:
  • 4829
    (Money Transfer): Customers transfer funds via an electronic funds transfer/wire transfer/remittance to a named entity (both card-present and card-absent locations, including on the premises of the Merchant and third-party agents).
  • 6540
    (Fund Transfer): Participants use the mentioned MCC for all other use cases for fund transfer.
Acquirers must adjust the mapping accordingly to clear the file to align with the Auth MCC, and ensure accurate clearing and compliance.
The system will automatically overwrite the MCC if mapping is not adjusted when you send MCCs other than the ones mentioned above. The system will overwrite them to
6540
.

Handling Person to Person Funding Transactions MCC Across Regions

Visa Business Application Identifier (BAI)
:
PP
: Person-to-Person Money Transfer
Mastercard Transaction Type Indicator (TTI)
:
F07
Description
:
Mastercard specifies MCCs to retain for general Person to Person funding transactions.
These are the MCCs:
  • 4829
    (Money Transfer): Customers transfer funds via electronic funds transfer/wire transfer/remittance to a named entity (both card-present and card-absent locations including on the premises of the Merchant and third-party agents).
  • 6540
    (Fund Transfer): Participants use this MCC for all other fund transfer use cases.
Acquirers must adjust the mapping accordingly to clear the file to align with the Auth MCC, and ensure accurate clearing and compliance.
The system will automatically overwrite the MCC if mapping is not adjusted when you send MCCs other than the ones mentioned above. The system will overwrite them to
6540
.

Handling Person to Person to Card Account Transactions MCC Across Regions

Visa Business Application Identifier (BAI)
:
PP
: Person-to-Person Money Transfer
Mastercard Transaction Type Indicator (TTI)
:
F08
Description
:
Mastercard specifies MCCs to retain for general person-to-person to card account transactions.
Person-to-person to card account
: When a merchant conducts a person-to-person transaction and provides both the recipient's account type and account ID, the system classifies the transaction as a Person-to-Person to Card Account transaction. Then the system will apply the specified MCC.
This is the MCC:
  • 4829
    (Money Transfer): Customers transfer funds via electronic funds transfer/wire transfer/remittance to a named entity (both card-present and card-absent locations, including on-premises of the merchant and third-party agents).
Acquirers must adjust the mapping accordingly to clear the file to align with the Auth MCC, and ensure accurate clearing and compliance.
The system will automatically overwrite the MCC if mapping is not adjusted when you send MCCs other than the ones mentioned above, the system will overwrite them to
6540
.
Account Identifier Type and value are required for TTI
F08
. If the you send the transaction without this data, the system will map it as general person-to-person with TTI
F07
(MCC
4829
will be sent as is to Mastercard, and all others will map to
6540
).