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 Name Tag Description Approval Decline
POS Entry Mode 9F39 Used 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). ER ER
Application Cryptogram 9F26 Cryptogram returned by the ICC in response of the 'Generate AC' command. TC (Approval) or AAC (Decline). O O
CVM Results 9F34 Indicates the results of the CVM performed. O O
Issuer Application Data 9F10 Contains proprietary application data for transmission to the issuer in an online transaction. ER ER
Terminal Verification Results 95 Status 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. ER ER
Terminal Country Code 9F1A Indicates the country of the terminal. O O
PAN Sequence Number 5F34 Identifies and differentiates cards with the same PAN. O O
Application Interchange Profile 82 Indicates the capabilities of the card to support specific functions in the application. O O
Application Transaction Counter 9F36 Counter maintained by the application in the ICC (incrementing the ATC is managed by ICC). O O
Cryptogram Information Data 9F27 Indicates the type of cryptogram and actions to be performed by the terminal. O O
Unpredictable Number 9F37 Value to provide variability and uniqueness to the generation of a cryptogram. O O
Application Identifier 4F ICC AID - Identifies the application as described in ISO/IEC 7816-5. BR BR
Dedicated File Name 84 Identifies 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. C C
Application Preferred Name 9F12 Preferred mnemonic associated with the AID. The payment application ensures the proper decoding from the Issuer Table Index before sending to the POS. BR BR
Application Label 50 Mnemonic associated with the AID according to ISO/IEC 7816-5. Required if Application Preferred Name is not available. C C
Issuer Action Code - Default 9F0D Specifies 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. O O
Issuer Action Code - Denial 9F0E Specifies the issuer's conditions that cause the denial of a transaction without attempt to go online. O O
Issuer Action Code - Online 9F0F Specifies the issuer's conditions that cause a transaction to go online. O O
Transaction Status Indicator 9B TSI - Indicates the functions performed in a transaction. ER ER
Terminal Action Code - Default No Tag Specifies the acquirer's conditions that cause the denial of a transaction without attempt to go online. O O
Terminal Action Code - Denial No Tag Specifies the acquirer's conditions that cause the denial of a transaction without attempt to go online. O O
Terminal Action Code - Online No Tag Specifies the acquirer's conditions that cause a transaction to be transmitted online. O O
Transaction Currency Code 5F2A If not present on the receipt the transaction is assumed to take place in the currency that is legal tender at the POI. C C
Transaction Date 9A Date of transaction. BR BR
Transaction Time 9C Time of transaction. BR BR
Amount Authorized 9F02 The amount of the transaction sent to the issuer for authorization. BR BR
Other Amount 9F03 Other amounts that may be included in the Amount Authorized such as cashback amount. O O
Application Usage Control 9F07 EMV Tag that indicates the usage of the payment application. O O
Application Response Code 8A Authorization response code. BR BR
Application PAN 5A Payment account number (properly masked). BR BR
Cardholder Verification Method No Tag PIN, Signature BR BR
Authorization Mode No Tag Issuer, Card ER ER

error_outline
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 Sig not required

Declined and Purchase with fall back swipe