Appearance
Introduction
A Card Transaction is an operation associated to an issued Card. All Card Transactions are mapped to CardTransaction objects.
Card payments almost always go through many steps. There is one CardTransaction per step but not all CardTransactions affect the Balances of the associated Wallet.
Key attributes
Attribute | Type | Description |
---|---|---|
cardtransactionId | string | The unique identifier of the card transaction. |
cardId | string | The unique identifier of the card used for the transaction. |
walletId | string | The unique identifier of the Wallet the card is attached to. |
walletCurrency | string | The currency of the Wallet. |
merchantId | string | The MID |
merchantName | string | The name of the merchant. |
merchantAddress | string | The address of the merchant. |
merchantCity | string | The city of the merchant. |
merchantCountry | string | The country of the merchant. ISO 3166 3-letter code (except of the US which is a two-letter code) |
publicToken | string | The token of the card (a way to identify a card without knowing or communicating its PAN) |
paymentAmount | string | The amount of the transaction, always expressed in Euros. |
paymentCurrency | string | The local currency in which the transaction was made, ISO 4217 3-letter code. |
paymentLocalAmount | string | The amount of the transaction in the local currency. |
paymentLocalDate | string | The local date on which the transaction occurred. |
paymentLocalTime | string | The local time at which the transaction occurred. |
fees | string | ATM usage or foreign payments fees as defined by Treezor, always set to 0 |
paymentCountry | string | Country in which the transaction occurred, ISO 3166 3-letter code. |
paymentStatus | string | The general status of the transaction. See table below |
posCardholderPresence | string | Describes more precisely how the card was used. See list below |
posPostcode | string | Postcode of the transaction location. |
posCountry | string | Country of the point of sale, ISO 3166 3-letter code. |
posTerminalId | string | The id of the terminal used for the transaction. |
posCardPresence | string | Indicates whether the card was physically present during the transaction:
|
panEntryMethod | string | How the PAN was captured by the merchant. See list below |
authorizationNote | string | Contains detailed information regarding a declined transaction. See table below |
authorizationResponseCode | string | The precise status of the transaction. See table below |
authorizationIssuerId | string | The transaction identifier as generated by the payment processor. |
authorizationIssuerTime | string | The time of the transaction, in the timezone of the payment processor. |
authorizedBalance | string | The Authorized Balance of the wallet after the transaction |
mcc | string | The Merchant Category Code (MCC). A MCC valued to 6011 indicates a withdrawal. Some MCC are prohibited for anonymous electronic money, such as: money transfer, money order, foreign currency, liquid and cryptocurrency assets, lotteries, on-line gambling, betting, etc. |
acquirerId | string | The acquirer's ID (the merchant's bank in the form of 5 to 6 digits) |
is3DS | string | Indicates whether 3DSecure was used for authentication:
|
totalLimitPaymentYear | string | The related Card yearly spent amount. This is used with Cards Limits |
totalLimitPaymentMonth | string | The related Card monthly spent amount. This is used with Cards Limits |
totalLimitPaymentWeek | string | The related Card weekly spent amount. This is used with Cards Limits |
totalLimitPaymentDay | string | The related Card daily spent amount. This is used with Cards Limits |
totalLimitPaymentAll | string | The related Card lifetime spent amount. This is used with Cards Limits |
totalLimitAtmWeek | string | The related Card weekly ATM withdrawal amount. This is used with Cards Limits |
totalLimitAtmDay | string | The related Card daily ATM withdrawal amount. This is used with Cards Limits |
totalLimitAtmAll | string | The related Card lifetime ATM withdrawal amount. This is used with Cards Limits |
cardDigitalizationExternalId | string | The digital payment token identifier (only present if payment was made with a digital token such as ApplePay or GooglePay for example) |
localMerchantId | string | Indicates the merchant's SIREN or SIRET if available. |
Tip – Transaction object id for Card Transactions
When a CardTransaction produces a Transaction object, the CardTransaction.id
is reflected in the Transaction.foreignId
attribute.
Caution – Data formats may differ
The date, time, and country formats are different from Treezor usual API format because Treezor displays the information as provided by the Card processor.
Statuses (paymentStatus
)
This attribute allows you to identify the type of transaction, as Card payments almost always go through many steps.
Status | Description | Impacts Current Balance | Impacts Authorized Balance | Note |
---|---|---|---|---|
A | Authorization accepted | Authorization request accepted by Treezor | ||
R | Refund | Refunded authorization | ||
S | Settled | Generally no | Can be:
| |
M | MoneySend | MoneySend authorization | ||
C | Cleared | Settlement is received without a previous matching authorization reques. | ||
I | Declined | Authorization refused | ||
V | Reversed | Authorization reversed |
C
(Cleared) may happen when a payment was approved offline by the payment terminal. Such transactions are processed asynchronously. It may take up to several days.
V
(Reversed) may happen when an automated gas station authorized an amount greater than the actual amount of fuel pumped.
💡 Negative amounts and Non-Euro Settlement (S
) can affect the Authorized Balance. See Non-Euro example and Negative amount settlement example.
PAN Entry Method (panEntryMethod
)
This attribute informs you of how the PAN was provided to or accessed by a merchant for a transaction.
Description | |
---|---|
0 | Unknown or no terminal |
1 | Manual Key Entry |
2 | Partial Magnetic Stripe Read |
3 | Barcode |
4 | OCR |
5 | Chip (contact interface) |
7 | Chip (contactless interface) |
10 | Credential-on-file (e.g., one-click purchase) |
79 | PAN & Expiration date entered by acquirer |
80 | Magnetic Stripe fallback (The terminal was not able to read the chip) |
81 | e-commerce |
91 | Contactless magstripe mod |
Cardholder Presence (posCardholderPresence
)
This attribute indicates whether the cardholder was present at the point of sale and provides details if they were not present.
Cardholder Presence | Description | ||
---|---|---|---|
0 | Present | Cardholder present | |
1 | Not-present | Unspecified | |
2 | Not-present | Mail/facsimile order | |
3 | Not-present | Phone/ARU order | |
4 | Not-present | Standing order/recurring transactions | |
5 | Not-present | Electronic order (home computer, internet, mobile phone, PDA) | |
6 | Not-present | Installment transaction (similar to recurring but fixed number of installments) | |
9 | Unknown | Unknown |
Authorization Note (authorizationNote
)
This attribute allows your Support Users to inform the cardholder of the cause of a payment incident and/or status.
You should always use the authorizationNote
together with the authorizationResponseCode
to provide accurate information to the cardholder.
The authorizationResponseCode
indicates if the transaction was Declined or Approved, while the authorizationNote
provides more details as to why.
Tip – Multiple messages may be contained in the authorizationNote
In which case they are concatenated with the \n
character to separate them.
Find below the list of common authorization notes.
Authorization Note | Description | Source |
---|---|---|
; DE095={amount}; DE095={amount} | Informative message, {amount} is the remaining authorized amount after a partial reversal | Card Processor |
ASI.... AVS check | Informative message, the address of the cardholder has been checked | Card Processor |
ASI.... CVC check | Informative message, the CVC has been checked | Card Processor |
ATM MONTHLY LEGAL LIMIT OF WALLET EXCEEDED | The legal ATM withdrawal limit has been reached | Treezor |
AUTOMATIC AUTHORISATION REMOVAL BillAmt - {amount} Location - {business} {country} | An authorization from 7 days ago has been cancelled and reversed, as no settlement occurred (these are generally used to ensure a Card is valid by authorizing a small amount that is never actually debited) | Card Processor |
Banknet advice: APS error; unable to deliver response | Temporary internal error, the Cardholder should retry their payment | Card Processor |
BlockedCard | The Card is blocked. | Card Processor |
Card CVV2 not matching with cvv2 in auth request | The cardholder entered an erroneous CVV2 (or CVC) | Card Processor |
ChargeBack - Credit to Card | Informative message, the cardholder has just been refunded following a chargeback | Card Processor |
Connection Timeout | Temporary internal error, the Cardholder should retry their payment | Card Processor |
COUNTRY CODE NOT ALLOWED | The merchant's country is not allowed by the Card or Card Program | Card Processor |
CountryNotPermittedToCardHolder | The payment country is not allowed by the Card or Card Program | Card Processor |
Credit Other - pre-arbitration | Arbitration case: the cardholder has definitively won the chargeback following a dispute with the merchant. | Treezor |
DECLINED BY GPS | The card processor declined the transaction (this is always accompanied by a more detailed message) | Treezor |
DECLINED BY NETWORK | The card processor declined the transaction | Scheme |
DR: AF:Mag ATM attempt | An ATM withdrawal was attempted using the magstripe, which is forbidden for security reason. The cardholder should retry using the Card Chip&PIN method. | Card Processor |
DR: ARQC not matching | There was a malfunction with the Card and/or the payment terminal, the cardholder may retry their payment once | Card Processor |
DR: Card expiry check failed with Emboss Expiry date (DE014) | The cardholder entered a wrong expiration date | Card Processor |
DR: Card not found UnKnownCard | The Card PAN is unknown or invalid but does match Treezor's range of Card numbers | Card Processor |
DR: CVC2 tries exceeded | The cardholder entered erroneous CVC too many times. A ticket must be open with Treezor to unlock it. | Card Processor |
DR: Declined due to Card Status: Card Destroyed (Original status 83, changed to 05) | The Card has been destroyed | Card Processor |
DR: Declined due to Card Status: Expired card | The Card has expired (expiration date is in the past) | Card Processor |
DR: Declined due to Card Status: Lost card (Capture)(Issuer will be charged if card is picked up) | The Card has been lost and the merchant is allowed to keep the Card and send it to their bank for restitution to Treezor | Card Processor |
DR: Declined due to Card Status: Restricted card (Card is not active) | The Card is inactive | Card Processor |
DR: Declined due to Card Status: Short-term Debit | The Card is locked | Card Processor |
DR: Declined due to Card Status: Stolen card (Capture)(Issuer will be charged if card is picked up) | The Card has been stolen and the merchant is allowed to keep the Card and send it to their bank for restitution to Treezor | Card Processor |
DR: Declined due to CardUsageGroupCheck GroupUsageID-{groupId} [additional information] | The authorization was blocked due to restrictions on the use of the Card. More information are available in the details: [additional information] . | Card Processor |
DR: Declined due to Lost Card (Capture)(Original auth resp status 41, changed to 05) | The Card has been declared as lost | Card Processor |
DR: Declined due to Restricted card (Card is not active) | The Card is not activated or is disabled | Card Processor |
DR: Declined due to Stolen Card (Capture)(Original auth resp status 43, changed to 05) | The Card has been declared as stolen | Card Processor |
DR: Decline existing tokens(10) > Min_Tokens_To_Decline(10) DR: MDES/VDEP validation failed MDES check failed from Tokenisation Processing | There are already 10 Cards tokenized with an X-Pay provider (Google Pay, Apple Pay, Samsung Pay...), no more tokenization are allowed | |
DR: Decline as wallet_device_score (1) <= wallet_device_max_score_decline (1) | Card tokenization has been denied by the X-Pay provider (Apple Pay, Google Pay, Samsung Pay...) due to poor End User's device scoring | |
DR: Expiry Date missing. | The expiration date of the Card has not been provided | Card Processor |
DR: IAV:V (checked by MC-PREVAL) | Monetary Currency mismatch between authorization and authentication | Card Processor |
DR: iCVV does not match on EMV Track 2 | Either an issue with the merchant's terminal, or the chip of the card. Contact Support if the issue occurs with multiple merchants. | Card Processor |
DR: Incorrect PIN | The PIN code entered was incorrect | Card Processor |
DR: MDES Invalid Card Number - payment_token not found | The Card was properly digitized for X-Pay but an incident occurred when payin with X-Pay. The cardholder should digitize their card again. | Card Processor |
DR: Offline PIN incorrect | The cardholder entered an erroneous PIN | Card Processor |
DR: Offline PIN try limit exceeded | The maximum number of erroneous PIN has been reached, the PIN must be unlocked | Card Processor |
DR: Requires SCA | The transaction requires a Strong Customer Authentication such as 3D Secure or Chip & Pin. | Card Processor |
EH Timeout - An error occurred while sending the request. | Temporary internal error, the Cardholder should retry their payment | Card Processor |
EH Timeout - Response status code does not indicate success: 429 (Too Many Requests). | Temporary internal error, the Cardholder should retry their payment | Card Processor |
EH Timeout - Response status code does not indicate success: 502 (Bad Gateway). | Temporary internal error, the Cardholder should retry their payment | Card Processor |
EH Timeout - The operation was canceled. | Temporary internal error, the Cardholder should retry their payment | Card Processor |
EH Timeout - Unable to connect to the remote server | Temporary internal error, the Cardholder should retry their payment | Card Processor |
EH Timeout | Temporary internal error, the Cardholder should retry their payment | Card Processor |
Electronic Money: MCC not permitted | The law prohibits this MCC (type of business). This only occurs with EM projects | Treezor |
Electronic Money: transaction not permitted to cardholder | The cardholder doesn't exist or is frozen. This only occurs with EM projects | Treezor |
Electronic Money: cumulative amount authorized exceeded | The electronic money limit on sliding period has been reached. This only occurs with EM projects | Treezor |
Electronic Money: amount exceeds the authorized amount | The transaction amount exceeds the authorized amount. This only occurs with EM projects | Treezor |
Electronic Money: payment is not permitted in this country | The country of the wallet and the country in which the payment is done don't match. This only occurs with EM projects | Treezor |
ErrorInternal | Temporary internal error, the Cardholder should retry their payment | Treezor |
EXTERNAL AUTHORIZATION - APPROVED | The Transaction was approved by you, using the External Authorization feature | Treezor / Agent |
EXTERNAL AUTHORIZATION - DO NOT HONOR | The transaction has been refused by you and the refusal code is unspecified, using the External Authorization feature | Agent |
EXTERNAL AUTHORIZATION - INSUFFICIENT_FUNDS | The transaction has been refused by you because there are insufficient funds, using the External Authorization feature | Agent |
EXTERNAL AUTHORIZATION - TRANSACTION_NOT_PERMITTED_TO_CARDHOLDER | The transaction has been refused by you because the conditions of use of the card are not respected by the cardholder, using the External Authorization feature | Agent |
EXTERNAL AUTHORIZATION - INVALID_CARD_NUMBER | The transaction has been refused by you because the card is unknown, using the External Authorization feature | Agent |
EXTERNAL AUTHORIZATION - INVALID_MERCHANT | The transaction has been refused by you because the merchant or type of merchant is not allowed, using the External Authorization feature | Agent |
EXTERNAL AUTHORIZATION - EXCEEDS_WITHDRAWAL_AMOUNT_LIMIT | The transaction has been refused by you because the withdrawal limits or ceilings are insufficient, using the External Authorization feature | Agent |
Fixed amount adjustment | The difference between the pre-authorized amount for the AFD transaction and the actually charged amount has been reversed. Learn more about this specific case in the corresponding example. | Treezor |
Gen: Pre-Authorization Request | Informative message, indicates a pre-authorization request (such as a deposit) which can be canceled later | Card Processor |
Incoming transaction concern an unactive wallet | The transaction is associated to an inactive Wallet | Treezor |
Incoming transaction concern an unactive user | The transaction is associated to an inactive User | Treezor |
Incoming transaction concern an unactive card | The transaction is associated to an inactive Card | Treezor |
Incoming transaction concern an unknown PAN | The transaction is associated to an unknown PAN (absent from our system) | Treezor |
Insufficient funds | The Wallet has insufficient funds | Treezor |
Invalid card number (no such token) | The Card PAN is invalid or unknown | Treezor |
Issuer Time-out | Temporary internal error, the Cardholder should retry their payment | Card Processor |
LIMIT ATM EXCEEDED ALL | The lifetime ATM withdrawal limit has been reached | Treezor |
LIMIT ATM EXCEEDED DAY | The daily ATM withdrawal limit has been reached | Treezor |
LIMIT ATM EXCEEDED MONTH | The monthly ATM withdrawal limit has been reached | Treezor |
LIMIT ATM EXCEEDED WEEK | The weekly ATM withdrawal limit has been reached | Treezor |
LIMIT ATM EXCEEDED YEAR | The yearly ATM withdrawal limit has been reached | Treezor |
LIMIT CONTACTLESS APPLE PAY EXCEEDED | The Apple Pay contactless limit has been reached | Treezor |
LIMIT CONTACTLESS EXCEEDED | The contactless limit has been reached | Treezor |
LIMIT PAYMENT EXCEEDED ALL | The lifetime payment limit has been reached | Treezor |
LIMIT PAYMENT EXCEEDED DAY | The daily payment limit has been reached | Treezor |
LIMIT PAYMENT EXCEEDED MONTH | The monthly payment limit has been reached | Treezor |
LIMIT PAYMENT EXCEEDED WEEK | The weekly payment limit has been reached | Treezor |
LIMIT PAYMENT EXCEEDED YEAR | The yearly payment limit has been reached | Treezor |
MCC NOT ALLOWED | The Merchant Category Code (category of business) is not allowed by the Card or Card Program | Treezor |
MccNotPermittedToCardHolder | The Merchant Category Code (category of business) is not allowed by the Card or Card Program | Treezor |
MDC DECLINED - did not match: {rulesetIds} | The transaction was refused by the Treezor transaction rules engine. | Treezor |
MDES FPAN Status:41 | Informative message, a payment was made with Apple Pay/Google Pay/Samsung Pay and the actual Card is lost | Card Processor |
MDES FPAN Status:62 | Informative message, a payment was made with Apple Pay/Google Pay/Samsung Pay and the actual Card is stolen or disabled | Card Processor |
MERCHANT ID NOT ALLOWED | The merchant's ID (one specific business) is not allowed | Treezor |
MerchantIdNotPermittedToCardHolder | The merchant's ID (one specific business) is not allowed | Treezor |
Null or Empty Response received from client | Temporary internal error, the Cardholder should retry their payment | Card Processor |
POSDailyLimitExceeded | The daily payment limit has been reached | Treezor |
Presentment for Partial Reversal | Informative message, following a Gas station transaction | Card Processor |
PSD2 Counter Reset | Informative message, the contactless counter or e-commerce counter has been reset to zero | Card Processor |
Refund | Informative message, refund authorization | Treezor |
REVERSAL | Informative message, the reversal cancels a previous authorization at the merchant's request. It frees up the Authorized Balance of the Wallet. | Treezor |
Reversal due to AFD Advice with different amount. (AFD Amount=30.0000) | Informative message, the reversal cancels a previous authorization at the merchant's request. It frees up the Authorized Balance of the Wallet. | Card processor |
Signature Verification - Failed | Occurs in countries where the authentication method consists in signing the receipt. Such authentications are refused as they can't be checked online. | Card processor |
SIMULTANEOUS OPERATIONS ON THE SAME WALLET | Multiple operations occurred at the very same time on the Wallet, the cardholder should retry their payment | Treezor |
Specific to AFD: fixed amount authorization | The fixed amount of €160 has been applied for a automated fuel dispenser (AFD) transaction. Learn more about this specific case in the corresponding example. | Treezor |
System Error. | Temporary internal error, the Cardholder should retry their payment. | Treezor |
User's assets are freezed | The Wallet or payment account of the User is frozen by an AML-CFT sanction. | Treezor |
{rulesetIds} | The transaction was accepted by the Treezor transaction rules engine. | Treezor |
The DR:
prefix means Decline Reason.
Caution – The authorization notes list isn't exhaustive
Due to the vast number of possibilities regarding authorization notes and their variations, we document only the most common ones.
Codes (authorizationResponseCode
)
This information is provided in the authorizationResponseCode
attribute.
It provides clues as to why the transaction was accepted or refused, and pointers regarding what to do next. This information comes in addition to the status of a transaction.
Code | Action | Description | |
---|---|---|---|
00 | Approve | APPROVED | |
08 | Approve | HONOR_WITH_ID | |
10 | Approve | PARTIAL_APPROVAL | |
87 | Approve | PURCHASE_AMOUNT_ONLY_NO_CASH_BACK_ALLOWED | |
98 | Approve | REFUND_GIVEN_TO_CUSTOMER | |
85 | Approve | NOT_DECLINED_VALID_FOR_ALL_ZERO_AMOUNT_TRANSACTIONS | |
01 | Call-Issuer | REFER_TO_CARD_ISSUER | |
70 | Call-issuer | CONTACT_CARD_ISSUER | |
41 | Capture | LOST_CARD | |
43 | Capture | STOLEN_CARD | |
02 | Decline | CARD_NOT_YET_ACTIVATED | |
03 | Decline | INVALID_MERCHANT | |
04 | Decline | CAPTURE_CARD_CAPTURE | |
05 | Decline | DO_NOT_HONOR | |
06 | Decline | ERROR (REVERSAL ONLY) | |
12 | Decline | INVALID_TRANSACTION | |
13 | Decline | INVALID_AMOUNT | |
14 | Decline | INVALID_CARD_NUMBER | |
15 | Decline | INVALID_ISSUER | |
30 | Decline | FORMAT_ERROR | |
51 | Decline | INSUFFICIENT_FUNDS | |
54 | Decline | EXPIRED_CARD | |
55 | Decline | INVALID_PIN | |
57 | Decline | TRANSACTION_NOT_PERMITTED_TO_CARDHOLDER | |
58 | Decline | TRANSACTION_NOT_PERMITTED_TO_ACQUIRER_TERMINAL | |
61 | Decline | EXCEEDS_WITHDRAWAL_AMOUNT_LIMIT | |
62 | Decline | RESTRICTED_CARD | |
63 | Decline | SECURITY_VIOLATION | |
65 | Decline | EXCEEDS_WITHDRAWAL_COUNT_LIMIT | |
71 | Decline | PIN_NOT_CHANGED | |
75 | Decline | ALLOWABLE_NUMBER_OF_PIN_TRIES_EXCEEDED | |
76 | Decline | INVALID_TO_ACCOUNT_SPECIFIED | |
77 | Decline | INVALID_FROM_ACCOUNT_SPECIFIED | |
78 | Decline | INVALID_ACCOUNT_SPECIFIED_GENERAL | |
81 | Decline | DOMESTIC_DEBIT_TRANSACTION_NOT_ALLOWED_REGIONAL_USE_ONLY | |
83 | Decline | CARD_DESTROYED | |
84 | Decline | INVALID_AUTHORIZATION_LIFE_CYCLE | |
86 | Decline | PIN_VALIDATION_NOT_POSSIBLE | |
88 | Decline | CRYPTOGRAPHIC_FAILURE | |
89 | Decline | UNACCEPTABLE_PIN__TRANSACTION_DECLINED__RETRY | |
91 | Decline | AUTHORIZATION_PLATFORM_OR_ISSUER_SYSTEM_INOPERATIVE | |
92 | Decline | UNABLE_TO_ROUTE_TRANSACTION | |
94 | Decline | DUPLICATE_TRANSMISSION_DETECTED | |
96 | Decline | SYSTEM_ERROR | |
99 | Decline | CARD_VOIDED |
3DS Exemption Type (3dsExemptionType
)
Value | Description |
---|---|
0 | Transaction not exempt from SCA or unknown. |
1 | Transaction is exempt from SCA due to being on an exempt Merchant Category Code (MCC). (Acquirer did not provide an SCA exemption indicator.) (As of 11/02/2020, exempt MCCs are: 4111, 4112, 4131, 4784, 7523) |
2 | Contactless transaction under low-value limits. |
3 | E-commerce transaction under low-value limits. |
4 | Recurring/installment transaction. |
5 | Credit. Visa expects credit transactions to be out-of-scope. |
6 | Mail Order, Telephone Order or other cardholder-not-present transaction (except recurring which is above) which is excluded from SCA requirements. |
7 | Acquirer is exempt (located in a country outside of the EEA or UK, so do not fall under the PSD2 jurisdiction). |
8 | Not a transaction under PSD2 rules |
9 | Reserved for a possible future detected exemption |
A | Acquirer transaction risk analysis. |
C | Secure corporate payment. |
D | SCA delegation. |
M | Merchant initiated transaction. |
O | Authentication outage exemption. |
R | Recurring payment. |
T | Trusted merchant. |
V | Low value payment. |
Card Transaction object
json
{
"cardtransactionId":"2xxx88",
"cardId":"1xx9", // related Card id
"walletId":"9xx32", // related Wallet id
"walletCurrency":"978",
"merchantId":"2288442AO1EOAZQ",
"merchantName":"REGULARISATION TVA",
"merchantCity":"330768976257 ",
"merchantCountry":"FRA",
"paymentLocalTime":"94902",
"publicToken":"58xxxx220",
"paymentAmount":"180.00",
"paymentCurrency":"978",
"fees":"0.00",
"paymentCountry":"FRA",
"paymentId":"1xxx63",
"paymentStatus":"A", // see table above
"paymentLocalAmount":"180.00",
"posCardholderPresence":"0", // see list above
"posPostcode":"5008",
"posCountry":"507",
"posTerminalId":"13061803",
"posCardPresence":"4", // see list above
"panEntryMethod":"1",
"authorizationNote":"",
"authorizationResponseCode":"0", // see table above
"authorizationIssuerId":"2354807787",
"authorizationIssuerTime":"2017-10-16 10:49:03",
"authorizationMti":"100", // see list above
"authorizedBalance":"18186.65",
"limitAtmYear":"0",
"limitAtmMonth":"0",
"limitAtmWeek":"100",
"limitAtmAll":"0",
"limitPaymentYear":"0",
"limitPaymentMonth":"5000",
"limitPaymentWeek":"5000",
"limitPaymentDay":"5000",
"limitPaymentAll":"0",
"totalLimitAtmWeek":"0.00",
"totalLimitAtmDay":"0.00",
"totalLimitAtmAll":"0.00",
"totalLimitPaymentYear":"0.00",
"totalLimitPaymentMonth":"1980.00",
"totalLimitPaymentWeek":"1980.00",
"totalLimitPaymentDay":"180.00",
"totalLimitPaymentAll":"0.00",
"cardDigitalizationExternalId": "0",
"mccCode":"5734",
"acquirerId": "12653",
"is3DS": null,
"merchantAddress": "",
"paymentLocalDate": "",
"3dsExemptionType": "",
"optimizedMerchantName": "",
"merchantLogo": "",
"merchantCategory": "",
"transactionSubtype": "",
"receiverData": "",
"senderData": "",
"transactionTypeIdentifier": "",
"localMerchantId": ""
}
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
Endpoints
Endpoint | Scope |
---|---|
/v1/cardtransactions Search Card transactions | read_only |
/v1/cardtransactions/{cardTransactionId} Retrieve a specific transaction, using its id | read_only |
/v1/auth-requests/{authenticationRequestID}/result Answer to a Strong Customer Authentication request | read_write |
Reading – Find out more about Transactions
Object relations diagram
Tip – Diagram is interactive
Click on the diagram nodes to access the relevant documentation.