Introduction

A Card Transaction represents a step of a card payment made with a Treezor-issued Card (e.g., authorization, settlement, or refund). They share the same paymentId value when generated by the same card payment.

Key attributes

Below are some of the most important Card Transaction 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, ISO 4217 3-digit code.
merchantId	string	The MID
merchantName	string	The name 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)
paymentId	string	The unique identifier of the card payment (or attempted payment), allowing you to follow the card transaction life cycle.
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-digit 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.
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
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: 0 – The card was present 1 – The card was absent 9 – The card presence cannot be determined
panEntryMethod	string	How the PAN was captured by the merchant. See list below
authorizationNote	string	Contains detailed information regarding a declined transaction. See Authorization notes
authorizationResponseCode	string	The precise status of the transaction. See Authorization response codes
authorizationIssuerId	string	The transaction identifier as generated by 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 identifier of the merchant's bank (acquirer) in the form of 5 to 6 digits.
is3DS	string	Indicates whether 3DSecure was used for authentication: 1 – 3DS was used 0 – 3DS was not used
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 Apple Pay or Google Pay for example).
localMerchantId	string	Indicates the merchant's SIREN or SIRET if available.

Please note that 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.

API – API Reference available

For a complete list of Card Transaction attributes, check the Card Transactions section of the API Reference.

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: Refund is successful and the buyer has been refunded Payment is successful and the merchant has been paid MoneySend is successful and the cardholder's bank account has been credited
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

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": ""
}

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

• Transactions lifecycle
• Transactions examples
• Transactions authentication

Object relations diagram

Tip – Diagram is interactive

Click on the diagram nodes to access the relevant documentation.