Receipt

Receipt requirements

Payment networks and other industry stakeholders have specific written requirements, recommendations, and guidelines upon which this document builds.

The conventions used in the table below are:

BR - Required by one or more global brands and therefore must be present on the receipt.

ER - Though not a mandate from one of the brands, Elavon requires this field on the receipt.

C - Identifies the field as conditionally required, depending on reasons that may or may not be identified in the table.

O - An optional field that can be present if desired by the vendor/client.

Field NameTagDescriptionApprovalDecline
POS Entry Mode9F39Used by POS to derive value/text on receipt that identities how card data was entered (i.e., via chip read successful, fallback to magnetic stripe, magnetic stripe).ERER
Application Cryptogram9F26Cryptogram returned by the ICC in response of the ‘Generate AC’ command. TC (Approval) or AAC (Decline).OO
CVM Results9F34Indicates the results of the CVM performed.OO
Issuer Application Data9F10Contains proprietary application data for transmission to the issuer in an online transaction.ERER
Terminal Verification Results95Status of different functions/test as seen from the terminal. A set of indicators which determine the decision of offline and online processing for an EMV transaction.ERER
Terminal Country Code9F1AIndicates the country of the terminal.OO
PAN Sequence Number5F34Identifies and differentiates cards with the same PAN.OO
Application Interchange Profile82Indicates the capabilities of the card to support specific functions in the application.OO
Application Transaction Counter9F36Counter maintained by the application in the ICC (incrementing the ATC is managed by ICC).OO
Cryptogram Information Data9F27Indicates the type of cryptogram and actions to be performed by the terminal.OO
Unpredictable Number9F37Value to provide variability and uniqueness to the generation of a cryptogram.OO
Application Identifier4FICC AID - Identifies the application as described in ISO/IEC 7816-5.BRBR
Dedicated File Name84Identifies the name of the Dedicated File as described in ISO 7816-4. This field can be used to retrieve the AID when Tag 4F is not present.CC
Application Preferred Name9F12Preferred mnemonic associated with the AID. The payment application ensures the proper decoding from the Issuer Table Index before sending to the POS.BRBR
Application Label50Mnemonic associated with the AID according to ISO/IEC 7816-5. Required if Application Preferred Name is not available.CC
Issuer Action Code - Default9F0DSpecifies the issuer’s conditions that cause a transaction to be rejected if it might have been approved online, but the terminal is unable to process the transaction online.OO
Issuer Action Code - Denial9F0ESpecifies the issuer’s conditions that cause the denial of a transaction without attempt to go online.OO
Issuer Action Code - Online9F0FSpecifies the issuer’s conditions that cause a transaction to go online.OO
Transaction Status Indicator9BTSI - Indicates the functions performed in a transaction.ERER
Terminal Action Code - DefaultNo TagSpecifies the acquirer’s conditions that cause the denial of a transaction without attempt to go online.OO
Terminal Action Code - DenialNo TagSpecifies the acquirer’s conditions that cause the denial of a transaction without attempt to go online.OO
Terminal Action Code - OnlineNo TagSpecifies the acquirer’s conditions that cause a transaction to be transmitted online.OO
Transaction Currency Code5F2AIf not present on the receipt the transaction is assumed to take place in the currency that is legal tender at the POI.CC
Transaction Date9ADate of transaction.BRBR
Transaction Time9CTime of transaction.BRBR
Amount Authorized9F02The amount of the transaction sent to the issuer for authorization.BRBR
Other Amount9F03Other amounts that may be included in the Amount Authorized such as cashback amount.OO
Application Usage Control9F07EMV Tag that indicates the usage of the payment application.OO
Application Response Code8AAuthorization response code.BRBR
Application PAN5APayment account number (properly masked).BRBR
Cardholder Verification MethodNo TagPIN, SignatureBRBR
Authorization ModeNo TagIssuer, CardERER

important

Requirement

  • Elavon requires mandatory EMV fields to be present on the sales receipt for both approved and declined transactions. Having conditional or optional fields on the receipt is at the merchant’s discretion.

  • Elavon requires receipts to be provided for both approved and declined transactions.

Best Practice

  • Storing receipt data is not mandated by Elavon. If the merchant system choses to store receipt data, the storage duration is at the discretion of the merchant.

  • Elavon recommends to store the digital version of the receipt data for a minimum of 30 days.

EMV Receipt Examples

Purchase with PIN and signature not required:

Purchase with PIN and Sig not required

Declined transaction and purchase with fall back swipe:

Declined and Purchase with fall back swipe