Requirements
Adyen provides certified receipts that are as short as possible while still meeting scheme requirements. For custom receipts, take care to include all data elements required by certification. Any issues that arise from not including these required data elements are at your own liability.
Card schemes have very specific requirements on what should be included on a receipt. These requirements differ per scheme and country/region, and can change. Receipts generated by Adyen have been certified as compliant by the card schemes that we support.
Card schemes will occasionally visit live stores to verify that receipts being generated are fully-compliant.
To prevent non-compliance and avoidable chargebacks, we strongly recommend using the Adyen-generated receipts without alterations. If you override this receipt data, or validate values against a hard-coded list, it is your responsibility to ensure that scheme requirements are met at all times.
Callback
| Name | Description |
|---|---|
|
|
Returns the receipt for printing, and requests that the POS confirms it has received the receipt. |
String values communicated to (and from) the cash register (whether from the terminal or not) should be in UTF-8 format.
Parameters
Name | Type | Description |
|---|---|---|
|
|
PED object that represents the terminal. | |
|
|
The tender associated with the additional data. | |
|
|
Passes receipts to the cash register. Its structure is formatted for printing. |
Confirmation Method
| Name | Description |
|---|---|
|
|
Confirms that the receipt is received by the POS. Print receipts after the POS completed the transaction. |
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
printed |
int |  |
Returns the result of printing, as the cash register must confirm printing of receipts. |
Confirming whether the receipt has been printed is a mandatory step. The cash register must confirm this to the library and the PED to complete the tender.