Are you looking for test card numbers?

Would you like to contact support?

Receipt requirements

Learn about Terminal API receipts.

Card schemes and transaction types such as Magstripe and MKE have very specific requirements on what should be included on a receipt. These requirements differ per scheme and country, and change from time to time. The good thing is that you don't have to worry about compliance if you use the receipts that Adyen generates. Our receipts include all necessary fields and nothing more. Also, we take care of all changes in requirements.


The supported card schemes have all certified the Adyen-generated receipts and occasionally verify them in a live store. If you override the receipts that the Adyen terminal or library provides to the POS with a POS implementation of your own, or validate values against a hard-coded list, it is your responsibility to ensure scheme requirements and all changes in requirements are met at all times.

To prevent non-compliance and avoidable chargebacks, we advise you to use the Adyen-generated receipts without alterations.

Receipt fields

A receipt consists of a subset of key-value pairs, generated dynamically based on transaction type, payment result (approved or declined), CVM, issuer country, country of your store, and payment method. This is the total collection of keys that can appear in receipts:

Key (POS) Description
header1 First header line as configured in your Customer Area.
header2 Second header line as configured in your Customer Area.
aac Decline cryptogram generated by the card.
accountType Bank account used for the authorisation. For example, chequing or savings account.
additionalEmvData Set of EMV details.
aid Application Identifier (the scheme product).
approved Final state for approved transactions.
refused Final state for declined transactions.
void Final state for transactions that were cancelled by the merchant, shopper, or terminal.
atc Application Transaction Counter.
authCode Authorisation code from the issuer.
authResponseCode Authorisation response code from the issuer.
buyerId Identification of the wallet used for authorization.
cardholderHeader Receipt type indicator. For example, ‘CARDHOLDER COPY’ (or the localized text).
cardType Terminal-determined value for the type of card.
cashbackAmount Amount to be provided to the shopper in cash.
charityAmount Amount donated to charity by the shopper.
cid Cryptogram Information Data.
cnpj Identification number issued for the National Registry of Legal Entities.
currentBalanceAmount Balance on the cardholder's bank account.
cvmRes When applicable, indicates the PIN has been verified.
dccexpl Explanation of the DCC process, for shopper consent.
dccmarkup Markup on the sourced exchange rate for DCC.
dccrate Exchange rate used to calculate the DCC conversion (including markup).
dccshopperamount Amount after DCC conversion was applied.
dccsource Source of the base exchange rate (proxied by Adyen, excluding markup).
discountAmount Discount applied by the merchant.
expiryDate Expiry date of the card.
filler Generic filler to create blocks of elements that go together.
gratuityAmount Amount for gratuity.
mid Merchant Identification.
mref Merchant-determined reference for the transaction.
originalAmount Starting amount of the transaction prior to gratuity, adjustments, and such.
pan The last four digits of the masked PAN.
panSeq PAN sequence number or sequence number of the issued card.
paymentMethod Payment method on the brand or scheme level, as provided by Adyen. For example, visa, maestro.
paymentMethodVariant Payment method on the product level, as provided by Adyen. For example, visastandarddebit, vpay.
posEntryMode Method of obtaining the PAN, such as ICC, NFC, MSR, or MKE.
preferredName Issuer-determined label for the application on the card.
productType Product used for paying, such as Credit or Debit.
ptid Hardware (terminal) identifier sent to the schemes.
retain Retention message.
rrn Retrieval Reference Number.
tid Adyen terminal identifier.
tokenTxVariant Description of the token variant, such as ApplePay or SamsungPay.
totalAmount Total amount to be debited or credited.
txdate Terminal date of the transaction, in the local time zone.
txRef Reference for the transaction, provided by the merchant.
txtime Terminal time of the transaction, in the local time zone.
txtype Transaction type: GOODS_SERVICES, REFUND, and so on.
walletDccAmount Amount after DCC was applied by the scheme.
walletDccRate Rate applied by the scheme to calculate DCC.
walletOperationType Similar to paymentMethod. For example, alipay or wechatpay.
walletTransactionReference Reference that the scheme assigned to the transaction.
sigline Line to indicate a signature needs to be placed above it.
signature Room for shopper signature on the merchant receipt.
merchantSigline Line for merchant signature on the shopper receipt.
thanks 'Thank you' message (or the localized text).
QRCode QR code value as configured in your Customer Area.

You can customize both header lines and the QR code of receipts in your Customer Area under Point of sale > Terminals.