On This Page
Payouts Developer Guide
Payouts Developer Guide
This section describes how to use this guide and where to find further information.
Audience and Purpose
This document is written for developers who want to use the
Cybersource
APIs to integrate Cybersource
Payouts
services into their transaction management system. Conventions
This statement is used in this document:
IMPORTANT
An
Important
statement contains information essential to
successfully completing a task or learning a concept.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
25.05.01
Initial release.
Introduction to Payouts
Payouts
This introduction contains an overview of the
Payouts
service
and describes the supported sender card types, payment networks, requirements, and
limitations. IMPORTANT
Visa Direct
is a distinct
REST API
connection and is unrelated to the Visa Platform Connect
processor mentioned in other Cybersource
documentation.Overview
The
Payouts
service transfers funds from one account to
another using a two-step transaction process:- An account funding transaction (AFT) withdraws funds from a sender’s account using standard credit card processing.
- An original credit transaction (OCT) deposits funds into a recipient’s account.
An AFT and OCT are independent transactions, though an AFT often precedes a
corresponding OCT.
In typical payment transactions, you initiate debits and credits to receive payments
from cardholders for your goods and services. With
Payouts
, you provide a money transfer service by initiating AFT and OCT transactions that
move funds between accounts. These are the money transfer types:- An account-to-account payment moves funds between accounts owned by the same person.
- A business-to-person payment moves funds between a merchant and a cardholder.
- A person-to-person payment moves funds between two cardholders.
For a person-to-person funds transfer, Pull and Push services are executed. When an
AFT is authorized for a person-to-person transaction, the funds are available and
can be withdrawn from the sender's account. This service is referred to as a Pull
service. A subsequent OCT is authorized, and the funds can deposited into the
recipient's account. This service is referred to a Push service.
The
Payouts
system ensures that both Pull and Push
services are executed efficiently, providing a seamless experience for users. By
leveraging Payouts
, businesses and individuals can
streamline their financial operations, making transactions more efficient and
reliable.No merchant goods are involved in
Payouts
transactions.IMPORTANT
You must receive approval from
your processor
before using the AFT
service. Contact your processor
to register in the
AFT program.AFT Types
The Account Funding Transaction (AFT) is a specific type of transaction that moves funds
from a Visa account to another Visa or non-Visa account. It is primarily used for
loading or topping up prepaid card accounts, transferring funds into another financial
account (like a savings account), acting as a funding source for person-to-person (P2P)
money transfers, or loading third-party digital wallets. AFTs cannot be used for
purchasing goods or services or transferring funds to a merchant account.
AFTs are the required transactions to load or top-up prepaid cards in all regions. An AFT
is the required pull transaction to be used for disbursing payroll funds, P2P or
me-to-me transactions, and pre-funding a customer's digital wallet in a card-not-present
environment. When used independently to fund another Visa or non-Visa account, AFTs must
be used only to fund an account belonging to the same individual or entity holding the
Visa account.
Reversal and Adjustment Transactions
You can reverse an AFT within the first 24 hours of the original transaction before
the transaction settles.
You can refund an AFT back to the sender's card within 30 days of the original AFT
back to the sender's card. You cannot originate a refund if the original transaction
is over 30 days old. The system accepts a refund after the original AFT settles.
IMPORTANT
Issuers can manage AFT refunds as credit adjustments instead of
posting the transaction directly into the cardholder's account. Therefore, the timeframe
for when the cardholder should expect the refund will vary by issuer.
Aggregator Support for Payouts
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.
Single Message System Credit Card Processing
Payouts that are processed through
Visa Direct
use Visa’s Single
Message System (SMS). In the SMS, a separate authorization and capture are not required.
The SMS processes transactions in a single message, which includes both the
authorization and the capture of the transaction. An AFT consists of a single pull funds transfer request. An OCT consists of a single
push funds transfer request.
Supported Sender Card Types
Supported Sender Card Types
These card types are supported :
- Mastercard
- Visa
Payment Networks
Networks
- Visa Direct
- The Visa Direct payment network provides these functions forPayouts:
- Enhanced message types forAFTs andOCTs.
- 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.
Requirement
You must meet these requirements in order to use AFTs:
- Have approval from your acquirer to enable AFTs.
- YourCybersourceaccount has Payouts enabled and configured.
- Your acquirer has updated the Merchant Category Codes (MCCs) into theCybersourcesystem.
- Agree to the MLE Beta agreement.
- Generate an API key. For more information, see REST API Key with a Shared Secret Key.
The Pull funds transfer is a pilot feature with no SDK support at this time.
AFT Limitations
AFT limitations affect how quickly a transaction is processed. These limitations include
restrictions on the maximum transaction amounts allowed per time period.
AFT Velocity Limits
These transaction amount limits in USD per time period apply to all AFTs.
AFT Transaction Type | 1-Day Time Period | 7-Day Time Period | Thirty-Day Time Period |
Domestic Money Transfer | 100,000 | 250,000 | 500,000 |
Cross-Border Money Transfer | 50,000 | 100,000 | 200,000 |
Domestic Non-Money Transfer | 100,000 | 250,000 | 500,000 |
Cross-Border Non-Money Transfer | 50,000 | 100,000 | 200,000 |
IMPORTANT
Domestic limits apply to intra-EEA transactions. These transactions occur within
the European Economic Area (EEA) and include EU countries as well as Iceland,
Liechtenstein, and Norway.
AFT Maximum Transaction Amounts
These are the maximum transaction amounts in USD for all AFTs:
- Domestic Money Transfer: 100,000
- Cross-Border Money Transfer: 25,000
- Domestic Non-Money Transfer: 50,000
- Cross-Border Non-Money Transfer: 50,000
IMPORTANT
Domestic limits apply to intra-EEA transactions. These transactions occur within
the European Economic Area (EEA) and include EU countries as well as Iceland,
Liechtenstein, and Norway.
AFT Transactions
The Account Funding Transaction (AFT) allows the transfer of funds between a payment card
and another account, including other payment cards. When used independently, an AFT can
only transfer funds between accounts owned by the same person or business entity. An AFT
is not intended for paying goods and services, funding a merchant account, or repaying
debts.
IMPORTANT
You must receive approval from
your
processor
before using the AFT services. Contact your processor
to register in the AFT program.Pull Services
Pull Services are designed to facilitate the movement of funds from a sender's
account to a recipient's account. This process is initiated by an AFT, which ensures
a secure and efficient transfer of funds. These services are essential for managing
transactions where you need to withdraw funds from a customer's account.
Types of Pull Services
These are several types of Pull Services available to you:
- Pull Funds Transfer Service: Allows you to initiate a transfer of funds from a sender's account to your account. It is commonly used for collecting payments or transferring funds between accounts.
- Pull Transfer Reversal Service: Enables you to return the funds to the sender's account if you need to reverse a transfer, this service. This is useful in cases of errors or disputes.
- Pull Funds Transfer Refund Service: Provides a mechanism for refunding a transaction, allowing you to return funds to the sender's account when necessary.
Benefits
Using the Pull Services offers these advantages:
- Efficiency: Streamlines the process of fund transfers, reducing the time and effort required.
- Security: Ensures that transactions are conducted securely, protecting both you and your customers.
- Flexibility: Offers various services to meet different transaction needs, from transfers to reversals and refunds.
Pull Funds Transfer Service
An AFT withdraws funds from a sender’s account. Some countries or regions have
mandatory fields for specific cases, such as a cross-border AFT. For more information about
country or regional requirements, see the Visa Direct AFT Processing guide. These fields are
not mandatory, but they are required in Visa’s processing rules.
Endpoints
Production:
POST https://api.cybersource.com/pts/v1/pull-funds-transfer
Test:
POST https://apitest.cybersource.com/pts/v1/pull-funds-transfer
Pull Funds Transfer Required Fields
These fields are required in a request for a Pull Funds Transfer:
- Sender card information or a Token Management Service (TMS) payment token is required.
Pull Funds Transfer Optional Fields
These fields are optional in a request for a Pull Funds Transfer:
- This field indicates that the funds transfer is for a cryptocurrency transaction.
- processingInformation.fundingOptions.initiator.originatorInitiatedTransaction. originalTransactionId
- processingInformation.fundingOptions.initiator.originatorInitiatedTransaction. reason
- processingInformation.fundingOptions.initiator.storedCredentialUsed
- processingInformation.payoutsOptions.retrievalReferenceNumber
- recipientInformation.descriptor
- recipientInformation.identificationNumber
- recipientInformation.personalIdentification.id
- recipientInformation.personalIdentification.issuingCountry
- recipientInformation.personalIdentification.personalIdType
- recipientInformation.personalIdentification.type
- recipientInformation.type
- senderInformation.address2
- senderInformation.consumerAuthentication.cavv
- senderInformation.consumerAuthentication. strongAuthentication.delegatedAuthenticationExemptionIndicator
- senderInformation.consumerAuthentication.strongAuthentication. lowValueExemptionIndicator
- senderInformation.consumerAuthentication.strongAuthentication. riskAnalysisExemptionIndicator
- senderInformation.consumerAuthentication.strongAuthentication. secureCorporatePaymentIndicator
- senderInformation.consumerAuthentication.strongAuthentication. trustedMerchantExemptionIndicator
- senderInformation.country
- senderInformation.paymentInformation.accountType
- senderInformation.paymentInformation.card.securityCode
- senderInformation.paymentInformation.card.type
- These are the valid values:
- 001: Visa
- 002: Mastercard
- 024: Maestro
- 033: Visa Electron
- senderInformation.paymentInformation.customer.id
- The value is the TMS customer token identification.
- senderInformation.personalIdentification.id
- senderInformation.paymentInstrument.id
- senderInformation.paymentInstrumentIdentifier.id
- senderInformation.personalIdentification.issuingCountry
- senderInformation.personalIdentification.personalIdType
- senderInformation.personalIdentification.type
REST Example: Pull Funds Transfer
Request with a PAN card
This example shows a Pull Funds Transfer request with a PAN card.
{ "clientReferenceInformation": { "code": "33557799", "applicationName": "EXAMPLE API", "applicationVersion": "V1", "applicationUser": "example_user" }, "orderInformation": { "amountDetails": { "totalAmount": "53.00", "currency": "USD" } }, "processingInformation": { "commerceIndicator": "INTERNET", "businessApplicationId": "WT", "purposeOfPayment": "example" }, "recipientInformation": { "administrativeArea": "TX", "countryCode": "US", "firstName": "Jennifer", "middleInitial": "M", "lastName": "Doe", "identificationNumber": "1234567890", "type": "I", "descriptor": "Jennifer1234", "address1": "123 Main St", "address2": "Suite 4000" }, "senderInformation": { "postalCode": "94440", "firstName": "John", "middleInitial": "A", "lastName": "Doe", "address1": "567 Paseo Padre Boulevard", "address2": "Apt 4", "locality": "Foster City", "administrativeArea": "CA", "country": "US", "paymentInformation": { "card": { "type": "001", "securityCode": "123", "number": "4111111111111111", "expirationMonth": "12", "expirationYear": "2030" }, "accountType": "30" }, "personalIdentification": { "issuingCountry": "US", "id": "123abc", "type": "TXIN", "personalIdType": "I" }, "referenceNumber": "123456" } }
Response to a Successful Request
This example shows a Pull Funds Transfer response with a PAN card.
{ "_links": { "refund": { "href": "/pts/v1/pull-funds-transfer/7180269028616978704951/refund", "method": "POST" }, "reversal": { "href": "/pts/v1/pull-funds-transfer/7180269028616978704951/reversal", "method": "POST" }, "self": { "method": "GET", "href": "/pts/v1/pull-funds-transfer/7180269028616978704951" } }, "processorInformation": { "approvalCode": "98765X", "transactionId": "798964527787170", "systemTraceAuditNumber": "903083", "retrievalReferenceNumber": "416213903083", "responseCode": "5" }, "id": "7180269028616978704951", "status": "AUTHORIZED", "submitTimeUtc": "2027-06-10T13:41:42Z" }
REST Example: Pull Funds Transfer with TMS
Request with TMS tokens
This example shows a Pull Funds Transfer request with tokens.
{ "senderInformation": { "firstName": "Ellen", "lastName": "Torres", "address": "123 N Test St", "middleInitial": "A", "countryCode": "US", "postalCode": "94404", "locality": "Foster City", "administrativeArea": "CA" }, "paymentInformation": { "customer": { "id": "B21E6717A6F03479E05341588E0A303F" }, "paymentInstrument": { "id": "B21E6B7E8BB3388EE05341588E0AFC84" }, "shippingAddress": { "id": "B21E6717A6F33479E05341588E0A303F" } }, "recipientInformation": { "firstName": "Amit", "lastName": "Gupta", "countryCode": "US", "administrativeArea": "CA", "identificationNumber": "123456789", "type": "I" }, "processingInformation": { "commerceIndicator": "INTERNET", "businessApplicationId": "PP" }, "orderInformation": { "amountDetails": { "totalAmount": "100", "currency": "USD" } }, "clientReferenceInformation": { "code": "REF123456", "applicationName": "Great Stuff Storefront", "applicationUser": "G. Miller" } }
Response: Pull Funds Transfer with TMS
This example shows a Pull Funds Transfer response with tokens.
{ "_links": { "refund": { "href": "/pts/v1/pull-funds-transfer/6668885718936344401953/refund", "method": "POST" }, "reversal": { "href": "/pts/v1/pull-funds-transfer/6668885718936344401953/reversal", "method": "POST" }, "self": { "method": "GET", "href": "/pts/v1/pull-funds-transfer/6668885718936344401953" } }, "processorInformation": { "approvalCode": "98765X", "transactionId": "393209441134856", "systemTraceAuditNumber": "572474", "responseCode": "5" }, "id": "6668885718936344401953", "status": "AUTHORIZED", "submitTimeUtc": "2027-10-27T16:36:12Z" }
Pull Transfer Reversal Service
Use an AFT reversal transaction to reverse an AFT within 24 hours of the original
transaction time. You must complete this before the transaction settles.
Endpoints
Production:
POST
https://api.cybersource.com/pts/v1/pull-funds-transfer/{id}/reversal
Test:
POST
https://apitest.cybersource.com/pts/v1/pull-funds-transfer/{id}/reversal
Pull Funds Transfer Reversal Required Fields
This field is required in a request for a Pull Funds Transfer reversal:
Pull Funds Transfer Reversal Optional Fields
These fields are optional in a request for a Pull Funds Transfer Reversal:
REST Example: Pull Funds Reversal Transfer
Request
This example shows a Pull Funds Transfer reversal request.
{ "reversalInformation": { "amountDetails": { "totalAmount": "5", "currency": "USD" } } }
Response
This example shows a Pull Funds Transfer reversal response.
{ "processorInformation": { "responseCode": "5", "approvalCode": "98765X", "transactionId": "858133930771324", "systemTraceAuditNumber": "572474" }, "id": "6668886748826345201953", "_links": { "self": { "method": "GET", "href": "/pts/v1/pull-funds-transfer/6668886748826345201953" } }, "status": "REVERSED", "submitTimeUtc": "2022-10-27T16:37:55Z" }
Pull Transfer Refund Service
Use an AFT refund transaction to send funds back to the sender's card within 30 days
of the original AFT. The funds cannot be traced if the original transaction is over
30 days old. You can accept a refund after the original AFT settles.
Endpoints
Production:
POST https://api.cybersource.com/pts/v1/pull-funds-transfer/{id}/refund
Test:
POST https://apitest.cybersource.com/pts/v1/pull-funds-transfer/{id}/refund
Pull Funds Transfer Refund Required Fields
This field is required in a request for a Pull Funds Transfer refund:
Pull Funds Transfer Refund Optional Fields
These fields are optional in a request for a Pull Funds Transfer refund:
REST Example: Pull Funds Transfer Refund
Request
This example shows a Pull Funds Transfer refund request.
{ "orderInformation": { "amountDetails": { "totalAmount": "95" } } }
Response
This example shows a Pull Funds Transfer refund response.
{ "processorInformation": { "transactionId": "351083755930580", "systemTraceAuditNumber": "761442" }, "id": "6668887829136346401953", "_links": { "self": { "method": "GET", "href": "/pts/v1/pull-funds-transfer/6668887829136346401953" } }, "status": "ACCEPTED", "submitTimeUtc": "2027-10-27T16:39:43Z" }
Reference
This section provides helpful reference information for using Payouts services.
Business Application Identifier
The Business Application Identifier (BAI) identifies the category of the Account Funding
Transaction (AFT).
All acquirers, service providers, and merchants must submit a valid BAI value when
submitting an AFT.
Provide one of the values when you send field .
processingInformation.businessApplicationId
IMPORTANT
Ensure that your acquirer has a Merchant
Category Code (MCC) that corresponds with the BAI value you are using. For more
information, contact your acquirer.
BAI Value | Category | Merchant Category Code | Transfer Type | Requirements |
---|---|---|---|---|
AA | Account-to-Account money transfer. This is
for funding the cardholder's own account at the same or a different
financial institution. | 4829 Non-Financial
Institution Wire Transfer Money Orders (not applicable in the US with
BAI AA )6012 Financial Institutions
– Merchandise and Services6211 Security
Brokers/Dealers | Money transfer | 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. | 6012 Financial
Institutions – Merchandise and Services | Money transfer | P2P (Person-to-Person)
Money transfer is initiated from an online banking system, making it a
bank-initiated transaction. BAI BI should be used
with MCC 6012 .BI for a
me-to-me or person-to-person transfer. IMPORTANT
This category is used only for specific scenarios and
available only in limited markets. For more information, contact
your Visa representative. |
FD | Funds Disbursement | Any MCC associated with the
merchant | Non-Money transfer | Insurance payout in which a third party
uses an AFT to fund the disbursement of OCT on behalf of the
insurance company. |
FT | Funds Transfer | 4829 Non-Financial
Institution Wire Transfer Money Orders (WTMOs)6012
Financial Institutions – Merchandise and
Services6540 Non-Financial Institutions
– Stored Value Card Purchase/LoadIf you use funds for a
high-brand risk transaction, the applicable high-brand risk MCC must
be used. If the general purpose wallet is used to purchase
liquid and cryptocurrency assets, the applicable special condition
indicator (Field 60.4) = 7 must be used. Non-Fiat Currency is
replaced with liquid and cryptocurrency assets. 6211 Security Brokers/Dealers | Money transfer | Adding funds to or cashing out a Stored
Value Digital Wallet (SVDW) account. Funding a Money Transfer
in which the OCT is not enabled as the push mechanism to the
recipient. LA
instead of FT for cashing out funds if the wallet is a
general-purpose wallet, and 50% or more of their annual sales volume
comes from liquid or cryptocurrency
assets. |
PD | Payroll Disbursement | 8931 Accounting, Auditing, and Bookkeeping services
including Payroll | Non-Money transfer | When a payroll provider disburses payroll
on behalf of the small business who funds the transactions. |
PP | Person-to-Person ( P2P )
Money Transfer | 4829 Non-Financial
Institution Wire Transfer Money Orders 6012
Financial Institutions – Merchandise and
Services6012 Financial Institutions-
Merchandise and Services | Money transfer | Services that support AFT and OCT. If only
AFT is supported, you must use BAI FT . |
TU | Prepaid Card Load or Top-Up | 6012 Financial
Institutions – Merchandise and Services.6051
Non-Financial Institutions – Foreign Currency, Liquid and
Cryptocurrency Assets (for example, Cryptocurrency), Money Order
(not Money Transfer), Travelers Check, and Debt
Repayment6540 Non-Financial Institutions –
Stored Value Card Purchase/Load | Non-Money transfer | Merchants that sell other goods and
services in addition to stored value cards and offer prepaid card load
capability can use the MCC associated with the merchant’s primary
business in accordance with the Visa Merchant Data Standards
Manual. |
WT | 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 Cheques, and Debt
Repayment.An AFT is not intended for debt repayment. 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. | Money transfer | When a Visa card is used to fund a SDW
before the cardholder makes a purchase, you must use an AFT with a
BAI WT . WT must be used only by
registered Staged Digital Wallet Operators (SDWO).For
additional information on SDW transactions, visit the SDWO section
at Visa Access (Visa Online). Contact your Visa representative for
additional information and requirements for digital
wallets. Effective October 2024: Field 104 – Sender Data and
Recipient Name will be required to support cross-border AFT. 0494
(when a field or data is missing or invalid). |
Sender Source
The Sender Source field identifies the source of funds. Provide one of the values when
you send field .
senderInformation.account.fundsSource
All acquirers, service providers, and merchants are required to submit a valid sender
source value when submitting an AFT.
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 senderInformation.account.fundsSource |
06 | Credit accounts that is not linked to a
Visa card such as credit cards and proprietary lines of credit. |
07 | Mobile wallet account |
08 | Other source of funds |
Visa Direct BAI to Mastercard TTI Mapping
Direct
BAI to Mastercard TTI MappingThis table shows how Visa BAI to Mastercard TTI mappings and their descriptions, and transaction types.
Visa Direct BAI to Mastercard TTI
Visa Business Application Identifier (BAI) | Mastercard Transaction Type Indicator (TTI) via PPGS |
---|---|
AA : Account to account | C52 : MoneySend account-to-account
transfer |
BB : Business to business (does not apply to
US) | C65 : MoneySend business-to-business
transfer |
BI : Money transfer—bank initiated (US domestic
only) | C07 : MoneySend person-to-person transfer |
CO : Cash out | C53 : MoneySend agent cash out |
CP : Card bill payment | C54 : MoneySend credit card bill payment |
FD : Funds disbursement (general) | C55 : MoneySend business disbursements |
FT : Funds transfer | C52 : MoneySend account-to-account
transfer |
GD : Government disbursement | C56 : MoneySend government/non-profit
disbursement |
GP : Gambling payouts | C04 : Gaming repay |
LO : Loyalty and offers | C55 : MoneySend business disbursements |
MD : Merchant disbursement | C57 : MoneySend acquirer merchant
settlement |
OG : Online gambling payout | C04 : Gaming repay |
PD : Payroll/pension disbursement | C55 : MoneySend business disbursements |
PP : Person to person | C07 : MoneySend person-to-person transfer |
TU : Top-up for enhanced prepaid loads (does not
apply for PPGS) | F64 : Transfer to own debit or prepaid card
account |
WT : Wallet transfer | C52 : MoneySend account-to-account
transfer |
Testing the Pull Funds Transfer Service
The table lists action codes, their descriptions, HTTP status codes, response
statuses, responses to
errorInformation.reason
fields, and
simulator trigger amounts. You can interpret and understand these codes when testing
the Pull Funds Transfer Service.Visa Action Code | Visa Code Description | Cybersource HTTP Status Code | Cybersource Response Status | Cybersource Response | Simulator Trigger Amount |
---|---|---|---|---|---|
0 | Approved and completed
successfully | 201 | AUTHORIZED | All mandatory fields present | |
1 | Refer to card issuer | 201 | DECLINED | CONTACT_PROCESSOR | 1100.01 |
2 | Refer to card issuer, special
condition | 201 | DECLINED | CONTACT_PROCESSOR | 1100.02 |
3 | Invalid merchant | 201 | DECLINED | INVALID_MERCHANT_CONFIGURATION | 1100.03 |
4 | Pick up card (no fraud) | 201 | DECLINED | STOLEN_LOST_CARD | 1100.04 |
5 | Do not honor | 201 | DECLINED | PROCESSOR_DECLINED | 1100.05 |
6 | Error | 201 | DECLINED | PROCESSOR_DECLINED | 1100.06 |
7 | Pick up card, special condition (fraud account) | 201 | DECLINED | STOLEN_LOST_CARD | 1100.07 |
10 | Partial approval | 201 | PARTIAL_AUTHORIZED | PARTIAL_APPROVAL | 1100.1 |
11 | Approved (V.I.P) | 201 | AUTHORIZED | 1100.11 | |
12 | Invalid transaction | 201 | DECLINED | PAYMENT_REFUSED | 1100.12 |
13 | Invalid amount or currency
conversion field overflow | 201 | DECLINED | PAYMENT_REFUSED | 1100.13 |
14 | Invalid account number (no such number) | 201 | DECLINED | PROCESSOR_DECLINED | 1100.14 |
15 | No such issuer | 201 | DECLINED | ISSUER_UNAVAILABLE | 1100.15 |
19 | Re-enter transaction | 201 | DECLINED | PROCESSOR_DECLINED | 1100.19 |
21 | No action taken | 201 | DECLINED | PROCESSOR_DECLINED | 1100.21 |
25 | Unable to locate record in file | 201 | DECLINED | PROCESSOR_DECLINED | 1100.25 |
28 | File temporarily not available for update or inquiry | 201 | DECLINED | PROCESSOR_DECLINED | 1100.28 |
39 | No credit account | 201 | DECLINED | GENERAL_DECLINE | 1100.39 |
41 | Lost card, pick up (fraud account) | 201 | DECLINED | STOLEN_LOST_CARD | 1100.41 |
43 | Stolen card, pick up (fraud account) | 201 | DECLINED | STOLEN_LOST_CARD | 1100.43 |
51 | Not sufficient funds | 201 | DECLINED | INSUFFICIENT_FUND | 1100.51 |
52 | No checking account | 201 | DECLINED | PROCESSOR_DECLINED | 1100.52 |
53 | No savings account | 201 | DECLINED | PROCESSOR_DECLINED | 1100.53 |
54 | Expired card or expiration date is missing | 201 | DECLINED | EXPIRED_CARD | 1100.54 |
55 | Incorrect PIN or PIN missing | 201 | DECLINED | INVALID_PIN | 1100.55 |
57 | Transaction not permitted to cardholder | 201 | DECLINED | UNAUTHORIZED_CARD | 1100.57 |
59 | Suspected fraud | 201 | DECLINED | PROCESSOR_DECLINED | 1100.59 |
61 | Exceeds approval amount limit | 201 | DECLINED | EXCEEDS_CREDIT_LIMIT | 1100.61 |
62 | Restricted card (card invalid in this region or country) | 201 | INVALID_REQUEST | UNAUTHORIZED_CARD | 1100.62 |
63 | Security violation (source is not correct issuer) | 201 | DECLINED | ISSUER_UNAVAILABLE | 1100.63 |
64 | Transaction does not fulfill AML requirement | 201 | DECLINED | GENERAL_DECLINE | 1100.64 |
65 | Exceeds withdrawal frequency limit | 201 | INVALID_REQUEST | DEBIT_CARD_USAGE_LIMIT_EXCEEDED | 1100.65 |
74 | Different value than what is used for PIN encryption error | 201 | DECLINED | GENERAL_DECLINE | 1100.74 |
75 | Allowable number of PIN entry tries exceeded | 201 | INVALID_REQUEST | DEBIT_CARD_USAGE_LIMIT_EXCEEDED | 1100.75 |
76 | Unsolicited reversal | 201 | INVALID_REQUEST | MISSING_AUTH | 1100.76 |
79 | Already reversed (by switch) | 201 | INVALID_REQUEST | AUTH_ALREADY_REVERSED | 1100.79 |
80 | No financial impact | 201 | INVALID_DATA | INVALID_DATA | 1100.80 |
81 | Cryptographic error found in PIN | 201 | DECLINED | GENERAL_DECLINE | 1100.81 |
82 | Negative CAM, dCVV, iCVV, or CVV
results | 201 | DECLINED | CVN_NOT_MATCH | 1100.82 |
85 | No reason to decline a request for address verification, CVV2 verification, or a credit voucher or merchandise return | 201 | AUTHORIZED | 1100.85 | |
86 | Cannot verify PIN; for example, no PVV | 201 | DECLINED | GENERAL_DECLINE | 1100.86 |
89 | Ineligible to receive financial position info (GIV) | 201 | DECLINED | PROCESSOR_DECLINED | 1100.89 |
91 | Issuer or switch inoperative and
Stand-in Processing (STIP) not applicable or not available for this
transaction; Time-out when no stand-in; POS (Point of Sale) Check
Service: Destination unavailable; Credit Voucher and Merchandise
Return Authorizations: V.I.P. sent the transaction to the issuer,
but the issuer was unavailable. | 201 | DECLINED | PROCESSOR_DECLINED | 1100.91 |
92 | Duplicate transmission. Transaction
submitted containing values in tracing data fields that duplicate
values in a previously submitted transaction. This code is available
in SMS raw data in case of duplicate transmission. | 201 | DECLINED | DUPLICATE_REQUEST | 1100.92 |
93 | Transaction cannot be
completed-violation of law | 201 | DECLINED | PROCESSOR_DECLINED | 1100.93 |
B1 | Surcharge amount not permitted on Visa cards or EBT food stamps (US acquirers only) | 201 | DECLINED | GENERAL_DECLINE | 11002.01 |
B2 | Surcharge amount not supported by debit network issuer. | 201 | DECLINED | GENERAL_DECLINE | 11002.02 |
N0 | Force STIP | 201 | DECLINED | PROCESSOR_DECLINED | 11002.03 |
N3 | Cash service not available | 201 | DECLINED | PROCESSOR_DECLINED | 11002.04 |
N4 | Cash request exceeds issuer or approved limit | 201 | DECLINED | EXCEEDS_CREDIT_LIMIT | 11002.05 |
N5 | Ineligible for resubmission | 201 | INVALID_DATA | INVALID_DATA | 11002.06 |
N7 | Decline for CVV2 failure | 201 | DECLINED | CVN_NOT_MATCH | 11002.07 |
N8 | Transaction amount exceeds
pre-authorized approval amount | 201 | INVALID_REQUEST | EXCEEDS_AUTH_AMOUNT | 11002.08 |
Q1 | Card authentication failed | 201 | DECLINED | GENERAL_DECLINE | 11002.09 |
R0 | Stop payment order | 201 | DECLINED | PROCESSOR_DECLINED | 11002.1 |
R2 | Revocation of authorization
order | 201 | DECLINED | PROCESSOR_DECLINED | 11002.11 |
R3 | Revocation of all authorizations order | 201 | DECLINED | PROCESSOR_DECLINED | 11002.12 |
T0 | First-time check | 201 | DECLINED | PROCESSOR_DECLINED | 11002.13 |
T1 | Check is OK, but cannot be
converted | 201 | DECLINED | PROCESSOR_DECLINED | 11002.14 |
T2 | Invalid routing transit number | 201 | DECLINED | PROCESSOR_DECLINED | 11002.15 |
T3 | Amount greater than established service limit | 201 | DECLINED | EXCEEDS_CREDIT_LIMIT | 11002.16 |
T4 | Unpaid items, failed negative file check (POS Check Service, US only) | 201 | DECLINED | PROCESSOR_DECLINED | 11002.17 |
T5 | Duplicate check number | 201 | DECLINED | PROCESSOR_DECLINED | 11002.18 |
T6 | MICR error | 201 | DECLINED | PROCESSOR_DECLINED | 11002.19 |
T7 | Too many checks | 201 | DECLINED | PROCESSOR_DECLINED | 11002.2 |
Y1 | Offline-approved | 201 | AUTHORIZED | SUCCESS | 11002.21 |
Y3 | Unable to go online; offline-approved | 201 | AUTHORIZED | SUCCESS | 11002.22 |
Z1 | Offline-declined | 201 | DECLINED | PROCESSOR_DECLINED | 11002.23 |
Z3 | Unable to go online; offline-declined | 201 | DECLINED | PROCESSOR_DECLINED | 11002.24 |
NA | The POST transaction timed out. If the API is not able to complete the transaction within 30 seconds (default) or within the timeout duration set in the HTTP header, it will respond with an 202 HTTP Status Code and a statusIdentifier value that can be used in the GET operation as the statusIdentifier in the URI. | 201 | SERVER_ERROR | GATEWAY_TIMEOUT | 2.02 |
NA | The API detected a duplicate transaction. | 201 | INVALID_REQUEST | DUPLICATE_REQUEST | 3.03 |
NA | The transaction was rejected by Visa due to a message validation error. | 201 | INVALID_REQUEST | INVALID_DATA | 40030.01 |
NA | Velocity limit exceeded | 201 | INVALID_REQUEST | INVALID_DATA | 40080.01 |
NA | This is returned due to client certificate does not matched with the one issued by Visa. | 201 | SERVER_ERROR | SYSTEM_ERROR | 40191.25 |
NA | This is returned if user credentials are wrong. | 201 | SERVER_ERROR | SYSTEM_ERROR | 40191.23/ 40191.24 |
NA | The URL access is not permitted. | 201 | SERVER_ERROR | SYSTEM_ERROR | 40396.11 |
NA | The message contains an invalid Primary Account Number (PAN) | 201 | INVALID_REQUEST | INVALID_DATA | 40430.01 |
NA | The URL is invalid or the Resource could not be found. | 201 | INVALID_REQUEST | INVALID_DATA | 4.04 |
NA | These are returned when an internal server error occurs. | 201 | SERVER_ERROR | SYSTEM_ERROR | 50010.01/ 50020.01 |
NA | These are returned when a Cybersource server error occurs. | 201 | SERVER_ERROR | SYSTEM_ERROR | 5.02 |
NA | This may be due to network connectivity issue. | 201 | SERVER_ERROR | SERVICE_UNAVAILABLE | 5.03 |
NA | Timeout which may be due to network connectivity issue. | 201 | SERVER_ERROR | GATEWAY_TIMEOUT | 5.04 |
Test Card Numbers
Use the Mastercard or Visa test payment card numbers to test the Pull Funds Transfer
service. Do not use real payment card numbers. For test card numbers, see Testing Guides.
You can use any of the testing card numbers in the linked guide, unless you are
testing cross-border transactions. If you are testing a cross-border transaction,
you must ensure that your specific scenario uses these fields and configurations:
- Use a sender test card that contains a BIN for the card-issuer country.
- Ensure that the merchant address country is correctly set in the Cybersource system.
- Ensure that the acquirer country is correctly set in the payouts configuration.
You can find domestic and cross-border identification in the Visa Direct AFT
Processing Guide. For more information about domestic and cross border
identification, see the Visa Direct AFT
Processing Guide.