FILTER BY TAG

EMV Tags Required for a Sale or Credit Request

The EMV tags listed in the table are required for
eftpos
sale or credit requests that include the
pointOfSaleInformation.emv.tags
REST API field. A tag requirement can be mandatory (
M
) or conditional (
C
). A conditional tag must be sent in the request when it is present in the card and terminal.
For information about supported EMV tags for responses, see EMV Tags Supported for a Sale or Credit Response. For an overview of supported payment services, see Supported Transactions Types and Integrations.
Required
eftpos
EMV Tags for a Sale or Credit Request
Tag ID
Tag Name
Tag Length (Characters)
Tag Requirement
Comment
82
Application Interchange Profile
2
M
84
Dedicated File Name
5-16
M
95
Terminal Verification Results
5
M
TVR might have changed in 0420. For example, issuer authentication failure.
9A
Transaction Date
3
M
9C
Transaction Type
1
M
5F2A
Transaction Currency Code
2
M
9F02
Amount, Authorized
6
M
  • Authorized amount of the transaction (excluding adjustments).
  • Used when calculating the cryptogram.
  • Value might not be the same value as shown in Field 4. For example, when the merchant or terminal applies a discount or surcharge before the online authorization request.
9F03
Amount, Cash Out
6
M
  • Must contain the cash component for sale (purchase) with cash-out and cash-out-only transactions at POS.
  • Contains zeros for sale transactions.
9F19
Token Requestor Id
6
C
Must be included, when present.
9F10
Issuer Application Data
Variable, up to 32
M
  • Contains proprietary application data for transmission to the issuer in an online transaction.
  • Examples of data included: key index value, cryptogram version.
9F1A
Terminal Country Code
2
M
9F26
Application Cryptogram
8
M
Cryptogram returned by the ICC in response of the
GENERATE AC
command.
9F27
Cryptogram Information Data
1
M
Indicates the type of cryptogram and the actions to be performed by the terminal.
9F33
Terminal Capabilities
3
C
Not present for in-app payments, otherwise mandatory.
9F34
CVM Results
3
C
Not present for in-app payments, otherwise mandatory.
9F35
Terminal Type
1
M
9F36
Application Transaction Counter
2
M
For multi-network cards, this information cannot not be shared by both scheme applets.
9F37
Unpredictable Number
4
M
  • Provides variability and uniqueness to the cryptogram.
  • Required for full transactions and contactless, magnetic-stripe transactions.
9F6E
Third Party Data
Variable, up to 32
C
Must be included, when present.
9F66
Terminal Transaction Qualifier
4
C
Must be included, when present. Used for consumer-device CVM processing.