Please try searching something.
Tables
Overview
Payment scenarios tables provide a clear and structured reference explaining how payments are processed. These tables serve as a reference for understanding and implementing payment processes. Each scenario typically includes a set of details, conditions, and outcomes, providing clear guidance for the handling of payments.
CVC2 / CVV2 Usage Table for MOTO Transactions
| Mail Order | Telephone order | |
|---|---|---|
| Visa cards | CVV2 is not mandatory | CVV2 is mandatory |
| Mastercard cards | CVC2 is not mandatory | CVC2 is not mandatory |
| Maestro cards | CVC2 is mandatory | CVC2 is mandatory |
Actions
Action1 – normal status for payment executions Step 1, specifies that not all mandatory details for payment execution are present. In the next request (Step 2), the required details must be passed.
Action2 – faulty status, must be treated as an error, specifies the label selection.
Action3 – faulty status, must be treated as an error, specifies the instrument selection.
Action4 – normal status for DMS payment (Step 2) and Person to Person payments (Step 1), specifies that the next request must contain a confirmed element with a value equal to "true".
Action5 – faulty status, must be treated as an error, incorrect PIN.
Action6 – if within the payment execution Step 2 (Step 3 for DMS payments) the finished element was not passed, then in the next request this element must be passed with a value "true". If in the payment execution Step 2 (Step 3 for DMS payments) the finished element with the value "true" was passed, then it must be treated as an error.
Action10 – normal status for Step 2 (Step 3 for DMS payments), specifies that the payment has been finished successfully.
Payment Statuses
Active - this status indicates that the payment is currently in progress. The payment execution is still ongoing, and it has not yet been completed, canceled, or returned.
Finished - this status indicates that payment execution has been successfully completed. The payment has gone through without any issues.
Canceled - this status indicates that the payment was canceled during its execution. This can happen for various reasons, including a decline on the payment system (WPS) or issuer side, internal system errors, or payment execution timeout. It can also occur when the CancelRequest method is called to cancel the payment.
Returned - this status indicates that the payment has been returned by calling ReturnPayment method, reversal or refund was sent.
Authorisation Response Codes
Following the ISO8583’93 standard authorisation response codes may be used in error response to identify the decline reason.
Codes 1XX and 2XX are usually provided by the card issuer to identify the decline reason.
Codes 9XX identify technical problems with processing of authorisation – in most cases, the problems are short term and payment may be resubmitted.
| Code | B.39 Response Code (Visa) | DE 39 Response Code (Mastercard) | Status | Description |
|---|---|---|---|---|
| 000 | 00, 85 | 00 | Approved | Approved |
| 001 | 08 | Approved with ID | Approved, honor with identification | |
| 002 | 10 | 10 | Approved | Approved for partial amount |
| 003 | 11 | 00 | Approved | Approved for VIP |
| 004 | 85 | Approved | Approved, update track 3 | |
| 006 | 00 | Approved | Approved for a partial amount, account type specified by the card issuer | |
| 007 | 00 | Approved | Approved, update ICC | |
| 008 | 87 | Approved | Approved, purchase only, no cashback allowed | |
| 100 | 05, N0 | 05 | Decline | Decline (general, no comments) |
| 101 | 54 | 54, could be used in combination with DE48 SE84 = 01 (meaning "New account information available") | Decline | Decline, expired card |
| 102 | 59 | 63 | Decline | Decline, suspected fraud |
| 103 | 63 | Decline | Decline, card acceptor contact acquirer | |
| 104 | 62 | 62 | Decline | Decline, restricted card |
| 105 | 63 | Decline | Decline, card acceptor call acquirer's security department | |
| 106 | 75 | 75 | Decline | Decline, allowable PIN tries exceeded |
| 107 | 01 | 01 | Decline | Decline, refer to card issuer |
| 108 | 02, 15, R0 | 01 (If MIT execution and DE39 in [05,14,51,54] and DE48 SE84 = 01) | Decline | Decline, refer to card issuer's special conditions |
| 109 | 03 | 03 | Decline | Decline, invalid merchant |
| 110 | 13, B2, N8 | 13 | Decline | Decline, invalid amount |
| 111 | 14, 46 | 14 | Decline | Decline, invalid card number |
| 112 | 86 | 65 | Decline | Decline, PIN data required |
| 113 | 12 | Decline | Decline, unacceptable fee | |
| 114 | 39, 52, 53 | 12, 76, 77, 78 (If MIT execution and DE39=51 and DE48 SE84 = 02) | Decline | Decline, no account of type requested |
| 115 | N3, R2 | 12 | Decline | Decline, requested function not supported |
| 116 | 51, T4 | 51 | Decline | Decline, not sufficient funds / over credit limit |
| 117 | 55 | 55 | Decline | Decline, incorrect PIN |
| 118 | 14 | Decline | Decline, no card record | |
| 119 | 57 | 57 | Decline | Decline, transaction not permitted to cardholder |
| 120 | 58, 64 | 58, 81 | Decline | Decline, transaction not permitted to terminal |
| 121 | 61, T3 | 61 | Decline | Decline, exceeds withdrawal amount limit |
| 122 | 63,70, 82, N7, Q1, 6P, P6 | 63 | Decline | Decline, security violation |
| 123 | 65,1A,70 | 65 | Decline | Decline, exceeds withdrawal frequency limit |
| 124 | 93 | 57 | Decline | Decline, violation of law |
| 125 | 71, 78 | 72 | Decline | Decline, card not effective |
| 126 | 55 | Decline | Decline, invalid PIN block | |
| 127 | 55 | Decline | Decline, PIN length error | |
| 128 | 55 | Decline | Decline, PIN key sync error | |
| 129 | 82 | 63 | Decline | Decline, suspected counterfeit card |
| 130 | 63 | Decline | Decline, CVC2 check counter exceeded | |
| 160 | 1A (if DE22 = 01 and 60.8 in [08,09]; if DE 60.8 in [05,06,07]) | 65 (if 48.22 = 1 or 48.42 present) | Decline | Decline, additional customer authentication required. Also called Soft Decline |
| 162 | 79 | Decline | Decline, lifecycle violation | |
| 163 | 82 | Decline | Decline, policy violation | |
| 164 | 83 | Decline | Decline, fraud / security violation | |
| 165 | 5C | Decline | Transaction not supported/blocked by issuer | |
| 169 | 9G | Decline | Blocked by cardholder/contact cardholder | |
| 180 | R1, R3 | (if DE39 in [05,14,51,54,79,82,83] and DE48 SE84 = 03; if DE39=05 and DE48 SE84 = 21; if MIT execution and DE39 in [05,14,51,54] and DE48 SE84 = 21) | Decline | Decline by the cardholder's request |
| 1N4 | N4 | Decline | Decline, cashback request exceeds the issuer limit | |
| 200 | 04 | 04 | Pick-up | Pick-up (general, no comments) |
| 201 | 04 | Pick-up | Pick-up, an expired card | |
| 202 | 04 | Pick-up | Pick-up, suspected fraud | |
| 203 | 04 | Pick-up | Pick-up, card acceptor contact card acquirer | |
| 204 | 46 | 46 | Pick-up | Pick-up, restricted card |
| 205 | 04 | Pick-up | Pick-up, card acceptor call acquirer's security department | |
| 206 | 04 | Pick-up | Pick-up, allowable PIN tries exceeded | |
| 207 | 07 | 04 | Pick-up | Pick-up, special conditions |
| 208 | 41 | 41 | Pick-up | Pick-up, lost card |
| 209 | 43 | 43 | Pick-up | Pick-up, stolen card |
| 210 | 04 | Pick-up | Pick-up, suspected counterfeit card | |
| 280 | 46 | 04 | Decline | Decline, card is not active at bank will |
| 400 | 00, 85 | 00 | Accepted | Accepted (for reversal) |
| 902 | 12 | 12, 84 | Call acquirer | Decline reason message: invalid transaction |
| 903 | 19 | 12 | Call acquirer | Status message: re-enter transaction |
| 904 | 06 | 30, 71, 89 | Call acquirer | Decline reason message: format error |
| 905 | 92 | Call acquirer | Decline reason message: acquirer not supported by switch | |
| 906 | 12 | Call acquirer | Decline reason message: cutover in process | |
| 907 | 91 | 91 | Call acquirer | Decline reason message: card issuer or switch inoperative |
| 908 | 92 | 15, 92 | Call acquirer | Decline reason message: transaction destination cannot be found for routing |
| 909 | 74, 96 | 05, 96 | Call acquirer | Decline reason message: system malfunction |
| 910 | 91 | Call acquirer | Decline reason message: card issuer signed off | |
| 911 | 68 | 91 | Call acquirer | Decline reason message: card issuer timed out |
| 912 | 91 | Call acquirer | Decline reason message: card issuer unavailable | |
| 913 | 79, 94 | 94 | Call acquirer | Decline reason message: duplicate transmission |
| 914 | 21, 76, 80 | 81 | Call acquirer | Decline reason message: not able to trace back to original transaction |
| 915 | 12 | Call acquirer | Decline reason message: reconciliation cutover or checkpoint error | |
| 916 | 12 | Call acquirer | Decline reason message: MAC incorrect | |
| 917 | 12 | Call acquirer | Decline reason message: MAC key sync error | |
| 918 | 05 | Call acquirer | Decline reason message: no communication keys available for use | |
| 919 | 05 | Call acquirer | Decline reason message: encryption key sync error | |
| 920 | 05 | Call acquirer | Decline reason message: security software/hardware error - try again | |
| 921 | 81, 86 | 05, 86, 88 | Call acquirer | Decline reason message: security software/hardware error - no action |
| 922 | 30 | Call acquirer | Decline reason message: message number out of sequence | |
| 923 | 05 | Call acquirer | Status message: request in progress | |
| 950 | Not accepted | Decline reason message: violation of business arrangement | ||
| 198 | Decline | Decline, call Card Processing Centre | ||
| 197 | Decline | Decline, call AmEx |
Merchant Advice Code
Mastercard is using specific Merchant Advice Codes to exchange the information between the card issuer (Mastercard) and the merchant. This information can be used by merchants to better understand the position of the issuing bank to accept or decline any further transaction with the specific card.
Mastercard advice codes are provided in SOAP response message fld_126_MS84 TAG. Possible tag values:
| Value | Description |
|---|---|
| 01 | New account information available |
| 02 | Cannot approve at this time, try again later |
| 03 | Do not try again |
| 04 | Token requirements not fulfilled for this token type |
| 05 | Negotiated value not approved |
| 21 | Payment Cancellation |
| 22 | Merchant does not qualify for product code |
| 24 | Retry after 1 hour |
| 25 | Retry after 24 hours |
| 26 | Retry after 2 days |
| 27 | Retry after 4 days |
| 28 | Retry after 6 days |
| 29 | Retry after 8 days |
| 30 | Retry after 10 days |
| 40 | Consumer non-reloadable prepaid |
| 41 | Consumer single-use virtual card number |
| 42 | Sanctions Scoring Service: Score Exceeds Applicable Threshold Value |
Merchants must not repeat the transaction with the same card if they has received the advice code 03 or 21.
Request Element Description
This section describes the element meanings that can be used in requests.
Element and detail format description:
N– Numeric;A– Alpha;AN– Alphanumeric;ANS- Alphanumeric with symbols.
Common Requests Elements
| Parameter | Format | Length | Description |
|---|---|---|---|
| billerRef | ANS | 256 | Biller reference value |
| payinstrRef | ANS | 256 | Instrument reference value |
| switchingID | N | 8 | Switching identifier |
| autoSwitch | N (1 or 0) | 1 | Parameter for automatic switching; if required, then must be equal to "1" |
| confirmed | A (true or false) | 5 | Parameter for payments executions flow; if required, then must be equal to "true" |
| finished | A (true or false) | 5 | Parameter for payments executions flow; if required, then must be equal to "true" |
| paymentID | N | 16 | Unique payment identifier, assigned by the system |
| original_payment_id | N | 16 | Unique payment identifier, assigned by the system; used for referring the original payment to limit the refund amount |
| clientID | ANS | 50 | Unique recurring payment identifier, generated by the merchant's system in format <merchant id>_<unique recurring payments identifier> |
| language | AN (en) | 3 | Language identifier for switching state |
Common Request Details
| Parameter | Format | Length | Description |
|---|---|---|---|
| pan | N | 19 | Primary account number |
| expiry | N | 4 | Expiration date (YYMM) |
| avs_data | ANS | MC-29 Visa-49 |
Data for Address Verification Service |
| amount | N | 12 | Amount |
| ccy_code | N | 3 | Currency code |
| merchant_id | N | 15 | Card acceptor identification code for credit transactions |
| point_code | AN | 12 | Point of service data code |
| cookie_info_id | ANS | 1024 | Clients cookie identifier |
| cardname | ANS | 1024 | Cardholder's name |
| client_ip_addr | ANS | 1024 | Client IP address |
| etid | A | 1 | Parameter for merchant_name details usage; if equal to "Y", then merchant_nameS is used |
| merchant_name | ANS | 99 (contains subfields; total subfield length: 40) | Merchant's name included in the authorisation message; used together with etid detail |
| csc | N | 3 | CVC2/CVV2 |
| sli | N | 3 | Security Level Indicator; only for Mastercard |
| xid | ANS | 28 | Transaction identifier; non-3D secure payments should not contain xid detail |
| cavv | ANS | 28 | Cardholder Authentication Verification Value; mandatory for Mastercard, Visa and UPI cards EMVCo 3DS (3dsv2) payments, if mdStatus equals "1" or "4" (base64 encoding must be used) |
| tavv | ANS | 28 | Token Cryptogram (for Mastercard: DSRP Cryptogram; for Visa: Token Authentication Verification Value (TAVV)) - Apple Pay: data.paymentData.onlinePaymentCryptogram - Google Pay: cryptogram |
| eci | N | 2 | Electronic Commerce Indicator for Visa and UPI cards and Visa tokenized wallet payments |
| 3ds_protocol | ANS | 8 | 3D protocol version used for 3D authentication; allowed values: 3DS2.1.0 - for 3DS 2.1.x (EMV 3DS) 3DS2.2.0 - for 3DS 2.2.x (EMV 3DS) 3DS2.3.1 - for 3DS 2.3.x (EMV 3DS) |
| 3ds_ds_id | ANS | 36 | Directory Server Transaction ID, used for EMV 3DS Mastercard and UPI transactions |
| transStatus | A | 1 | Transaction status, equals with paresTxStatus or TDS2.transStatus received from MPI |
| moto | A | 1 | Detail governing point code passed to ICO; if equal to "Y", then the point code of MOTO transaction will be used (default value "N") |
| ppwi | AN | 3 | Wallet id. Allowed values for tokenized wallet payments: “103” for ApplePay; “216” for GooglePay. For DWO wallets the Wallet ID is assigned by Mastercard |
| merchant_url | ANS | 150 | Merchant business website URL or reverse domain; base64 encoded (only for Mastercard) |
| sca_exemptions | A | 4 | SCA exemption flag, if the transaction is applied for SCA exemption. Allowed values: "1" for low value exemption; "01" for acquirer risk analysis; "0001" for secure corporate exemption; "00000001" for authentication outage exemption |
| sl_city | ANS | 13 | Service Location city |
| sl_region | ANS | 3 | Service Location country subdivision code |
| sl_country | ANS | 10 | Service Location country code |
| sl_index | ANS | 10 | Service Location postal code |
| mp_mvv | N | 8 | Visa assigned identifier (MVV code) of Visa Marketplace |
| mp_fr | A | 1 | Visa Marketplace foreign retailer indicator; equals to "Y", if domestic marketplace transaction is completed by a foreign marketplace retailer; otherwise this detail should be omitted |
| gate_id | N | 11 | Merchant Payment Gateway ID provided by Mastercard. The value must be right-justified with leading zeros |
Recurring Payment Specific Details
Details governing recurring payments registration, storing card data on DECTA side, and its execution conditions.
| Parameter | Format | Length | Description |
|---|---|---|---|
| perspayee_gen | N | 1 | Main detail governing recurring payments registration; if equal to "1", then the personal payment will be generated other way |
| recurring | A | 1 | Detail governing point code and environment type passed to ICO |
| biller_client_id | N | 35 | Unique recurring payments identifier, generated in the merchants' application in the following format <merchant id>_<unique recurring payment identifier>. During the recurring payments execution, this value must be passed in clientID element |
| perspayee_expiry | N | 4 | Expiry date for personal payment in format MMYY |
| perspayee_overwrite | N | 1 | If present and equals to "1", the existing personal payments will be overwritten; otherwise, only new payment will be created (if such payment already exists, nothing will be done); cannot be present at the same time as perspayee_duplicate |
| perspayee_duplicate | N | 1 | If present and equals to "1", then, if there exists a personal payment with the same template data, a new payment will be created; cannot be present at the same time as perspayee_overwrite |
| period1 | A | 1 | This detail specifies if and how often personal regular recurring payment should be executed automatically by batch task; possible values D (execute each day), W (execute each week), M (execute each month), Q (execute every 3 months), Y (execute every year) |
| first_exec_date | AN | 5 | This date specifies the date on which the payment will be executed for the first time in format MM.DD |
| times_to_exec | N | 10 | Specifies how many times recurring payment should be executed. If specified -1 payment will be executed infinite times |
| max_attempts | N | 10 | Specifies how many times recurring payment will be attempted to be executed, if it fails with "not enough funds" error |
| onfile | A | 1 | Card on file indicator with possible value Y or N |
| oboc | A | 1 | On behalf of a Cardholder indicator with possible value Y or N |
| recurring_reg2 | A | 1 | IPSP registration indicator with possible value Y or N |
| cof_original_tid3 | AN | MC-13 Visa-15 |
In case if card and payment data are stored at IPSP/merchant side, IPSP/merchant must provide the initial transaction identifier (cof_original_tid) with other payment data. Initial transaction ID is returned to IPSP/merchant where initial transaction response is in TLV format and the data field iss_ref_data, populated with tag 0003 |
| moto4 | A | 1 | Moto indicator with possible value Y or N |
| recurring_numb5 | AN | 2 | Number of Recurring Payments is required if not provided in detail times_to_exec. Valid value ranging from 01–99 |
| recurring_per5 | AN | 2 | Frequency of Recurring Payment is required if not provided in detail period. Valid values 01 (daily), 02 (twice per week), 03 (weekly), 04 (every ten days), 05 (fortnightly), 06 (monthly), 07 (every two months), 08 (trimester), 09 (quarterly), 10 (twice per year), 11 (annually), 12 (unscheduled) |
| recurring_ref5 | MC-AN Visa-N |
MC-10 Visa-35 |
Registration Reference Number in case if card and payment data are stored at IPSP/merchant side |
1 not applicable for airline addendum payments
2 mandatory for all recurring registration transactions when data is stored on IPSP side
3 mandatory for Merchant Initiated transactions when data is stored on IPSP side
4 mandatory for MOTO transaction when Merchant Initiated transactions and execution data is stored on IPSP side (Only for Mastercard)
5 mandatory for payment cards issued in India. In all other cases it is optional
Visa Instalment (VIS) specific details
Details governing VIS payment registration on DECTA side and its’ execution conditions.
| Name | Format | Length | Description |
|---|---|---|---|
| gate_payment_ref | N | 12 | Internal Transaction ID on the requestor side |
| instalment_request_id | N | 28 | Instalment request ID on DECTA side |
| instalment_plan | ANS | 50 | Visa generated identifier for an Instalment plan |
| instalment_tc_version | N | 10 | Version of Terms and Conditions |
| instalment_tc_language | A | 3 | Language of Terms and Conditions according to ISO 639-2 format |
Details governing VIS payment registration on PSP side and its’ execution conditions.
| Name | Format | Length | Description |
|---|---|---|---|
| inst_plan_id | AN | 10 | Plan Registration System Identifier as in Visa Instalment API response field vPlanIDRef |
| recurring | A | 1 | Detail governing environment type passed to ICO with static value ‘I’ |
Payout Transaction Specific Details
P2P Payment Specific Details
Details governing person-to-person transfers. There are two options for how P2P can be executed. It can be either only a credit transaction for the second card number (pan2). In this case the pan and expiry details are not provided> The second option is full P2P transfer with a debit and credit transaction.
client_* details from field specification refer to the sender's information. Even if only a credit transaction is performed according to Visa or Mastercard rules, the sender information must be provided in the credit record as well.
| Parameter | Format | Length | Description |
|---|---|---|---|
| amount | N | 12 | Amount |
| pan | N | 19 | Primary account number |
| expiry | N | 4 | Card expiry |
| expiry2 | N | 4 | Expiry date for the credited card |
| csc | N | 3 | CVC2/CVV2 |
| pan2 | N | 19 | Card number for the credited card |
| ccy_code | N | 3 | Currency code |
| client_address | AN | MC–35 Visa-30 |
Client's address |
| client_city | A | 30 | Client's city |
| client_name | ANS | MC–30 Visa-25 |
Client's full name |
| client_postal_code | AN | 10 | Client's postal code |
| recipient_name | ANS | 71 | Recipient's name and surname |
| merchant_ext | N | 15 | Card acceptor identification code for debit transactions |
| merchant_ext2 | N | 15 | Card acceptor identification code for credit transactions |
| c_ref | AN | 1024 | Concentrator reference identifier |
| client_country_code | N / AN | 3 | Client's country code; format depends on brand: Visa – N, Mastercard – AN |
| client_birth_date | N | 8 | Client's date of birth (MMDDYYYY) |
| client_state_code | ANS | 3 | Client's state code (for USA and Canada) |
| recipient_country_code | N | 3 | Recipient's country code (ISO Numeric Code) |
| recipient_birth_date | N | 8 | Recipient's date of birth (MMDDYYYY) |
| recipient_address | AN | MC-35 Visa-30 |
Recipient's address if the issuer is from Canada. In other cases, this is optional |
| recipient_state_code | ANS | 3 | Recipient's state code (mandatory for USA and Canada) |
| recipient_city | A | 25 | Recipient's city |
| client_account_number | ANS | MC-50 Visa-34 |
Client's bank or personal information |
| client_account_type | N | 2 | One of specific values must be used: 00 (other), 01 (RTN + bank account), 02 (IBAN), 03 (card account), 04 (email), 05 (phone number), 06 (bank account number (BAN) + bank identification code (BIC)), 07 (wallet ID), 08 (social network ID) |
| recipient_account_number | ANS | MC-50 Visa-34 |
Recipient's bank or personal number |
| recipient_account_type | N | 2 | One of specific values must be used: 00 (other), 01 (RTN + bank account), 02 (IBAN), 03 (card account), 04 (email), 05 (phone number), 06 (bank account number (BAN) + bank identification code (BIC)), 07 (wallet ID), 08 (social network ID) |
| payment_purpose | AN | 12 | Contains the purpose of the payment code that the originating acquirer will populate for the recipient issuer |
B2P Payment Specific Details
Details governing business-to-person transfers. These payments are used for the transfers from a legal entity to an individual.
| Parameter | Format | Length | Description |
|---|---|---|---|
| b2p_merchant | A | 1 | A detail for the B2P payment usage; must be equal to Y |
| amount | N | 12 | Amount |
| expiry2 | N | 4 | Expiry date for the credited card |
| pan2 | N | 19 | Card number for the credited card |
| ccy_code | N | 3 | Currency code |
| recipient_name | ANS | 71 | Recipient's name and surname |
| merchant_ext2 | N | 15 | Card acceptor identification code for a credit transaction |
| c_ref | AN | 256 | Concentrator reference identifier |
| recipient_country_code | N | 3 | Recipient's country code (ISO Numeric Code) |
| recipient_birth_date | N | 8 | Recipient's date of birth (MMDDYYYY) |
| recipient_city | A | 25 | Recipient's city |
| recipient_address | AN | MC-35; Visa-30 | Recipient's address if issuer is from Canada. In other cases this is optional |
| recipient_state_code | ANS | 3 | Recipient's state code (mandatory for USA and Canada) |
| payment_purpose | AN | 12 | Contains the purpose of the payment code that the originating acquirer will populate for the recipient issuer |
| crypto | A | 1 | A detail for the crypto transaction usage with the value Y |
OG Payment Specific Details
Details governing online gaming payouts. These payment are used for gaming payouts from a legal entity to an individual via MCC 7995 (Visa and Mastercard) and 9406 (Only Visa) merchants.
| Parameter | Format | Length | Description |
|---|---|---|---|
| payout_type | AN | 2 | Detail for executing the OG Payout switching. Must be equal to og |
| amount | N | 12 | Amount |
| expiry2 | N | 4 | Expiry date for the credited card |
| pan2 | N | 19 | Card number for the credited card |
| ccy_code | N | 3 | Currency code |
| recipient_name | ANS | 71 | Recipient's full name |
| merchant_id2 | N | 15 | Card acceptor identification code for credit transactions |
| recipient_city | A | 25 | Recipient's city |
| recipient_country_code | N | 3 | Recipient's country code (ISO Numeric Code) |
| recipient_address | AN | MC-35; Visa-30 | Recipient's address if the issuer is from Canada. In other cases this is optional |
| recipient_state_code | ANS | 3 | Recipient's state code (mandatory for USA and Canada) |
| payment_purpose | AN | 12 | The purpose of payment code that the originating acquirer will populate for the recipient issuer |
Account to Account Payout Specific Details
Details governing the Account to Account payouts. These payments are used for a cardholder transferring money between their own card accounts. For Visa transfers MCC 4829, 6012 are applicable and for Mastercard transfers MCC 6536, 6537 are applicable.
| Parameter | Format | Length | Description |
|---|---|---|---|
| payout_type | AN | 3 | Detail for executing the A2A Payout switching. Must be equal to a2a |
| amount | N | 12 | Amount |
| expiry2 | N | 4 | Expiry date for the credited card |
| pan2 | N | 19 | Card number for the credited card |
| ccy_code | N | 3 | Currency code |
| client_name | ANS | MC – 30; Visa - 20 | Client's full name |
| client_country_code | N | 3 | Client's country code (ISO Numeric Code) |
| client_birth_date | N | 8 | Client's date of birth (MMDDYYYY) |
| client_city | A | 25 | Client's city |
| client_state_code | ANS | 3 | Client's state code |
| client_address | AN | MC – 35; Visa - 30 | Client's address |
| client_postal_code | AN | 10 | Client's postal code |
| client_account_number | ANS | MC-50 Visa-34 |
Client's bank or personal number |
| client_account_type | N | 2 | One of specific values must be used: 00 (other), 01 (RTN + bank account), 02 (IBAN), 03 (card account), 04 (email), 05 (phone number), 06 (bank account number (BAN) + bank identification code (BIC)), 07 (wallet ID), 08 (social network ID) |
| merchant_id2 | N | 15 | Card acceptor identification code for a credit transaction |
| payment_purpose | AN | 12 | The purpose of payment code that the originating acquirer will populate for the recipient issuer |
Payroll & Pensions Disbursements Specific Details
Details governing Payroll & Pensions Disbursements payouts. These payments are used for an independent contractor work for temporary staffing agencies or directly with an employer or pension payouts. For Visa transfers MCC 8931 is applicable and for Mastercard transfers MCC 6536, 6537 are applicable.
| Parameter | Format | Length | Description |
|---|---|---|---|
| payout_type | AN | 2 | Detail for executing PD Payout switching. Must be equal with pd |
| amount | N | 12 | Amount |
| expiry2 | N | 4 | Expiry date for the credited card |
| pan2 | N | 19 | Card number for the credited card |
| ccy_code | N | 3 | Currency code |
| merchant_id2 | N | 15 | Card acceptor identification code for a credit transaction |
| recipient_name | ANS | 71 | Recipient's full name |
| recipient_country_code | N | 3 | Recipient's country code (ISO Numeric Code) |
| recipient_birth_date | N | 8 | Recipient's date of birth (MMDDYYYY) |
| recipient_city | A | 25 | Recipient's city |
| recipient_state_code | ANS | 3 | Recipient's state code (mandatory for USA and Canada) |
| recipient_address | AN | MC - 35; Visa - 30 | Recipient's address if the issuer is from Canada. In other cases this is optional |
| payment_purpose | AN | 12 | The purpose of payment code that the originating acquirer will populate for the recipient issuer |
AFT Payment Specific Details
Details governing Account Funding Transaction (AFT). These payments are used for Merchant FT debit transactions.
crypto is required for Visa transactions to correctly identify and populate transaction details when a cryptocurrency purchase is processed.
| Parameter | Format | Length | Description |
|---|---|---|---|
| amount | N | 12 | Amount |
| pan | N | 19 | Primary account number |
| expiry | N | 4 | Card expiry |
| csc | N | 3 | CVC2/CVV2 |
| ccy_code | N | 3 | Currency code |
| recipient_name | ANS | 71 | Recipient's name and surname |
| merchant_id | N | 15 | Card acceptor identification code for debit transactions |
| recipient_country_code | N | 3 | Recipient Country code (ISO Numeric Code) |
| recipient_birth_date | N | 8 | Recipient birth date (MMDDYYYY) |
| recipient_city | A | 25 | Recipient city |
| recipient_address | AN | 30 | Recipient address |
| recipient_account_number | ANS | MC-50 Visa-34 |
Recipient's bank or personal number |
| recipient_account_type | N | 2 | One of specific values must be used: 00 (other), 01 (RTN + bank account), 02 (IBAN), 03 (card account), 04 (email), 05 (phone number), 06 (bank account number (BAN) + bank identification code (BIC)), 07 (wallet ID), 08 (social network ID) |
| client_name | ANS | 20 | Client's full name |
| client_address | AN | 30 | Client's address |
| client_city | A | 25 | Client's city |
| client_state_code | AN | 3 | Client's State Code |
| client_country_code | N | 3 | Client's Country code (ISO Numeric Code) |
| client_birth_date | N | 8 | Client birth date – MMDDYYYY |
| crypto | A | 1 | A detail for crypto transaction usage with a value Y |
AFT AA Payment Specific Details
Details governing Account Funding Transaction account-to-account (AFT AA). These payments are used if the client is sending money to themselves (i.e. the sender and the receiver are the same person). For AFT AA funding transactions, the type of funding entity must be specified (the paramater funding_type) to indicate the correct type of Mastercard funding. AFT AA payment scenario is not available for Visa cards.
| Parameter | Format | Length | Description |
|---|---|---|---|
| funding_type | N | 1 | Funding type. One of specific values must be used: 1 - Payment account (F52); 2 - SDWO account (F61); 3 - Prepaid or gift card (F64) |
| amount | N | 12 | Amount |
| pan | N | 19 | Primary account number |
| expiry | N | 4 | Card expiry |
| csc | N | 3 | CVC2/CVV2 |
| ccy_code | N | 3 | Currency code |
| recipient_name | ANS | 71 | Recipient's name and surname |
| merchant_id | N | 15 | Card acceptor identification code for debit transactions |
| recipient_country_code | N | 3 | Recipient's country code (ISO Numeric Code) |
| recipient_birth_date | N | 8 | Recipient's date of birth (MMDDYYYY) |
| recipient_city | A | 25 | Recipient's city |
| recipient_address | AN | 30 | Recipient's address |
| recipient_account_number | ANS | MC-50 Visa-34 |
Recipient's bank or personal number |
| recipient_account_type | N | 2 | One of specific values must be used: 00 (other), 01 (RTN + bank account), 02 (IBAN), 03 (card account), 04 (email), 05 (phone number), 06 (bank account number (BAN) + bank identification code (BIC)), 07 (wallet ID), 08 (social network ID) |
| crypto | A | 1 | A detail for crypto transaction usage with a value Y |
| hr_asset | N | 1 | 1 - crypto-currency; 2 - high-risk forex; 3-6 - RFU |
| payment_purpose | AN | 12 | The purpose of payment code that the originating acquirer will populate for the recipient issuer |
Valid Values for AFT_AA Scenario Specific Details
| Business type | MCC | Mastercard cards | Visa cards | ||
|---|---|---|---|---|---|
| hr_asset | funding_type | hr_asset1 | crypto2 | ||
| Payment institution account funding | 4829 | - | 1, 3 | - | - |
| Payment institution account funding | 6540 | - | 1, 2, 3 | - | - |
| Payment institution account funding | 6012 | Invalid for Mastercard | - | - | |
| Crypto-currency | 6051 | 1 | 1, 2 | 1 | - |
| Crypto-currency | 6051 | 1 | 1, 2 | - | Y |
| Funding of High-risk securities | 6211 | 2 | 1, 2 | 2 | - |
| Low risk securities | 6211 | - | 1, 2 | 2 | - |
| Gaming, gambling | 7995 | - | 1, 2 | Invalid for Visa | |
1 detail hr_asset with any of allowed values must be used to process Visa AFT with BAI LA
2 detail crypto must be used to process Visa AFT with BAI FT
Funds Transfer Specific Details
Details governing Funds Transfer payouts. These payments are used for cashing out a Stored Value Digital Wallet (SVDW) account. For Visa transfers MCC 4829, 6012, 6051, 6540 are applicable, and for Mastercard transfers MCC 6536, 6537 are applicable.
| Parameter | Format | Length | Description |
|---|---|---|---|
| payout_type | A | 2 | A detail for executing FT Payout switching. Must be equal to ft |
| amount | N | 12 | Amount |
| expiry2 | N | 4 | Expiry date for the credited card |
| pan2 | N | 19 | Card number for the credited card |
| ccy_code | N | 3 | Currency code |
| client_name | ANS | MC – 30; Visa - 20 | Client's full name |
| client_country_code | N | 3 | Client's country code (ISO Numeric Code) |
| client_birth_date | N | 8 | Client's date of birth (MMDDYYYY) |
| client_city | A | 25 | Client's city |
| client_state_code | ANS | 3 | Client's state code |
| client_address | AN | MC – 35; Visa - 30 | Client's address |
| client_postal_code | AN | 10 | Client's postal code |
| client_account_number | ANS | MC-50 Visa-34 |
Client's bank or personal information |
| client_account_type | N | 2 | One of specific values must be used: 00 (other), 01 (RTN + bank account), 02 (IBAN), 03 (card account), 04 (email), 05 (phone number), 06 (bank account number (BAN) + bank identification code (BIC)), 07 (wallet ID), 08 (social network ID) |
| merchant_id2 | N | 15 | Card acceptor identification code for credit transactions |
| crypto | A | 1 | A detail for the crypto transaction usage with the value Y |
| payment_purpose | AN | 12 | The purpose of payment code that the originating acquirer will populate for the recipient issuer |
SDWO Payment Specific Details
| Parameter | Format | Length | Description |
|---|---|---|---|
| sdwo_merchant_id | N | 15 | SDWO acceptor identification code |
| wallet_id | AN | MC - 3; Visa - 10 | MC - Mastercard Wallet Identifier; Visa - Visa Merchant Verification Value (MVV) |
SDWO Payout Specific Details
| Parameter | Format | Length | Description |
|---|---|---|---|
| b2p_merchant | A | 1 | A detail for the B2P payment usage; must be equal to Y |
| recipient_name | ANS | 71 | Recipient's full name |
| c_ref | AN | 256 | Concentrator reference identifier |
| recipient_country_code | N | 3 | Recipient's country code (ISO Numeric Code) |
| recipient_birth_date | N | 8 | Recipient's date of birth (MMDDYYYY) |
| recipient_city | A | 25 | Recipient's city |
| recipient_address | AN | MC-35; Visa-30 | Recipient's address if the issuer is from Canada. In other cases, this is optional |
| recipient_state_code | ANS | 3 | Recipient's state code (mandatory for USA and Canada) |
| sender_name | AN | 30 | Sender's full name |
| wallet_id | AN | MC - 3; Visa - 10 | MC - Mastercard Wallet Identifier; Visa - Visa Merchant Verification Value (MVV) |
| sdwo_merchant_id | N | 15 | SDWO acceptor identification code |
| merchant_ext2 | N | 15 | Card acceptor identification code for payout transactions |
| crypto | A | 1 | A detail for the crypto transaction usage with the value Y |
| payment_purpose | AN | 12 | The purpose of payment code that the originating acquirer will populate for the recipient issuer |
Airline Addendum Specific Details
Common details for all trip legs.
| Parameter | Format | Length | Description |
|---|---|---|---|
| n_legs | N | 1 | Number of trip legs. Main detail governing the airline addendum related request generation. Possible values: 1, 2, 3, 4. |
| ticket_number | AN | 15 | Airline ticket number |
| carrier_name | AN | 19 | Airline carrier name |
| travel_agency_code | AN | 8 | Airline agency code |
| travel_agency_name | AN | 25 | Airline agency name |
| plan_nr | AN | 2 | Airline plan number |
| invoice_number | AN | 6 | Airline invoice number |
| airline_orig_ccy | N | 3 | Airline original currency code |
| passenger_name | ANS | 29 | Airline passenger name |
| customer_ref | ANS | 20 | Airline customer reference |
| original_amnt | N | 12 | Airline original invoice amount |
| ticket_issue_addr | ANS | 16 | Airline ticket issue address |
| ticket_issue_date | N | 8 | Airline ticket issue date - YYYYMMDD |
| total_fare | N | 12 | Airline total fare amount |
| total_fees | N | 12 | Airline total fees amount |
| total_tax | N | 12 | Airline total taxes amount |
| restricted_ticket_indicator | N | 1 | Restricted ticket indicator. Possible values: 0 - no restriction; 1 - restricted ticket (non-refundable) |
Details for airline addendum n_legs specifies the trip leg number and must be between 1..n_legs.
| Parameter | Format | Length | Description |
|---|---|---|---|
| departure_airportN | AN | 5 | Trip leg departure airport |
| carrier_codeN | AN | 2 | Trip leg carrier code |
| fare_bassisN | AN | 15 | Trip leg fare basis code |
| service_classN | AN | 2 | Trip leg class of travel |
| stop_over_codeN | AN | 1 | Trip leg stop over code. Possible values: O - stopover allowed; X - stopover not allowed |
| destination_airportN | AN | 5 | Trip leg destination airport |
| departure_dateN | N | 8 | Trip leg date of travel (DDMMYYYY) |
| departure_taxN | N | 12 | Trip leg departure tax amount |
| conjunct_ticketN | AN | 15 | Trip leg conjunction ticket number |
| exchange_ticketN | AN | 15 | Trip leg exchange ticket number |
| coupon_numberN | ANS | 1 | Trip leg coupon number |
| trip_numberN | ANS | 5 | Trip leg flight number |
| departure_timeN | N | 4 | Trip leg departure time |
| arrival_timeN | N | 4 | Trip leg arrival time |
| fare_amntN | N | 12 | Trip leg fare amount |
| fees_amntN | N | 12 | Trip leg fees amount |
| tax_amntN | N | 12 | Trip leg taxes amount |
| endorsements_restrN | ANS | 20 | Trip leg endorsements/restrictions |
Apple Pay Purchase Specific Details
| Parameter | Format | Length | Description |
|---|---|---|---|
| merchant_url | ANS | 150 | Merchant business website URL or reverse domain name; base64 encoded. Only for Mastercard |
| tavv | ANS | 28 | base64-encoded; For Mastercard: DSRP Cryptogram; for Visa: Token Authentication Verification Value (TAVV) - Apple Pay: PKPaymentToken.paymentData.data.paymentData.onlinePaymentCryptogram |
Response Message Detail Description
| Parameter | Format | Length | Payout specific | Description |
|---|---|---|---|---|
| acq_inst | N | 11 | Internal reference | |
| acq_inst2 | N | 11 | Y | Internal reference |
| auth_action_code | AN | 3 | Authorisation action code: 000 for approved authorisations |
|
| auth_action_code2 | AN | 3 | Y | Authorisation action code: 000 for approved authorisations |
| auth_appr_code | AN | 6 | Authorisation approval code as provided by the issuer | |
| auth_appr_code1a | AN | 6 | Authorisation approval code as provided by the issuer, used only for the DMS payments | |
| auth_appr_code2 | AN | 6 | Y | Authorisation approval code as provided by the issuer |
| auth_ref_number | AN | 12 | Reference number assigned to the transaction | |
| auth_ref_number2 | AN | 12 | Y | Reference number assigned to the transaction |
| auth_row_numb1 | N | 11 | Internal reference number assigned to the authorisation message | |
| auth_row_numb1a | N | 11 | Internal reference number assigned to the authorisation message, used only for the DMS payments | |
| auth_row_numb3 | N | 11 | Y | Internal reference number assigned to the authorisation message |
| auth_stan | N | 6 | Internal system trace audit number | |
| auth_stan2 | N | 6 | Y | Internal system trace audit number |
| auth_time | N | 14 | Time of authorisation (YYYYMMDDhhmmss) | |
| auth_time2 | N | 14 | Y | Time of authorisation (YYYYMMDDhhmmss) |
| merchant_name | ANS | 99 | Merchant name as registered in the DECTA’s system or sent by a merchant if the dynamic descriptor is used | |
| netsw_svcbrand | AN | 3 | Card brand | |
| avs_result | A | 1 | AVS verification result | |
| perspayee_id | N | 8 | Internal reference, registered recurring payment identifier | |
| reconcile_info | N | 17 | Internal information | |
| reconcile_info2 | N | 17 | Y | Internal information |
| ret_ref_numb1a | N | 12 | Retrieval reference number | |
| debits_number | N | 20 | Count of debit transactions | |
| debits_amount | N | 20 | Total amount of debit transactions | |
| credits_number | N | 20 | Count of credit transactions | |
| credits_amount | N | 20 | Total amount of credit transactions | |
| debits_reversal_number | N | 20 | Count of debit reversals | |
| debits_reversal_amount | N | 20 | Total amount of debit reversals | |
| credits_reversal_number | N | 20 | Count of credit reversals | |
| credits_reversal_amount | N | 20 | Total amount of credit reversals |
billerRef and payinstrRef Examples
The example outlines the mapping of biller and instrument reference values to a specific payment scenario.
| Operation | billerRef | payinstrRef | switchingID |
|---|---|---|---|
| Simple recurring payment generation | XX_AUTH | XX_AUTH | Not used |
| Account Name Inquiry requests | XX_AUTH_NAME | XX_AUTH_NAME | Not used |
| SMS payment | XX_SMS | XX_SMS | Not used |
| QCash payment | QCASH_XX | QCASH_XX | Not used |
| DMS payment | XX_DMS | XX_DMS | Not used |
| QCash payment in DMS mode | QCASH_DMS_XX | QCASH_DMS_XX | Not used |
| Reconciliation | XX_RECO | XX_RECO | Not used |
| Refund execution | XX_REFND | XX_REFND | Not used |
| Refund Online execution | XX_REFND_ON | XX_REFND_ON | Not used |
| AFT payment | XX_AFT | XX_AFT | Not used |
| AFT AA payment | XX_AFT_AA | XX_AFT_AA | Not used |
| OG payouts | Not used | Not used | Request from Client Manager |
| FT payouts | Not used | Not used | Request from Client Manager |
| A2A payouts | Not used | Not used | Request from Client Manager |
| P2P payments | Not used | Not used | Request from Client Manager |
| B2P payments | Not used | Not used | Request from Client Manager |
| SDWO funding | DWO_FUNDING_XX | DWO_FUNDING_XX | Not used |
| SDWO purchase | DWO_PURCHASE_XX | DWO_PURCHASE_XX | Not used |
| SDWO payout | Not used | Not used | Request from Client Manager |
| Recurring simple payment execution | XX_SMS | XX_SMS | Not used |
| Payment return | Not used | Not used | Not used |
| Payment cancel | Not used | Not used | Not used |
| Apple Pay purchase in DMS mode | XX_APPLEPAY_DMS | XX_APPLEPAY_DMS | Not used |
| Apple Pay purchase in SMS mode | XX_APPLEPAY_SMS | XX_APPLEPAY_SMS | Not used |
Precise billerRef and payinstrRef must be requested from the Client Manager.
Jump to
- Overview
- CVC2 / CVV2 Usage Table for MOTO Transactions
- Actions
- Payment Statuses
- Authorisation Response Codes
- Merchant Advice Code
- Request Element Description
- Common Requests Elements
- Common Request Details
- Recurring Payment Specific Details
- Visa Instalment (VIS) specific details
- Payout Transaction Specific Details
- AFT Payment Specific Details
- Funds Transfer Specific Details
- SDWO Payment Specific Details
- SDWO Payout Specific Details
- Airline Addendum Specific Details
- Apple Pay Purchase Specific Details
- Response Message Detail Description
- billerRef and payinstrRef Examples