Learn how to generate compliant transaction receipts.
The POS+ system provides comprehensive receipt printing functionality for all transaction types. Receipts serve as a physical record of transactions and include different information for merchant and customer copies, in accordance with card scheme rules and data protection requirements.
When Dynamic Currency Conversion (DCC) is used, receipts include additional information to ensure full transparency about the currency conversion applied to the transaction.
A receipt includes the following standard sections:
- Header information
- Transaction information
- Card details
- Method and type
- Amount information
- DCC information (when applicable)
- Verification information
- Authorisation information
- Technical details
- Footer
| Information | Description | Parameter |
|---|---|---|
| Receipt type identifier | Whether the receipt is a merchant copy or customer copy. | N/A |
| Merchant's physical address | The street, city, postal code, and country of the merchant. | N/A |
| Information | Description | Parameter |
|---|---|---|
| Transaction reference number | The reference number for the transaction. | merchantTransactionId |
| Merchant ID | Your merchant ID. This should be masked in the customer copy. | providerResponse.merchantId |
| Terminal ID | The ID of the point-of-sale device. This should be masked in the customer copy. | providerResponse.terminalId |
| Information | Description | Parameter |
|---|---|---|
| Card scheme | The card's scheme. | fundingData.cardScheme |
| Application Identifier (AID) | The unique identifier for the application used during the EMV transaction. | fundingData.emvDataResponse.applicationId |
| Application label | The label or name of the application selected for the transaction, typically representing the card brand. | fundingData.emvDataResponse.applicationLabel |
| Masked PAN | The partially masked version of the Primary Account Number. | fundingData.maskedPrimaryAccountNumber |
| Card sequence number | The sequence number for the card used in this transaction. Sequence numbers differentiate cards with the same Primary Account Number (PAN) issued to the same account holder. | fundingData.emvDataResponse.panSequenceNumber |
| Expiry date | The card's expiry date. This should be masked in the customer copy. | fundingData.expiryMonth and fundingData.expiryYear |
| Information | Description | Parameter |
|---|---|---|
| Entry method | How the card was processed. | N/A |
| Transaction type | The type of transaction. | transactionMethod.intent |
| Information | Description | Parameter |
|---|---|---|
| Transaction amount | The amount of the transaction. | amounts.transaction |
When a customer selects Dynamic Currency Conversion (DCC) for their transaction, additional information must be included on the receipt to comply with card scheme rules and provide full transparency to the cardholder.
DCC information only appears on receipts where the customer has actively selected to pay in their home currency. If the customer declines DCC and pays in the merchant's local currency, these fields are not included.
| Information | Description | Parameter |
|---|---|---|
| Cardholder currency | The currency of the customer's card (their home currency). | dccData.amounts.cardholder.currencyCode |
| Cardholder currency amount | The total transaction amount in the customer's home currency. | dccData.amounts.cardholder.transaction |
| Merchant currency | The local currency of the merchant. | dccData.amounts.local.currencyCode |
| Merchant currency amount | The original transaction amount in the merchant's local currency. | dccData.amounts.local.transaction |
| Exchange rate | The conversion rate applied to convert from merchant currency to cardholder currency. | dccData.exchangeRate |
| Markup rate | The markup rate applied by the rate provider on top of the base exchange rate. | dccData.markupRate |
| Rate provider | The name of the foreign exchange rate provider (such as Fexco, Elavon, OpenFX, or Global Blue). | dccData.providerData.provider |
| DCC disclosure statement | A statement confirming that the customer chose to pay in their home currency and that no further conversion will occur. | dccData.disclaimer |
The receipt must clearly display both currency amounts to ensure the customer understands the conversion that has been applied. All DCC-related information must be presented in accordance with Visa and Mastercard Dynamic Currency Conversion requirements.
Integrators should check the latest DCC scheme specifications to ensure receipts meet all current DCC receipt requirements. Scheme rules may be updated periodically.
| Information | Description | Parameter |
|---|---|---|
| Cardholder verification method used | The result of the Cardholder Verification Method (CVM) used in the transaction, such as PIN verification or signature. | fundingData.providerResponse.emvDataResponse.cardHolderVerificationMethodResults |
| PIN verified | If the CVM was Pin verified, include confirmation that the PIN was successfully verified. | N/A |
| Signature line | If the CVM was Signature verified, include the signature line. This only applies to the merchant copy. | N/A |
| Information | Description | Parameter |
|---|---|---|
| Authorisation code | The response code indicating the outcome of the authorisation request. | approvalCode |
| Transaction status | The status of the transaction. | state |
| Information | Description | Parameter |
|---|---|---|
| Transaction date and time | The date and time when the transaction occurred. | merchantTransactionDate |
The system supports different receipt formats for various transaction types:
- Initial transaction receipts: standard purchase receipts, authorisation receipts, and standalone refund receipts.
- Modification transaction receipts: capture receipts, void receipts, and incremental authorisation receipts.
- DCC transaction receipts: receipts where the customer selected Dynamic Currency Conversion, displaying amounts in both merchant and cardholder currencies along with exchange rate and markup information.
- Special condition receipts: declined transaction receipts, and store and forward receipts (offline mode).