Certification : Transaction Receipts

Certification : Transaction Receipts

Transaction Receipts

Mandatory certification requirements for merchants who generate their own transaction receipts — from their own cash register software, or from a payment terminal without an integrated printer (e.g. the PAX A35 or IM30) — covering required fields, signature-line logic, and disclaimer text.

Version: v1.0   |  Last updated: 2026-07-03 

❓

  Introduction

This topic is intended to help with the mandatory certification of transaction receipts if the merchant chooses to generate their own receipt from their cash register software, or if they are using a payment terminal without an integrated printer (for example, the PAX A35 or IM30).

📋

  Required Information on Transaction Receipt

⚠️

Important

To respect PCI Data Security Standards, the expiry date MUST NEVER appear on transaction receipts.

The following table outlines the information that must appear on the transaction receipt:

Name Parameter Description
Account type accountType Debit transactions only. Chequing or Savings.
Application Identifier (AID) emvAID Identifies the EMV application (EMV transactions only). E.g. AID: A000000277
Approval/Decline Indication receiptDisp Response code and text.
Authorization Number authorizationNumber Approved transactions only.
Card Number cardNumber Do NOT show the complete card number, per PCI security standards. Display the masked card number and last 4 digits only.
Transaction or Card Type trxType / cardType D for debit transactions; C for credit transactions.
Cash Back Amount * cashbackAmount Shown separately, but included in the final total amount.
Cryptogram Type and Info emvTC EMV transactions only. E.g. TC: A2E51243D4C7E551 / AAC: A2E51243D4C7E551
Date and Time trxDate / trxTime The date MUST be YYYY/MM/DD. The time MUST be in 24-hour format. E.g. 2010/08/25 16:08:45
Entry Method trxMethod M = manual, S = swipe, C = chip, T = tap (contactless).
Final Amount amount Total amount of the transaction being settled by the card; includes all amounts.
Host Timestamp timeStamp Must be written on the invoice. E.g. TS: 20110825160912. For offline transactions, the Host Timestamp should be set to all zeroes.
Invoice Number invoiceNumber / terminalInvoiceNumber Transaction identifier / terminal transaction identifier.
Merchant Name and Address Determined by merchant Legal name and address.
Extra Receipt Display Determined by merchant Extra receipt display.
Sequence Number sequenceNumber Sequence number associated with the transaction. For offline transactions, the Sequence Number should be set to all zeroes.
Surcharge Amount * surchargeAmount Shown separately (but included in the final total amount).
Terminal ID bankTerminalNumber PayFacto 8-digit Terminal ID.
Tip Amount * tipAmount Shown separately (but included in the final total amount).
Transaction Amount [CONFIRM] Shown separately (but included in the final total amount).
Transaction Type As per web service call E.g. Purchase, Return, etc.
Transaction Status Information (TSI) emvTSI Indicates the functions performed in a transaction. E.g. TSI: F800
Batch batchNumber 4 numeric characters corresponding to the batch number.

* For Cash Back Amount, Surcharge Amount, and Tip Amount: include only if the merchant includes them as part of the transaction.

🚧

Source Gaps Flagged

Two rows don't follow the table's usual Name/Parameter/Description pattern: Transaction Amount has no parameter name given (reproduced as [CONFIRM]), and Transaction Type's "Parameter" column contains the phrase "As per web service call" rather than an actual field name. Both reproduced verbatim. [CONFIRM: correct parameter names for these two rows]

✍️

  Signature Line on the Transaction Receipt

To determine whether the client's signature is required on the receipt, perform the following validations:

1

Was the transaction approved?

Validate the return code in the transactionOutput of the call.

Yes: the transaction is approved (returnCode = 00) → continue to point 2.

No: the transaction is declined → no signature is required.

2

Was a value received for the CVMResult parameter?

Check the CVMResult parameter in the transactionOutput of the call. There are 3 possible responses:

Yes: there is a value for CVMResult → continue to point 3.

No: the value is blank or NULL → signature is required (also applicable for entry method Manual or Swipe).

No: the value is blank or NULL → signature is not required — applicable only to Visa contactless.

🚧

Source Inconsistency Flagged

Point 2 gives two contradictory "No" outcomes for the same condition (a blank/NULL CVMResult) — one says signature required, the other says not required — distinguished only by an entry-method qualifier folded into each answer rather than being split into separate branches. Reproduced verbatim. [CONFIRM: please restructure or clarify the condition that separates these two cases]

3

What are the first 2 characters of the CVMResult value received?

First 2 Characters Signature Required?
03 Yes
05 Yes
43 Yes
45 Yes
1E Yes
5E Yes
Any other value No
📜

  Transaction Receipt Disclaimer Text

A disclaimer must appear on the transaction receipt if a signature line is generated. Disclaimer language is defined according to merchant preferences. The disclaimer must appear on the merchant copy, above the signature line.

🇬🇧

English

"I, THE CARDHOLDER, AGREE TO PAY THE ABOVE TOTAL AMOUNT ACCORDING TO THE CARDHOLDER AGREEMENT"

🇫🇷

French

« J'ACCEPTE DE PAYER LE MONTANT CI-DESSUS, SELON LA CONVENTION DE L'ÉMETTEUR DE LA CARTE »

🖼️

  Transaction Receipt Examples

Financial Transactions





  Sample English Receipt


Sample French Receipt

DataCandy Transactions


Sample English Receipt


Sample French Receipt