Transaction response
The Transaction object describes a transaction. Unlike Payment , the Transaction object contains only one transaction.
Structure of the Transaction object
The structure of the Transaction object is as follows:
Response reference
amount
Payment amount in its smallest currency unit (cent for euro).
Example: 30050 for EUR 300.50.
Format
creationDate
Date and time when the transaction was registered.
Format
currency
Payment currency. Alphabetic code in uppercase according to alpha-3 (ISO 4217).
Eg: "EUR" for the euro.
Format
Possible values
The possible values are:
Currency | ISO 4217 ENCODING | Fractional unit |
---|---|---|
Australian dollar (036) | AUD | 2 |
Canadian dollar (124) | CAD | 2 |
Danish crown (208) | DKK | 2 |
Japanese yen (392) | JPY | 0 |
Norwegian crown (578) | NOK | 2 |
Swedish krona (752) | SEK | 2 |
Swiss franc (756) | CHF | 2 |
Pound Sterling (826) | GBP | 2 |
US dollar (840) | USD | 2 |
Euro (978) | EUR | 2 |
detailedErrorCode
Detailed unfiltered and unmodified error code returned by the Acquirer.
See the List of authorization return codes for more information.
Format
detailedErrorMessage
Detailed unfiltered error message returned by the acquirer or the payment application.
Contains contextual information to help understand the error.
This field may be set to null when errorCode equals ACQ_001 .
See the detailedErrorCode field description to see the reason of the authorization refusal.
Format
detailedStatus
The detailedStatus parameter provides detailed information on the payment status. Each of the statuses is specific to the used payment method.
Possible values
The possible values are:
detailedStatus | DESCRIPTION |
---|---|
ACCEPTED | Status of a VERIFICATION type transaction for which the authorization or inquiry has been accepted. This status cannot change. Transactions with the "ACCEPTED" status are never captured at the bank. A VERIFICATION transaction is created when a token without payment is created or updated. |
AUTHORISED | The amount is authorized and will be captured automatically. |
AUTHORISED_TO_VALIDATE | The transaction, created in manual validation mode, is authorized. The merchant must manually validate the transaction for it to be captured at the bank. The transaction can be validated as long as the expiration date of the authorization request has not passed. If this date is exceeded, then the payment takes the EXPIRED status. The Expired status is final. |
CANCELLED | The transaction has been canceled. |
CAPTURED | The transaction amount has been captured. |
EXPIRED | The expiry date of the authorization request has been reached and the Merchant has not validated the transaction. The cardholder will therefore not be debited. |
PARTIALLY_AUTHORISED | The transaction has been partially paid. |
REFUSED | The transaction has been rejected. |
UNDER_VERIFICATION | Current acquirer verification processes. This status is not final. |
WAITING_AUTHORISATION | The capture delay is longer than the authorization validity period. |
WAITING_AUTHORISATION_TO_VALIDATE | The capture delay is longer than the authorization validity period. The Merchant must manually validate the transaction in order for the authorization request and the capture to take place. |
ERROR | An unexpected error has occurred. |
For more information on the transaction lifecycle, go to: Transaction lifecycle .
Format
effectiveStrongAuthentication
Indicates whether the cardholder successfully authenticated during the payment.
Possible values
The possible values are:
Value | DESCRIPTION |
---|---|
ENABLED | The cardholder has successfully authenticated him or herself. |
DISABLED | The payment is not subject to cardholder authentication or cardholder authentication has failed. |
Format
errorCode
Error code. See Error codes for more information.
Format
errorMessage
Error message. See Error codes for more information.
Format
metadata
Custom values linked to the transaction, in JSON format.
Example of a call
For example, to pass a custom value, such as the Buyer's eye color, add the following to your query:
{ "metadata": { "eyesColor": "blue" } }
This value will be returned in the newly created transaction object.
You can also use the metadata “ orderInfo1 ”, “ orderInfo2 ” and “ orderInfo3 ” to send complementary information about the order
This data can be found later in the Extra tab of the transaction details via your
Format
operationType
Type of operation.
Possible values
The possible values are:
Value | DESCRIPTION |
---|---|
DEBIT | Debit operation. |
CREDIT | Refund operation. |
VERIFICATION | Payment method verification operation. |
Format
uuid
Unique transaction ID generated by the payment gateway.
Format
paymentMethodToken
Token associated with a payment method.
Only tokens associated with a credit card are supported.
Format
paymentMethodType
Type of payment method.
Possible values
Value | DESCRIPTION |
---|---|
CARD | Card payment |
SDD | SEPA Direct Debit |
Format
shopId
Shop ID.
Format
status
Simplified transaction status. It is the same for all payment methods. It allows you to implement a generic code compatible with all payment methods.
Each payment method also has dedicated statuses. See the detailedStatus property for more information.
Possible values
The possible values are:
STATUS | DESCRIPTION |
---|---|
PAID | The transaction is paid. |
UNPAID | The transaction is not paid. |
RUNNING | The transaction is in progress. |
PARTIALLY_PAID | The transaction is partially paid. |
For more information on the transaction lifecycle, go to: Transaction lifecycle .
Format
orderEffectiveAmount
Path: orderDetails.orderEffectiveAmount
Initial transaction amount in case of currency conversion.
Format
orderDetails.mode
Allows to define the mode in which the order was created.
Possible values
The possible values are:
STATUS | DESCRIPTION |
---|---|
TEST | For a test order. |
PRODUCTION | For the actual order. |
Format
orderCurrency
Path: orderDetails.orderCurrency
Order currency code, in the 4217 alpha-3 format.
Eg: "EUR" for the euro.
Format
orderDetails.orderId
Order reference defined by the Merchant. Does not support UTF-8 characters.
Format
orderTotalAmount
Path: orderDetails.orderTotalAmount
Total amount of the order expressed in the smallest monetary unit (cent for euro).
Example: 30050 for EUR 300.50.
Format
customer.reference
Buyer ID on the merchant side.
Format
customer.email
Buyer's e-mail address.
Format
address
Path: customer.billingDetails.address
Billing address.
Warning: the characters > and < are not authorized.
Format
address2
Path: customer.billingDetails.address2
Second line of the billing address.
Warning: the characters > and < are not authorized.
Format
category
Path: customer.billingDetails.category
Buyer type.
Format
Possible values
values | DESCRIPTION |
---|---|
PRIVATE | Individual buyer type. |
COMPANY | Company buyer type. |
cellPhoneNumber
Path: customer.billingDetails.cellPhoneNumber
Buyer's cell phone number.
Accepts all formats:
Examples:
- 0623456789
- +33623456789
- 0033623456789
- (+34) 824 65 43 21
- 87 77 12 34
Format
city
Path: customer.billingDetails.city
City of the billing address.
Format
country
Path: customer.billingDetails.country
Buyer's country (in uppercase, in accordance with the ISO 3166-1 alpha-2 country codes).
Format
Possible values
Examples of possible values:
Country | Code |
---|---|
AUSTRIA | AT |
BRAZIL | BR |
CORSICA | FR |
IVORY COAST | CI |
FRANCE | FR |
GUADELOUPE | GP |
INDIA | IN |
MARTINIQUE | MQ |
NEW CALEDONIA | NC |
ST-PIERRE-ET-MIQUELON | PM |
FRENCH POLYNESIA | PF |
district
Path: customer.billingDetails.district
District of the billing address.
Format
firstName
Path: customer.billingDetails.firstName
Buyer's first name.
Format
identityCode
Path: customer.billingDetails.identityCode
National identifier. Allows to identify each citizen within a country.
Format
language
Path: customer.billingDetails.language
Buyer's language code, according to ISO 639-1.
Specify the language in which payment confirmation e-mails are sent.
Format
Possible values
Examples of possible values:
Language | Code |
---|---|
German (Germany) | DE |
English (United Kingdom) | EN |
English (United States) | EN |
Chinese (Traditional) | ZH |
Spanish (Spain) | ES |
Spanish (Chile) | ES |
French (France) | FR |
Italian (Italy) | IT |
Japanese (Japan) | JP |
Dutch (the Netherlands) | NL |
Polish (Poland) | PL |
Portuguese (Brazil) | PT |
Portuguese (Portugal) | PT |
Russian (Russia) | RU |
lastName
Path: customer.billingDetails.lastName
Buyer's last name.
Format
legalName
Path: customer.billingDetails.legalName
Legal name.
Format
phoneNumber
Path: customer.billingDetails.phoneNumber
Buyer's phone number.
Accepts all formats:
Examples:
- 0123456789
- +33123456789
- 0033123456789
- (00.571) 638.14.00
- 40 41 42 42
Format
state
Path: customer.billingDetails.state
Region (state) of the billing address. It is recommended, but not mandatory, to pass the value in ISO-3166-2.
Format
streetNumber
Path: customer.billingDetails.streetNumber
Street number of the billing address.
Accepted characters:
- Alphabetical characters (from "A" to "Z" and from "a" to "z")
- Space
Format
title
Path: customer.billingDetails.title
Buyer's title.
Examples:
- Mr
- Ms
- Mrs
Format
zipCode
Path: customer.billingDetails.zipCode
Zip code of the billing address.
Format
address
Path: customer.shippingDetails.address
Shipping address.
Warning: the characters > and < are not authorized.
Format
address2
Path: customer.shippingDetails.address2
Second line of the shipping address.
Warning: the characters > and < are not authorized.
Format
category
Path: customer.shippingDetails.category
Buyer type.
Format
Possible values
values | DESCRIPTION |
---|---|
PRIVATE | Individual buyer type. |
COMPANY | Company buyer type. |
city
Path: customer.shippingDetails.city
Shipping city.
Format
country
Path: customer.shippingDetails.country
Shipping country (in uppercase, in accordance with the ISO 3166-1 alpha-2 country codes).
Format
Possible values
Examples of possible values:
Country | Code |
---|---|
AUSTRIA | AT |
BRAZIL | BR |
CORSICA | FR |
IVORY COAST | CI |
FRANCE | FR |
GUADELOUPE | GP |
INDIA | IN |
MARTINIQUE | MQ |
NEW CALEDONIA | NC |
ST-PIERRE-ET-MIQUELON | PM |
FRENCH POLYNESIA | PF |
deliveryCompanyName
Path: customer.shippingDetails.deliveryCompanyName
Name of the delivery company.
Format
district
Path: customer.shippingDetails.district
District of the billing address.
Format
firstName
Path: customer.shippingDetails.firstName
First name of the recipient.
Format
identityCode
Path: customer.shippingDetails.identityCode
National identifier. Allows to identify each citizen within a country.
Format
lastName
Path: customer.shippingDetails.lastName
Buyer's last name.
Format
legalName
Path: customer.shippingDetails.legalName
Legal name in case of shipping to a company.
Format
phoneNumber
Path: customer.shippingDetails.phoneNumber
Buyer's phone number.
Accepts all formats:
Examples:
- 0123456789
- +33123456789
- 0033123456789
- (00.571) 638.14.00
- 40 41 42 42
Format
shippingMethod
Path: customer.shippingDetails.shippingMethod
Shipping mode.
Format
Possible values
Value | DESCRIPTION |
---|---|
RECLAIM_IN_SHOP | Item pickup at the shop. |
RELAY_POINT | Use of a third-party pickup network (Kiala, Alveol, etc.). |
RECLAIM_IN_STATION | Pickup at an airport, a train station or a travel agency. |
PACKAGE_DELIVERY_COMPANY | Shipping by the transporter (Colissimo, UPS, etc.). |
ETICKET | Issue of an electronic ticket, online download of the product. |
CARD_HOLDER_ADDRESS | Delivery to the buyer. Reserved for future use. |
VERIFIED_ADDRESS | Delivery to a verified address. Reserved for future use. |
NOT_VERIFIED_ADDRESS | Delivery to a non-verified address. Reserved for future use. |
SHIP_TO_STORE | In-store pickup. Reserved for future use. |
DIGITAL_GOOD | Digital delivery. Reserved for future use. |
ETRAVEL_OR_ETICKET | E-ticket. Reserved for future use. |
OTHER | Other: Reserved for future use. |
PICKUP_POINT | Pickup point delivery. Reserved for future use. |
AUTOMATED_PICKUP_POINT | Pickup at an automatic pickup point. Reserved for future use. |
shippingSpeed
Path: customer.shippingDetails.shippingSpeed
Shipping delay.
Format
Possible values
Examples of possible values:
Value | DESCRIPTION |
---|---|
STANDARD | Standard shipping. |
EXPRESS | Express shipping (in less than 24h). |
PRIORITY | Priority shipping (Click & Collect). |
state
Path: customer.shippingDetails.state
Region of the billing address.
Format
streetNumber
Path: customer.shippingDetails.streetNumber
Street number of the delivery address.
Accepted characters:
- Alphabetical characters (from "A" to "Z" and from "a" to "z")
- Space
Format
zipCode
Path: customer.shippingDetails.zipCode
Zip code of the billing address.
Format
ipAddress
Path: customer.extraDetails.ipAddress
Buyer's IP address.
Format
fingerPrintId
Path: customer.extraDetails.fingerPrintId
Format
browserUserAgent
Path: customer.extraDetails.browserUserAgent
"User-Agent" header of buyer's browser (HTTP/1.1 - RFC. 2616)
Format
browserAccept
Path: customer.extraDetails.browserAccept
"Accept" header of buyer's browser (HTTP/1.1 - RFC. 2616)
Format
insuranceAmount
Path: customer.shoppingCart.insuranceAmount
Insurance amount for the entire order, expressed in the smallest monetary unit (cent for euro).
Example: 30050 for EUR 300.50.
Format
shippingAmount
Path: customer.shoppingCart.shippingAmount
Amount of delivery fees for the entire order, expressed in its smallest monetary unit (cent for euro).
Example: 30050 for EUR 300.50.
Format
taxAmount
Path: customer.shoppingCart.taxAmount
Amount of taxes for the entire order expressed in the smallest monetary unit (cent for euro).
Example: 30050 for EUR 300.50.
Format
cartItemInfo
Path: customer.shoppingCart.cartItemInfo
cardItemInfo is a list that contains Customer/ShoppingCartItemInfo objects.
See the customer.shoppingCart.* properties for more information.
Format
productAmount
Path: customer.shoppingCart.cartItemInfo.productAmount
Amount of the product expressed in the smallest currency unit (cent for euro).
Example: 30050 for EUR 300.50.
Format
productLabel
Path: customer.shoppingCart.cartItemInfo.productLabel
Product name.
Format
productQty
Path: customer.shoppingCart.cartItemInfo.productQty
Product quantity.
Format
productRef
Path: customer.shoppingCart.cartItemInfo.productRef
Product reference.
Format
productType
Path: customer.shoppingCart.cartItemInfo.productType
Product type.
Format
Possible values
Value | DESCRIPTION |
---|---|
FOOD_AND_GROCERY | Food and grocery |
AUTOMOTIVE | Cars / Moto |
ENTERTAINMENT | Entertainment / Culture |
HOME_AND_GARDEN | Home and gardening |
HOME_APPLIANCE | Household appliances |
AUCTION_AND_GROUP_BUYING | Auctions and group purchasing |
FLOWERS_AND_GIFTS | Flowers and presents |
COMPUTER_AND_SOFTWARE | Computers and software |
HEALTH_AND_BEAUTY | Health and beauty |
SERVICE_FOR_INDIVIDUAL | Services for individuals |
SERVICE_FOR_BUSINESS | Services for companies |
SPORTS | Sports |
CLOTHING_AND_ACCESSORIES | Clothes and accessories |
TRAVEL | Travel |
HOME_AUDIO_PHOTO_VIDEO | Sound, image and video |
TELEPHONY | Telephony |
productVat
Path: customer.shoppingCart.cartItemInfo.productVat
Product type.
Tax fee amount (expressed in the smallest currency unit).
Possible values
Value | DESCRIPTION |
---|---|
Integer | Transaction amount. Its value must be a positive integer (e.g.: 1234 for 12.34 EUR). |
Decimal number, lower than 100 | Percentage applied to the amount. Examples: 20.0 or 19.6532 |
To display a percentage applied to the payment amount for the product in question, the value should have maximum 4 digits after the decimal point. The decimal separator is mandatory for displaying a percentage. The decimal separator is represented by the "." symbol.
companyType
Path: subMerchantDetails.companyType
Company type of the sub-merchant. Transmitted by the payment facilitator.
Format
legalNumber
Path: subMerchantDetails.legalNumber
Legal identifier of the sub-merchant. Transmitted by the payment facilitator.
Format
name
Path: subMerchantDetails.name
Business name of the sub-merchant. Transmitted by the payment facilitator.
Format
url
Path: subMerchantDetails.url
URL of the sub-merchant. Transmitted by the payment facilitator.
Format
phoneNumber
Path: subMerchantDetails.phoneNumber
Telephone number of the sub-merchant. Transmitted by the payment facilitator.
Format
address1
Path: subMerchantDetails.address1
Address of the sub-merchant. Transmitted by the payment facilitator.
Format
address2
Path: subMerchantDetails.address2
Address line 2 of the sub-merchant. Transmitted by the payment facilitator.
Format
zip
Path: subMerchantDetails.zip
Zip code of the sub-merchant. Transmitted by the payment facilitator.
Format
city
Path: subMerchantDetails.city
City of the sub-merchant. Transmitted by the payment facilitator.
Format
country
Path: subMerchantDetails.country
Country code of the sub-merchant's address (ISO 3166 alpha-2 standard). Transmitted by the payment facilitator.
Format
mcc
Path: subMerchantDetails.mcc
MCC code of the sub-merchant. Transmitted by the payment facilitator.
Format
mid
Path: subMerchantDetails.mid
Contract number (MID) of the sub-merchant. Transmitted by the payment facilitator.
Format
softDescriptor
Path: subMerchantDetails.softDescriptor
Title (soft descriptor) of the sub-merchant that appears on the buyer's bank statement. Transmitted by the payment facilitator.
Format
liabilityShift
Path: transactionDetails.liabilityShift
Specified if the payment is guaranteed.
Possible values
The possible values are:
VALUES | DESCRIPTION |
---|---|
YES | The payment is guaranteed. |
NO | The payment is not guaranteed. |
nulle | The payment is not guaranteed. |
Format
mid
Path: transactionDetails.mid
Merchant ID number. If this field is populated, make sure you use the appropriate MID depending on the card scheme.
Format
effectiveAmount
Path: transactionDetails.effectiveAmount
Initial transaction amount in case of currency conversion.
Format
sequenceNumber
Path: transactionDetails.sequenceNumber
Transaction sequence number.
Format
effectiveCurrency
Path: transactionDetails.effectiveCurrency
Initial transaction currency in case of currency conversion.
Format
creationContext
Path: transactionDetails.creationContext
Specified the process that initiated the transaction.
Possible values
The possible values are:
VALUES | DESCRIPTION |
---|---|
CHARGE | For a debit request. |
REFUND | For a credit request. |
Format
parentTransactionUuid
Path: transactionDetails.parentTransactionUuid
UUID of the transaction source.
Format
paymentSource
Path: transactionDetails.cardDetails.paymentSource
Payment source.
Format
Possible values
The possible values are:
Value | DESCRIPTION |
---|---|
EC | E-commerce: the payment method details are entered by the Buyer. This value allows to have strong authentication during a payment. |
MOTO | MAIL OR TELEPHONE ORDER: entry by an operator. The payment information is sent by mail or e-mail. Requires a VAD contract |
CC | Call Center: payment made via a call center. Requires a VAD type contract. |
OTHER | Other sales channel. Returned output value for payments made via the Back-Office, payments by file, recurring payments, proximity payments, refunds via the Shopify CMS. |
Absent ou null | The default value is "EC". |
manualValidation
Path: transactionDetails.cardDetails.manualValidation
Transaction validation mode.
Format
Possible values
The possible values are:
Value | DESCRIPTION |
---|---|
NO | Automatic validation by the payment gateway. |
YES | Manual validation by the Merchant. |
null | Default configuration of the selected shop (configurable in the |
expectedCaptureDate
Path: transactionDetails.cardDetails.expectedCaptureDate
Date of capture in the bank expressed in ISO 8601 format defined by W3C.
Format
effectiveBrand
Path: transactionDetails.cardDetails.effectiveBrand
Card brand.
Payment method | Card type (effectiveBrand) |
---|---|
Carte enseigne Accord | ACCORD_STORE |
Carte enseigne Accord - Mode sandbox | ACCORD_STORE_SB |
Alipay | ALIPAY |
American Express | AMEX |
Titre-Restaurant Dématérialisé Apetiz | APETIZ |
Carte Cpay | AURORE-MULTI |
Bancontact Mistercash | BANCONTACT |
CB | CB |
Titre-Restaurant Dématérialisé Chèque Déjeuner | CHQ_DEJ |
Titre-Restaurant Dématérialisé Conecs | CONECS |
Chèque-Vacances Connect | CVCO |
Diners | DINERS |
Discover | DISCOVER |
e-carte bleue | E-CARTEBLEUE |
Ticket Eco Chèque Edenred | EDENRED_EC |
Ticket Sports & Culture Edenred | EDENRED_SC |
Ticket Compliment Edenred | EDENRED_TC |
Ticket Restaurant Edenred | EDENRED_TR |
Paiement en 3X Franfinance | FRANFINANCE_3X |
Paiement en 4X Franfinance | FRANFINANCE_4X |
Paiement en 3x sans frais par BNPP PF | FULLCB3X |
Paiement en 4x sans frais par BNPP PF | FULLCB4X |
Giropay | GIROPAY |
iDeal Internet Banking | IDEAL |
Carte Cadeau Illicado | ILLICADO |
Carte Cadeau Illicado - Mode sandbox | ILLICADO_SB |
JCB | JCB |
Maestro | MAESTRO |
Mastercard | MASTERCARD |
Multibanco | MULTIBANCO |
MyBank | MYBANK |
Paiement 3x 4x Oney | ONEY_3X_4X |
Cartes Enseignes partenaires d'Oney | ONEY_ENSEIGNE |
PayDirekt | PAYDIREKT |
Wallet Paylib | PAYLIB |
PayPal | PAYPAL |
PayPal - Mode sandbox | PAYPAL_SB |
PostFinance | POSTFINANCE |
PostFinance E-finance | POSTFINANCE_EFIN |
Solution de crédit en ligne Presto de Cetelem | PRESTO |
Przelewy24 | PRZELEWY24 |
Prélèvement Bancaire SEPA DIRECT DEBIT | SDD |
Titre-Restaurant Dématérialisé Sodexo | SODEXO |
Sofort Banking | SOFORT_BANKING |
Union Pay | UNION_PAY |
Visa | VISA |
Visa Electron | VISA_ELECTRON |
Vpay | VPAY |
Format
pan
Path: transactionDetails.cardDetails.pan
Truncated card number.
Format
expiryMonth
Path: transactionDetails.cardDetails.expiryMonth
Expiry month.
Format
expiryYear
Path: transactionDetails.cardDetails.expiryYear
Expiry year.
Format
country
Path: transactionDetails.cardDetails.country
Country code of the card.
Format
issuerCode
Path: transactionDetails.cardDetails.issuerCode
Code associated with the issuing bank.
Format
issuerName
Path: transactionDetails.cardDetails.issuerName
Name of the bank associated with the issuing bank.
Format
effectiveProductCode
Path: transactionDetails.cardDetails.effectiveProductCode
Product code of the card used for the payment.
Format
paymentMethodSource
Path: transactionDetails.cardDetails.paymentMethodSource
Allows to define the mode of the used payment method.
Possible values
The possible values are:
STATUS | DESCRIPTION |
---|---|
NEW | Transaction created using a new payment method. |
TOKEN | Transaction created using an existing payment method. |
Format
legacyTransId
Path: transactionDetails.cardDetails.legacyTransId
6 character long transaction identifier.
Format
cardHolderName
Path: transactionDetails.cardDetails.cardHolderName
Cardholder's first and last names.
Format
identityDocumentType
Path: transactionDetails.cardDetails.identityDocumentType
ID type.
Possible values:
Type | DESCRIPTION |
---|---|
DNI | Documento Nacional de Identidad |
CC | Cédula de ciudadania |
TI | Tarjeta de Identidad |
CE | Cédula de Extranjeria |
NI | Número de Identificación Tributaria |
PS | Pasaporte |
Format
identityDocumentNumber
Path: transactionDetails.cardDetails.identityDocumentNumber
Buyer's ID number.
The format depends on the ID type: between 7 and 13 characters, digits, letters and/or dots.
In Latin America, this parameter may be mandatory for some buyers.
Format
legacyTransDate
Path: transactionDetails.cardDetails.legacyTransDate
Date and time of payment request reception. Used for identifying transactions IDs in old format.
Format
amount
Path: transactionDetails.cardDetails.authorizationResponse.amount
Authorization amount.
Format
currency
Path: transactionDetails.cardDetails.authorizationResponse.currency
Code of the currency used during the authorization request.
Format
authorizationDate
Path: transactionDetails.cardDetails.authorizationResponse.authorizationDate
Date and time of the authorization request.
Format
authorizationNumber
Path: transactionDetails.cardDetails.authorizationResponse.authorizationNumber
Number of the authorization request.
Format
authorizationResult
Path: transactionDetails.cardDetails.authorizationResponse.authorizationResult
Return code of the authorization request.
See the List of authorization return codes for more information.
Format
authorizationMode
Path: transactionDetails.cardDetails.authorizationResponse.authorizationMode
Specifies the mode of the authorization request.
Possible values
values | DESCRIPTION |
---|---|
MARK | A pre-authorization of a null or unitary amount has been made, see below. |
FULL | An authorization of the total amount has been requested. |
When authorizationMode is MARK : An authorization for 1 EUR100 XPF1 CHF1 BRL100 CLP1 USD1000 XOF100 INR (or information request within the CB network if the acquirer supports it) has been made in order to check if the card is valid. This case occurs when the capture date exceeds the authorization validity period (e.g. 7 days for VISA / MasterCard / CB / AMEX in France).
Format
amount
Path: transactions.transactionDetails.cardDetails.markAuthorizationResponse.amount
Pre-authorization amount.
Format
currency
Path: transactions.transactionDetails.cardDetails.markAuthorizationResponse.currency
Code of the currency used during the pre-authorization request.
Format
authorizationDate
Path: transactions.transactionDetails.cardDetails.markAuthorizationResponse.authorizationDate
Date and time of the pre-authorization request.
Format
authorizationNumber
Path: transactions.transactionDetails.cardDetails.markAuthorizationResponse.authorizationNumber
Number of the pre-authorization request.
Format
authorizationResult
Path: transactions.transactionDetails.cardDetails.markAuthorizationResponse.authorizationResult
Return code of the pre-authorization request.
Format
captureDate
Path: transactionDetails.cardDetails.captureResponse.captureDate
Capture date and time.
Format
captureFileNumber
Path: transactionDetails.cardDetails.captureResponse.captureFileNumber
Capture number.
Format
refundAmount
Path: transactionDetails.cardDetails.captureResponse.refundAmount
Refunded amount.
Format
refundCurrency
Path: transactionDetails.cardDetails.captureResponse.refundCurrency
Currency of the refunded amount.
Format
effectiveRefundAmount
Path: transactionDetails.cardDetails.captureResponse.effectiveRefundAmount
Format
effectiveRefundCurrency
Path: transactionDetails.cardDetails.captureResponse.effectiveRefundCurrency
Format
transactionCondition
Path: transactionDetails.cardDetails.threeDSResponse.authenticationResultData.transactionCondition
Authentication status of 3D Secure.
Possible values
Authentication status of the cardholder.
VALUE | DESCRIPTION |
---|---|
COND_3D_SUCCESS | Authentication success. The Merchant and the cardholder are registered in the 3D Secure program and the buyer has correctly authenticated. |
COND_3D_FAILURE | Authentication failure. The Merchant and the cardholder are registered in the 3D Secure program but the Buyer did not manage to authenticate (wrong password). |
COND_3D_ERROR | Authentication error. The Merchant participates in the 3D Secure program but the payment gateway server has encountered a technical issue during the authentication process (while checking whether the card is registered in the 3D program or whether the cardholder is authenticated). |
COND_3D_NOTENROLLED | Cardholder not enrolled. The Merchant participates in the 3D Secure program but the cardholder's card is not enrolled. |
COND_3D_ATTEMPT | Authentication attempt. The Merchant and the cardholder are registered in the 3D Secure program but the buyer did not need to authenticate (the access control server of the bank that issued the card only implements the generation of proof of authentication attempt). |
COND_SSL | 3D Secure not applicable. The Merchant is not enrolled in 3D Secure or the sales channel is not covered by this guarantee. |
Format
enrolled
Path: transactionDetails.cardDetails.threeDSResponse.authenticationResultData.enrolled
Cardholder's enrollment status.
Possible values
The possible values are:
VALUE | DESCRIPTION |
---|---|
YES | Cardholder enrolled, 3DS authentication possible. Note: in the Back Office, the ENROLLED value is displayed (3D Secure tab in Transaction details). |
NO | Cardholder not enrolled. Note: in the Back Office, the NOT_ENROLLED value is displayed (3D Secure tab in Transaction details). |
UNKNOWN | Unable to verify the cardholder's enrollment status. Note: in the Back Office, the UNAVAILABLE value is displayed (3D Secure tab in Transaction details). |
Format
status
Path: transactionDetails.cardDetails.threeDSResponse.authenticationResultData.status
Authentication status of the cardholder.
Possible values
Authentication status of the cardholder.
VALUE | DESCRIPTION |
---|---|
YES | Successful authentication. Note: in the Back Office, the SUCCESS value is displayed (3D Secure tab in Transaction details). |
NO | Authentication error. Note: in the Back Office, the FAILED value is displayed (3D Secure tab in Transaction details). |
UNKNOWN | Authentication impossible. Note: in the Back Office, the UNAVAILABLE value is displayed (3D Secure tab in Transaction details). |
ATTEMPT | Authentication attempt Note: in the Back Office, the ATTEMPT value is displayed (3D Secure tab in Transaction details). |
Format
eci
Path: transactionDetails.cardDetails.threeDSResponse.authenticationResultData.eci
E-commerce index.
Possible values
The value depends on the 3DS authentication status and the card type. The possible values are:
CARD TYPE | STATUS=Y | STATUS=A | STATUS=U | STATUS=N |
---|---|---|---|---|
VISA - AMEX | 5 | 6 | 7 | - |
MasterCard | 02 | 01 | - | - |
Format
xid
Path: transactionDetails.cardDetails.threeDSResponse.authenticationResultData.xid
Unique transaction ID.
Format
cavvAlgorithm
Path: transactionDetails.cardDetails.threeDSResponse.authenticationResultData.cavvAlgorithm
Algorithm for checking the authentication status of the cardholder.
Possible values
The possible values are:
VALUE | DESCRIPTION |
---|---|
HMAC | HMAC |
CVV | Card Verification Value |
CVV_ATN | CVV Authentication Tracking Number |
SPA | MasterCard SPA Algorithm. |
A | AV-CB |
Format
cavv
Path: transactionDetails.cardDetails.threeDSResponse.authenticationResultData.cavv
Cardholder Authentication Verification Value.
Format
signValid
Path: transactionDetails.cardDetails.threeDSResponse.authenticationResultData.signValid
Validity of the PARes message signature.
Possible values
Authentication status of the cardholder.
VALUE | DESCRIPTION |
---|---|
nulle | 3DS unavailable. |
0 | Incorrect signature. |
1 | Correct signature. |
Format
brand
Path: transactionDetails.cardDetails.threeDSResponse.authenticationResultData.brand
Card brand.
Format
id
Path: transactionDetails.cardDetails.authenticationResponse.id
Unique identifier of the authentication, in UUID format.
Format
operationSessionId
Path: transactionDetails.cardDetails.authenticationResponse.operationSessionId
Unique identifier of the authentication, in UUID format.
Format
instructionType
Path: transactionDetails.cardDetails.authenticationResponse.value.instructionType
Type of instruction to carry out.
Format
Possible values
values | DESCRIPTION |
---|---|
FORM | Form with redirect type instruction. |
name
Path: transactionDetails.cardDetails.authenticationResponse.value.name
Instruction name.
Possible values
Value | DESCRIPTION |
---|---|
CHALLENGE | Challenge Instruction that allows interactive user authentication via the ACS. |
FINGERPRINT | Fingerprint Instruction that allows to identify the user via the ACS. |
Format
_type
Path: transactionDetails.cardDetails.authenticationResponse.value._type
Type of received response. The interpretation of the rest of the response depends on this attribute.
Possible values
Value | DESCRIPTION |
---|---|
AuthenticationInstruction | Instruction type response. |
AuthenticationResult | Final result type response. |
Format
timeout
Path: transactionDetails.cardDetails.authenticationResponse.value.timeout
Maximum response delay when executing an instruction, expressed in seconds. Beyond this delay, it is necessary to initiate the return to the payment gateway server in order to obtain the final result.
Format
method
Path: transactionDetails.cardDetails.authenticationResponse.value.http.method
Method (verb) used for the request.
Possible values
Value | DESCRIPTION |
---|---|
DELETE | Delete method |
GET | Get method |
PATCH | Patch method |
POST | Post method |
PUT | Put method |
Format
url
Path: transactionDetails.cardDetails.authenticationResponse.value.http.url
URL to which the HTTP form must be submitted.
Format
body
Path: transactionDetails.cardDetails.authenticationResponse.value.http.body
List of request body parameters, presented as “name”: “value”.
Format
headers
Path: transactionDetails.cardDetails.authenticationResponse.value.http.headers
List of HTTP request headers, presented as “name”: “value”.
Format
element
Path: transactionDetails.cardDetails.authenticationResponse.value.target.element
Type of the target HTML element which contains the instruction.
Possible values
Value | DESCRIPTION |
---|---|
IFRAME | iFrame |
Format
height
Path: transactionDetails.cardDetails.authenticationResponse.value.target.height
Height of the HTML target in pixels.
Format
visible
Path: transactionDetails.cardDetails.authenticationResponse.value.target.visible
Boolean indicating whether or not the HTML target must be visible.
Format
width
Path: transactionDetails.cardDetails.authenticationResponse.value.target.width
Width of the HTML target in pixels.
Format
showUrl
Path: transactionDetails.cardDetails.authenticationResponse.value.target.showUrl
Technical field for internal use that allows to show or hide the URL of the ACS.
Format
challengePreference
Path: transactionDetails.cardDetails.authenticationResponse.protocol.challengePreference
Indicates whether or not the merchant has requested a challenge.
Possible values
values | DESCRIPTION |
---|---|
NO_PREFERENCE | No particular preference. |
NO_CHALLENGE_REQUESTED | Challenge is not explicitly requested. |
CHALLENGE_REQUESTED | Challenge is requested by the Merchant. |
Format
name
Path: transactionDetails.cardDetails.authenticationResponse.protocol.name
Name of the protocol used by the cardholder authentication services.
Possible values
Value | DESCRIPTION |
---|---|
THREEDS | 3D Secure protocol |
PROCESOS_DINERS | Procesos Diners OTP protocol |
OSB | Protocol OTP OSB |
Format
simulation
Path: transactionDetails.cardDetails.authenticationResponse.protocol.simulation
Boolean indicating if the authentication must be carried out in simulation mode. Simulation mode allows to perform merchant integration without being in production or using a real card.
Format
network
Path: transactionDetails.cardDetails.authenticationResponse.protocol.network
Network where the payment method was authenticated.
Currently supported versions
Value |
---|
CB |
VISA |
MASTERCARD |
AMEX_SAFEKEY |
ELO |
PROCESOS_DINERS |
DINERS |
DISCOVER |
OSB |
Format
version
Path: transactionDetails.cardDetails.authenticationResponse.protocol.version
Version of the protocol used by the cardholder authentication services.
Currently supported versions
Value | DESCRIPTION |
---|---|
1.0.2 | Version 1.0.2 |
2.1.0 | Version 2.1.0 |
Format
authenticationType
Path: transactionDetails.cardDetails.authenticationResponse.value.authenticationType
Type of authentication that has been applied.
Possible values
Value | DESCRIPTION |
---|---|
FRICTIONLESS | Authentication in Frictionless mode, i.e. transparent for the Buyer. |
CHALLENGE | Authentication with a Challenge, the Buyer had to explicitly authenticate him/herself via the ACS. |
Format
commerceIndicator
Path: transactionDetails.cardDetails.authenticationResponse.value.commerceIndicator
Commerce Indicator, or ECI (Electronic Commerce Indicator) for the 3DS protocol. Indicator returned by the ACS to report the results of cardholder’s authentication attempt.
In case of authentication without payment (e.g. in case of card registration) MasterCard can return the following 2 values:
VALUE | DESCRIPTION |
---|---|
N0 | Not authenticated |
N2 | Authenticated |
Format
status
Path: transactionDetails.cardDetails.authenticationResponse.value.status
Authentication status, i.e. the positive/negative outcome of the authentication.
Possible values
Value | DESCRIPTION |
---|---|
ATTEMPT | Proof of authentication attempt when authentication is not available. |
ENROLLED_UNAVAILABLE | Unable to assess the enrollment status. |
FAILED | Authentication error. |
NOT_ENROLLED | Card not enrolled. |
SUCCESS | Successful authentication. |
UNAVAILABLE | The authentication could not be completed (technical error, etc.). |
DISABLED | Authentication disabling requested. |
REJECTED | Authentication rejected by the ACS. |
Format
authenticationIdType
Path: transactionDetails.cardDetails.authenticationResponse.value.authenticationId.authenticationIdType
Type of authentication that has been applied.
Possible values
Value | DESCRIPTION |
---|---|
xid | The field originates from the xid field of the v1 3DS protocol. |
dsTransId | The field originates from the dsTransId field of the v2 3DS protocol. |
Format
value
Path: transactionDetails.cardDetails.authenticationResponse.value.authenticationId.value
Value of the authentication transaction identifier known to the banking network.
The length of the field varies depending on the authentication protocol.
Protocol | Format / Length | value Example: |
---|---|---|
3DS v1 (xid) | chaine / 28 caractères alphanumériques | f8e120f1fe934db8b8e58ba4c423db48 |
3DS v2 (dsTransId) | chaine / 32 caractères alphanumériques + 4 tirets | 4317fdc3-ad24-5443-8000-000000000891 |
Format
authenticationValueType
Path: transactionDetails.cardDetails.authenticationResponse.value.authenticationValue.authenticationValueType
Type of authentication value.
Possible values
Value | DESCRIPTION |
---|---|
AEVV | American Express Verification Value (used by Amex). |
CAVV | Cardholder Authentication Verification Value (used by VISA). |
AAV | Accountholder Authentication Value (used by Mastercard). |
Format
value
Path: transactionDetails.cardDetails.authenticationResponse.value.authenticationValue.value
Final authentication value (depending on the DS this value can be called CAVV, AEVV or AAV) Character string encoded in base64 with a size of 28 characters.
Format
code
Path: transactionDetails.cardDetails.authenticationResponse.value.reason.code
Additional code explaining the result. E.g.: DS_TIMEOUT
Format
message
Path: transactionDetails.cardDetails.authenticationResponse.value.reason.message
Additional message explaining the result.
Format
installmentNumber
Path: transactionDetails.cardDetails.installmentNumber
Number of installments.
Format
installmentCode
Path: transactionDetails.cardDetails.installmentCode
Code of the payment option used for the payment.
Format
subscriptionId
Path: transactionDetails.subscriptionDetails.subscriptionId
Recurring payment identifier.
Format
name
Path: transactionDetails.fraudManagement.riskControl.name
Name of the control implemented for risk assessment.
Possible values
The possible values are:
VALUE | DESCRIPTION |
---|---|
CARD_FRAUD | Checks whether the cardholder's card number is on the card greylist. |
SUSPECT_COUNTRY | Checks whether the cardholder's card number is on the list of forbidden countries. |
IP_FRAUD | Checks whether the cardholder's IP address is on the IP greylist. |
CREDIT_LIMIT | Checks the purchase frequency and amounts for the same card number, or the maximum amount of an order. |
BIN_FRAUD | Checks whether the BIN code of the card is on the BIN code greylist. |
ECB | Checks whether the Buyer's card belongs to the "e-carte bleue" type. |
COMMERCIAL_CARD | Checks whether the Buyer's card is a commercial credit card. |
SYSTEMATIC_AUTO | Checks whether the Buyer's card is a MAESTRO or VISA ELECTRON credit card. |
INCONSISTENT_COUNTRIES | Checks whether the country of the IP address, the country of the payment card and the Buyer's country of residence match. |
NON_WARRANTY_PAYMENT | Checks the liability shift of the transaction. |
SUSPECT_IP_COUNTRY | Checks whether the cardholder's country, identified by the IP address, is on the list of forbidden countries. |
Format
result
Path: transactionDetails.fraudManagement.riskControl.result
Name of the control implemented for risk assessment.
Possible values
Result of the risk assessment.
VALUE | DESCRIPTION |
---|---|
OK | OK |
WARNING | Informational control failed. |
ERROR | Blocking control failed. |
Format
score
Path: transactionDetails.fraudManagement.riskAnalysis.score
Analysis identifier on the risk analyzer side.
Format
resultCode
Path: transactionDetails.fraudManagement.riskAnalysis.resultCode
Code returned by an external risk analyzer.
Possible values
The possible values are:
STATUS | DESCRIPTION |
---|---|
INVALID_CREDENCIAL | Configuration problem of the risk management contract. |
COMUNICATION_PROBLEM | Impossible to connect to the risk analyzer. |
DATA_PROCESSING_PROBLEM | Problem occurred when processing the data being transmitted or the response of the risk management system. |
MISSING_MANDATORY_ORDER_INFO | Order details are missing. |
MISSING_MANDATORY_SHIPPING_INFO | Shipping details are missing. |
MISSING_MANDATORY_SHIPPING_ADDRESS_INFO | Shipping address details are missing. |
MISSING_MANDATORY_BILLING_INFO | Billing details are missing. |
MISSING_MANDATORY_BILLING_ADDRESS_INFO | Billing address details are missing. |
MISSING_MANDATORY_CARD_INFO | Payment method details are missing. |
MISSING_MANDATORY_CUSTOMER_INFO | Buyer details are missing. |
APA | Specific to ClearSale. The transaction is automatically approved according to the defined parameters. |
APM | Specific to ClearSale. The transaction is manually approved by an analyst. |
RPM | Specific to ClearSale. The order is rejected due to missing buyer details in accordance with the implemented policy. |
AMA | Specific to ClearSale. Waiting for manual analysis. The order is waiting to be analyzed. |
ERR | Specific to ClearSale. Error. |
NVO | Specific to ClearSale. New order. Waiting to be processed and classified. |
SUS | Specific to ClearSale. Order manually suspended. The order is suspended for suspected fraud. |
CAN | Specific to ClearSale. Order is canceled. The order has been canceled by the buyer. |
FRD | Specific to ClearSale. Fraud confirmed by the credit card operator or the cardholder. |
RPA | Specific to ClearSale. Order automatically declined. The order has been automatically declined in accordance with the parameters of the external risk analyzer. |
RPP | Specific to ClearSale. Order automatically declined. The order is reproved based on the customer or ClearSale policy |
100 | Specific to CyberSource. Transaction successfully completed. |
101 | Specific to CyberSource. Transaction is declined. One or more parameters are missing. |
102 | Specific to CyberSource. Transaction is declined. One or more parameters have invalid data. |
150 | Specific to CyberSource. Error. |
151 | Specific to CyberSource. Error. The request was received but the time limit has been exceeded. This error does not include the timeouts between the client and the server. |
152 | Specific to CyberSource. Error. The request was received but a service did not finish an operation in time. |
202 | Specific to CyberSource. Declined. Card expired. |
231 | Specific to CyberSource. Declined. Invalid account number. |
234 | Specific to CyberSource. Declined. A problem occurred with the merchant CyberSource configuration. |
400 | Specific to CyberSource. Declined. The score of the fraud exceeds the tolerance. |
480 | Specific to CyberSource. The order is marked and needs to be reviewed by the Decision Manager. |
481 | Specific to CyberSource. The order has been rejected by the Decision Manager. |
APPROVE | Specific to Konduto. Konduto recommends to accept the transaction. If no rules contradict this recommendation, the transaction status will be AUTHORISED. |
DECLINE | Specific to Konduto. Konduto recommends to decline the transaction. The transaction status will be REFUSED. |
REVIEW | Specific to Konduto. Konduto recommends to check the transaction. Depending on the result of the 3D Secure authentication, the transaction status will be: |
AUTHORISED_TO_VALIDATE | If the cardholder has successfully authenticated. |
REFUSED | In case of authentication failure of the cardholder. |
Format
status
Path: transactionDetails.fraudManagement.riskAnalysis.status
Code returned by an external risk analyzer.
Risk analysis status.
Possible values
The possible values are:
VALUE | DESCRIPTION |
---|---|
P_SEND_OK | Success. "Sent to clearsale and successfully processed". |
P_TO_SEND | The transaction analysis is scheduled to be sent. “Transaction analysis is scheduled to be sent to risk analyzer”. |
P_TO_SEND_KO | Processing error. "Problem when tried to send to risk analyzer." |
P_PENDING_AT_ANALYZER | The analysis result is being processed by the risk analyzer. “Analysis result is still being processed by the risk analyzer. We should keep checking/waiting for the analysis result”. |
P_MANUAL | Waiting for manually sending the analysis. “Analysis should be requested through user request (not automatically)”. |
P_SKIPPED | Discarded. "Analysis request discarded by current transaction status/problem". |
P_SEND_EXPIRED | Expired.* "Analysis request expired". |
Format
requestId
Path: transactionDetails.fraudManagement.riskAnalysis.requestId
Analysis identifier on the risk analyzer side.
Format
extraInfo
Path: transactionDetails.fraudManagement.riskAnalysis.extraInfo
Specific to CyberSource. Codes returned by the DecisionManager.
Format
fingerPrintId
Path: transactionDetails.fraudManagement.riskAnalysis.fingerPrintId
Disable the requested authentication Allows the session ID (or fingerPrint Id) to be transmitted to the payment gateway for completing the risk analysis.
The supported analyzers are:
- NOTO
- Cybersource
- MonitorPlus
- ClearSale
Can contain uppercase and lowercase characters, numbers or hyphens ([A-Z] [a-z], 0-9, _, -).
Format
results
Path: transactionDetails.fraudManagement.riskAssessments.results
List of actions made with the transaction, following the activation of the advanced risk assessment enabled in the Back Office.
Possible values
The possible values are:
VALUE | DESCRIPTION |
---|---|
ENABLE_3DS | 3D Secure enabled. |
DISABLE_3DS | 3D Secure disabled. |
MANUAL_VALIDATION | The transaction has been created via manual validation. The payment capture is temporarily blocked to allow the Merchant perform all the desired verifications. |
REFUSE | Transaction is declined. |
RUN_RISK_ANALYSIS | Call to an external risk analyzer provided that the Merchant has a contract. See the description of the TransactionDetails object. FraudManagement. RiskAnalysis to identify the list of possible values and their description. |
INFORM | A warning message appears. The Merchant is notified that a potential problem has been identified. The Merchant is informed via one or several notification center rules (IPN, e-mail or SMS). |
Format
taxRate
Path: transactionDetails.taxRate
Used by some payment methods in Latin America. Allows you to transmit the tax rate applied to the entire order. The value must be the percentage to be applied (21 for 21%)
Format
taxAmount
Path: transactionDetails.taxAmount
Amount of taxes for the entire order expressed in the smallest monetary unit (cent for euro).
Example: 30050 for EUR 300.50.
Format
preTaxAmount
Path: transactionDetails.preTaxAmount
Allows to define the pre-tax amount of the whole order.
The value must be specified in the smallest currency unit.
Format
externalTransactionId
Path: transactionDetails.externalTransactionId
External transaction reference.
Format
dccAmount
Path: transactionDetails.dcc.dccAmount
Transaction amount expressed in the smallest currency unit defined by dccCurrency (cent for euro).
This field is populated only if the card is eligible for the dynamic currency conversion (DCC) service and if the buyer has chosen to pay in the currency of their card.
The conversion rate is returned in the dccChangeRate field.
Format
dccCurrency
Path: transactionDetails.dcc.dccCurrency
Numeric code in accordance with the ISO 4217 standard of the currency chosen by the Buyer if the card is eligible for the Dynamic Currency Conversion (DCC) service.
This field is populated only if the card is eligible for the dynamic currency conversion (DCC) service and if the buyer has chosen to pay in the currency of their card.
The conversion rate is returned in the dccChangeRate field.
Format
dccChangeRate
Path: transactionDetails.dcc.dccChangeRate
Exchange rate used to calculate the effective payment amount.
Format
dccMarkup
Path: transactionDetails.dcc.dccMarkup
Indicates the percentage (or rate) of sales margin on the total amount.
This field is populated only if the card is eligible for the dynamic currency conversion (DCC) service and if the buyer has chosen to pay in the currency of their card.
E.g.: "3, 5" for a margin rate of 3, 5%.
Format
dccRateDate
Path: transactionDetails.dcc.dccRateDate
Date and time, in UTC format, when the conversion rate was received from the dynamic currency conversion (DCC) service.
This field is populated only if the card is eligible for the dynamic currency conversion (DCC) service and if the buyer has chosen to pay in the currency of their card.
The conversion rate is returned in the dccChangeRate field.
Format
paymentReference
Path: transactionDetails.acquirerDetails.paymentReference
Payment reference that appears on the payment receipt.
Used in particular for the Multibanco payment method.
Format
serviceSupplier
Path: transactionDetails.acquirerDetails.serviceSupplier
Identifier of the entity for which the payment is made.
Used in particular for the Multibanco payment method.
Format
nsu
Path: transactionDetails.nsu
Unique sequence number (Latin America).
Format
tid
Path: transactionDetails.tid
Terminal ID POS identifier defined within the acceptance contract.
This field is only used in Colombia for choosing between REDEBAN and CREDIBANCO.
Format
acquirerNetwork
Path: transactionDetails.acquirerNetwork
Acquirer network code.
Possible values:
Network code | Label |
---|---|
ACCORD | Accord brand card |
ACCORD_SANDBOX | Accord brand card - Sandbox mode |
AMEXGLOBAL | American Express International |
AURORE | Cetelem - Aurore and Cpay credit cards |
CB | Bank Card |
CONECS | Conecs |
CVCONNECT | Chèque-Vacances ANCV Connect |
EDENRED | Edenred Belgium |
FRANFINANCE | Franfinance |
FRANFINANCE_SB | Franfinance - Sandbox mode |
FULLCB | Cetelem - 3 or 4 fois Card Payment |
GATECONEX | Elavon Europe |
GICC_DINERS | Diners via Concardis, SIX or VR Pay |
GICC_MAESTRO | Maestro via Concardis, SIX or VR Pay |
GICC_MASTERCARD | Mastercard via Concardis, SIX or VR Pay |
GICC_VISA | Visa via Concardis, SIX or VR Pay |
JCB | JCB France and French Polynesia |
PPRO | PPRO |
ONEY_API | 3x 4x Oney Payment |
ONEY_API_SANDBOX | Oney 3x 4x payment - Sandbox mode |
PAYDIREKT_V2 | PayDirekt |
PAYLIB | Paylib |
PAYPAL | PayPal |
PAYPAL_SB | PayPal - Sandbox mode |
PLANET_DCC | Planet Payment |
POSTFINANCEV2 | PostFinance |
PRESTO | Cetelem - Presto online credit |
SEPA | SEPA DIRECT DEBIT |
Format
taxRefundAmount
Path: transactionDetails.taxRefundAmount
Used in Uruguay, this field corresponds to the amount of tax credit granted to the merchant for the transaction. The value is expressed in the smallest unit of a currency (cent for euro).
Example: 30050 for EUR 300.50.
Format
occurrenceType
Path: transactionDetails.occurrenceType
Allows to identify if the transaction is part of a series of payments (subscription or payment in installments).
Useful for accurately identifying the first payment in a series.
With the application of the Soft Decline, the payment gateway automatically makes a new payment attempt with 3D Secure authentication when possible. This changes the payment's sequence number. The sequenceNumber field no longer allows to easily identify the first payment in a series.
Possible values
Value | DESCRIPTION |
---|---|
RECURRENT_INITIAL | First payment of a series. |
RECURRENT_INTERMEDIAIRE | The umpteenth payment in a series. |
RECURRENT_FINAL | Last payment of a series. |
UNITAIRE | Single payment (instant payment). |