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, 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.
Returns the receipt for printing, and requests that the POS confirms it has received the receipt. For example, an authorisation receipt which must be signed by the shopper.
Trigger this callback by creating a tender with the
Confirm the print receipt callback before the POS begins printing the receipt. This will prevent an approved transaction from being cancelled because of printer failure.
String values communicated to (and from) the cash register (whether from the terminal or not) should be in UTF-8 format.
||Object used to hold the tender attributes.|
Callback Response Attributes
||Adyen returns the
||Reference the PED provides for the transaction, used in reporting on the Adyen payments platform.|
||Transaction result details|
||Confirm that the receipt is received by the POS. Print receipts after the POS completed the transaction.|
||Tender||Use this as a key to confirm additional data.|
||boolean||If set to true, the PED continues to process the tender. If set to false, the PED cancels the tender.|
Determine the current and final tender state
Adyen provides a method to determine the current, or final, tender state. For more information, see Determine the current and final tender state - JNI.