Field 63: Reserved Private Data III

1.1.1Tag 01 DUKPT Key Serial Number

Contains the Key Serial Number (KSN) for DUKPT encryption that is associated with the PIN data contained in Field 52. The Key Serial Number is a 10 byte composite field that is transmitted as 20 bytes as it contains binary data. The 10 bytes before they are expanded to ASCII character representation are composed as follows:

Bytes	Description	Bits
Bytes 1-2	Hexadecimal F’s	16
Bytes 3-5	Base Derivation Key ID	24
Bytes 6-7 + byte 8, bits 1-3	Terminal Device ID	19
Byte 8, bits 4-8 + bytes 9-10	Encryption Counter	21

 

1.1.2Tag 02 Card Verification Value (CVV2/CVC2)

CVV2 value as printed on the card. Mastercard and Visa: 3 bytes, left justified, space filled. American Express: 4 bytes.

1.1.3Tag 03 Card Verification Value (CVV2/CVC2) Result Code

The result of CVV2 validation:

Value	Description
M	Match
N	No Match
P	Not Processed
U	Not Participating
S	CVV2 Should Be Present – indicates that Visa or the issuer was not able to perform CVV2 verification, and notifies the merchant that the card should contain a CVV2 value.

 

American Express Values:

Value	Description
Y	Match
N	No Match
U	Unchecked

 

1.1.4Tag 04 Mail Order/Telephone Order/Ecommerce Indicator (MOTO/ECI)

 

Value	Description
0	Cardholder Present
1	Mail Order/Telephone Order (MOTO) Transaction
2	Recurring Transaction
3	Instalment Payment (not currently supported)
5	Ecommerce Fully Authenticated 3D Secure Transaction (see also Field 63, Tags 11, 12 and 13)
6	Ecommerce 3D Secure Authentication Attempt supported by merchant / cardholder does not participate (see also Field 63, Tags 11, 12 and 13)
7	Ecommerce Unsecure Transaction using SSL or Channel Encryption
9	UnionPay 3D Secure attempted. Transaction not authenticated as card is not registered for 3DS. Applicable for UnionPay cards only.

1.1.5Tag 05 Ignore TID Indicator

Field 41 (Card Acceptor Terminal Identification) value will not be validated by the Elavon host allowing non-Elavon supplied TIDs to be used. The value in Field 41 will be passed to the schemes and included in the Response message unless Field 63, Tag 20 (Alphanumeric TID) is populated.

Only available for approved customers in the Nordic region and approved users of alphanumeric terminal IDs. Not supported for Host Based solutions.

Y = Customer is approved to utilise Ignore TID functionality.

1.1.6Tag 06 Mobile POS (MPOS) Indicator

Indicates that the point of acceptance is a mobile device or tablet computer.

M = Mobile device used

1.1.7Tag 07 Payment Facilitator Indicator

Indicates Payment Facilitator acceptance. If present Field 43 Payment Facilitator values must be populated.

Y = Payment Facilitator

1.1.8Tag 08 Partial Approval Indicator

Specifies whether a terminal supports partial approval.

The option of a partial approval must not be offered for an authorisation with cashback.

If the issuer grants a partial approval but this indicator was not set the terminal will receive a decline in the response message. The Elavon acquiring host will generate a reversal to the issuer.

Y = Supports Partial Approval responses

1.1.9Tag 09 Address Verification Service (AVS) Request Data

Contains address data of the Cardholder.

Format 1:

Position	Type	Description
1-9	an 9	Subfield contains only numerics from the postcode.
10-49	ans 40	Subfield contains up to 5 numerics from the cardholder’s billing address.

 

Format 2:

Position	Type	Description
1-9	an 9	Subfield contains complete postcode.
10-49	ans 40	Subfield contains cardholder billing address.

 

Format 1 Examples	Pos	Value
Flat. 4a 123 London Road, London CH48 8AQ	1-9	488
	10-49	4123
1 Elm Street Valley Stream NY 1151	1-9	1151
	10-49	1
Spachbrücker Str 21, 64354 Reinheim	1-9	64354
	10-49	21
The Ridings Dean Court, Guildford GU14 7SR	1-9	147
	10-49

1.1.10Tag 10 Address Verification Service (AVS) Response Data

AVS result code.

Value	Description
A	Address match, Postal Code no-match
B	Street Address match, Postal Code not verified (incompatible format)
C	Street Address and Postal Code not verified (incompatible format)
D	Street Address and Postal Code match
F	Street Address and Postal Code match (UK issued cards)
G	Address information not verified
I	Address information not verified
M	Street Address and Postal Code match
N	No match
P	Postal Code match, Street Address not verified (incompatible format)
R	Retry - system unavailable/timed-out
S	Not applicable / AVS not supported
U	Address information not verified / No data from issuer
W	Postal Code match, Street Address no-match
X	Street Address and Postal Code Match
Y	Street Address and Postal Code Match
Z	Postal Code/ZIP Code match, Street Address no-match

 

1.1.11Tag 11 Transaction Identifier (XID)

3D Secure Transaction Identifier

20 bytes binary.

Transaction	Contents
Visa 3D Secure Version 1 (Verified by Visa)	Transaction XID
Visa 3D Secure Version 1 (Verified by Visa) Tokenised	Token Authentication Verification Value (TAVV)
American Express 3D Secure Version 1 (SafeKey)	Transaction XID
American Express 3D Secure Version 2	Directory Server (DS) Transaction ID

1.1.12Tag 12 3D Secure Cardholder Authentication Verification Values

20 bytes binary (Hex).

Scheme	Contents
American Express Safe Key	AEVV
Diners ProtectBuy	CAVV
JCB J/Secure	CAVV
Mastercard SecureCode	Not Applicable
UnionPay	AV
Verified by Visa	CAVV

Tag must be present if Tag 04 is set as value 5 or 6.

If Cardholder Authentication Verification Value (CAVV) data is not present in Verified By Visa ecommerce transactions (PAN or Token), the transactions will be downgraded.

1.1.13Tag 13 Accountholder Authentication Value (AAV)

Mastercard Secure Code AAV value. Applicable for Mastercard and Maestro ecommerce transactions only. Elavon expects the AAV field to be populated with the Base 64 encoded authentication value. This Tag must be present if Tag 04 is set as value 5 or 6.

Please note: AAV value is not mandatory for tokenised transactions. This Tag must be preceded by Tag 04. Formally called Universal Cardholder Authentication Field (UCAF).

1.1.14Tag 14 Financial Institution Data

Required for UK Domestic Transactions under the following Merchant Category Codes.

MCC 6012 – Visa/Mastercard – Please see Debt Repayment Field

MCC 6050 - Mastercard

Position	Type	Data Description
1-8	an 8	Date of birth of primary recipient. Format: YYYYMMDD (year, month, date) Note: No default date is captured.
9-18	an 10	Partially masked PAN or account number of recipient. Card-to-Card Payments: First 6 and last 4 characters of recipient PAN (no spaces) Card-to-Non-Card Payments: Up to 10 characters of recipient account number details. If the account number is under 10 characters then the remaining field locations are populated with an asterisk (*).
19-24	an 6	First part of the post code (district) which UK acquirers are required to populate. E.g. postcode KA27 8AA becomes KA27. If the first part of the post code is only 2 characters then the remaining field locations must be left blank.
25-30	an 6	First 6 characters of the recipient’s surname. Only alphabetic characters to be used (Latin characters such as A, B, C or a, b, c etc.). If the surname is shorter than 6 characters then the remaining field locations are populated with an asterisk (*).

The data must be arranged in sequential order without special characters or delimiters to discern subsections.

Example 1: Customer with UK Address and surname longer than 6 characters. ‘_’ denotes a space.

Position	1-8	9-18	19-24	25-30
Value	19840501	1234569999	KA27__	Witwic

 

Example 2: Customer with bank account and surname shorter than 6 characters. ‘_’ denotes a space.

Position	1-8	9-18	19-24	25-30
Value	19870629	123456****	XX____	Fong**

1.1.15Tag 15 Card Scheme Data Acceptance Indicator

Flag in requests to indicate that Card Scheme Data can be received and processed on the partner's host or terminal. Not required in Reversal Requests where no Card Scheme Data will be returned in the response.

Please advise Elavon if Card Scheme Data cannot be supported.

Y = Card Scheme Data supported

Please note: the return of Card Scheme Data in Online Refund Responses is currently supported in the Elavon Certification Test Environment only.

1.1.16Tag 16 Card Scheme Data

Data will be returned to the partner host system or POS terminal in approved responses where Tag 15 in the corresponding request is set to Y. This is retain and return data for the various Reversal messages. Data must also be populated in the equivalent fields on the corresponding submission file if applicable. Card Scheme Data may be required for subsequent Merchant Initiated Transactions.

Please note: Mastercard declines will not contain Card Scheme Data.

Scheme	Pos. 1	Pos. 2-16	Pos. 17-20	Pos. 21-22
Visa	ACI value	Transaction ID	Validation Code	ALP/ Product ID
Mastercard	M	BankNet Ref. No.	BankNet Date	Spaces
Discover	D	NRID	Track Data Condition Code (please note: can be space filled)	Spaces
AMEX	A	Transaction ID	Spaces	Spaces

 

Scheme	Pos. 1	Pos. 2-7	Pos. 8-17	Pos. 18-20	Pos. 21–22
Union Pay	B	STAN	Date and Time	Settlement Date	Spaces

1.1.17Tag 17 Instalment Payment

Supports the transmission of Instalment payment data. The indicated transaction may be the first or a subsequent transaction. In all cases the initial transaction of such a series must be identified as an Instalment payment. Currently not supported by Elavon.

Pos.	Type	Description
1	an 12	Total Amount. Contains the payments total. Zero-filled, right-justified.
2	an 3	Currency Code. Contains the currency code of the payment submitted.
3	an 3	Number of Instalments. Contains the number of Instalment payments that will occur. Zero-filled, right-justified.
4	an 12	Amount of each Instalment. Contains the amount of each Instalment payment. Zero-filled, right-justified.
5	an 3	Instalment Payment Number. Contains the Instalment payment number. Zero-filled, right-justified.
6	an 1	Frequency of Instalments. Contains the frequency of the Instalment payments. Valid values are: W - Every Week B - Every 2 Weeks M - Every Month

 

1.1.18Tag 18 Unattended Acceptance Terminal Indicator (CAT Level)

Indicates the type of unattended terminal.

Value	Description
01	Automated dispensing machine with PIN. Online authorised. Examples: ATM Fuel Purchase with PIN
02	Self-service terminal. Examples: Fuel Purchase without PIN (No CVM), online authorised. Prepaid Card Purchase Video Rental
03	Limited amount terminal without PIN (No CVM). Offline. Examples: Road Toll Motion Picture Theatre Parking Garage Fee

 

1.1.19Tag 19 Dual Brand Override Indicator

Allows a Dual Branded UnionPay card (i.e. UnionPay/Visa) to be processed as UnionPay.

Note: The top 100 UnionPay Dual Brand BINs (list available from Elavon) are automatically processed as UnionPay regardless of the use of this Tag.

This Indicator allows BINs not on that list to also be processed as UnionPay. Any Dual Brand cards processed as UnionPay must be correctly flagged at Settlement.

Please contact Elavon for more information on UnionPay processing.

UP = Union Pay

1.1.20Tag 20 Alphanumeric Terminal ID

Populated when an Alphanumeric Terminal ID is used at the Point of Interaction. Tag is left-justified with trailing spaces.

Field 41 (Card Acceptor Terminal Identification) must be zero-filled when Tag 20 is populated.

Field 63, Tag 05 (Ignore TID Indicator) must be set to ‘Y’. Not supported for Host Based solutions. 

1.1.21Tag 21 MasterPass Enabled Merchant Flag

Indicates that the merchant is enabled to process via the MasterPass Wallet. This does not require that MasterPass Digital Wallet is present. Mastercard only.

Y = MasterPass supported

1.1.22Tag 22 Digital Wallet Data

 

Pos	Name	Description
1	Digital Wallet Type	V - Visa Checkout M - MasterPass
3-6	Digital Wallet Data	Visa Checkout Pos. Description 1-2 Additional Authorisation Method 3-4 Additional Authorisation Reason Code MasterPass Pos. Description 1-3 Wallet Identifier 101 - Remote eCommerce 102 - Remote NFC 4 Space-filled Please note: While values 101 and 102 were initially introduced, other values may be transmitted by MasterPass. Mastercard will not publish these values and as such, acquirer and processor systems should pass whatever value is provided by the MasterPass wallet unaltered in the transaction record.

1.1.23Tag 23 Accountholder Authentication Value (AAV) Collection Indicator

Contains the result of AAV validation. 

Value	Description
0	Merchant does not participate in AAV scheme
1	Merchant participates / Attempted AAV data is present
2	Merchant participates / AAV data is present
3	Maestro Basic Checkout
5	Issuer Risk Based Decisioning
6	Merchant Risk Based Decisioning
7	Partial Shipment/Recurring Payment. Liability dependent on original AAV provided and matching initial transaction.

 

1.1.24Tag 24 Mastercard Assigned ID

Contains the Mastercard Assigned Merchant ID. This field is required if the AAV Collection Indicator Field contains the value 3 (Maestro Basic Checkout).

1.1.25Tag 25 Unique Transaction Response Reference Number

Contains a unique Elavon generated reference number populated in response messages only. This value should subsequently be populated in settlement.

Please note: this tag should not be used in request messages.

 

1.1.26Tag 26 Payment Facilitator Additional Information

Contains additional information required for Payment Facilitators. Alphanumeric fields should be left-justified with trailing spaces. Numeric fields should be right-justified with leading zeros.

Position	Type	Description
1-14	an 14	PF Sub-Merchant ID (MID number of  sub-merchant) This should not match the value in Field 42 (Card Acceptor Merchant ID)
15-18	n 4	PF Sub-Merchant MCC (MCC of sub-merchant)
19-38	an 20	PF Phone Number (sub-merchant phone number) Amex Only
39-78	an 40	PF Email Address (sub-merchant email address) Amex Only
79-92	n 14	PF Tax ID (sub-merchant Tax ID) Space-Fill if not available

1.1.27Tag 27 DCC Reference Number

Unique DCC reference number assigned by the Elavon Host. Format = YYMMDDHHMMnnnn where nnnn is a random number generated by the Host. To be returned in all subsequent authorisation and settlement messages from the terminal to the Host.

1.1.28Tag 28 Transit Transaction Data

Carries data related to the processing of Transit Transactions. Available for the following Merchant Category Codes: 4111 / 4112 / 4131 / 4784.

Position	Type	Description
1-2	n2	Transit Transaction Type Indicator Value Description 01 Pre-Funded Cardholder purchases a value redeemable on future travel e.g. weekly or monthly pass. 02 Real-Time Authorised Cardholder taps and pays for travel fare each trip. An authorisation is obtained every time a cardholder uses their bank-issued device at the transit terminal. 03 Post-Authorised Aggregated Multiple trips/card taps are aggregated into a single transaction amount. Taps can be combined for up to 14 days from the first tap or up to the chargeback protection amount. Variable fare model. 04 Authorised Aggregated Split Clearing Only applicable for UK domestic transactions. Please advise Elavon if you wish to make use of this transaction type. 05 Other 06 Post-Authorised Aggregated Maestro Multiple trips/Maestro taps are aggregated into a single transaction amount. Variable fare model. 07 Debt Recovery Indicates that a transit transaction has previously been declined but cardholder was granted travel. The Debt Recovery is a resubmission of the declined transaction. 08 Amex Account Status Check Applicable for Amex Transit Transactions. Requests that the issuer confirms that account is valid. Message should be formatted as a standard auth request with a nominal transaction amount. 09 Amex Application Transaction Counter Synchronisation Request Applicable for Amex Transit Transactions. Alerts the issuer that a following Post-Authorised Aggregated Transaction may contain an out-of-sync ATC. Message should be formatted as a standard auth request with a nominal transaction amount.  10 Amex PAN Translation Request with Account Status Check Applicable for Amex Transit Transactions. Requests that the issuer returns tha card PAN and expiry date. This will be populated in Field 63 Tag 29 (PAN Association Data). Message should be formatted as a standard auth request with a nominal transaction amount. A request for PAN Translation will automatically include an Amex Account Status Check.
3-4	n2	Transportation Mode Indicator Value Description Value Description 00 Unknown 11 Rural Bus 01 Urban Bus 12 Express Commuter Train 02 Interurban Bus 13 Para Transit 03 Light Train Mass Transit 14 Self-Drive Vehicle 04 Train 15 Coach 05 Commuter Train 16 Locomotive 06 Waterborne Vehicle 17 Powered Motor Vehicle 07 Toll 18 Trailer 08 Parking 19 Regional Train 09 Taxi 20 InterCity 10 High-Speed Train 21 Funicular Train     22 Cable Car

 

For Visa Debt Recovery transactions, the below fields should be populated as follows:

• Field 22, Byte 1 (POS Terminal Capability) should be set to 0 (Unknown)
• Field 22, Byte 7 (POS Entry Mode) should be set to 1 (Manual, No Terminal)

1.1.29Tag 29 PAN Association Data

The PAN Association Data is returned in Response Messages for Transit Transactions for Mastercard and American Express as follows:

Mastercard: returned in all Transit Transaction Responses.

American Express: returned when the Auth Request as Field 63 Tag 28 set to 10 (Amex PAN Transalation Request).

Field carries the cardholder’s PAN which can be cross-referenced with the contactless PPAN used in the original contactless Transit taps and used for the purpose of Debt Recovery.

Position	Type	Description
1	an 1	Account Number Indicator. Valid values: A - American Express E - Mastercard - Embossed account number provided by Issuer L - Mastercard - Pay with Rewards Loyalty Program Operator (LPO) card M - Mastercard - Primary account number P - Mastercard - PayPass account number R - Mastercard - Pay with Rewards card V - Mastercard - Virtual card number
2-20	n 19	Account Number
20-24	n 4	Expiration Date YYMM
25-27	an 3	Product Code (See Appendix C) Space-Filled if not applicable e.g. Amex transactions.

1.1.30Tag 30 Credential on File Indicator

Indicates status of Credential on File transaction initiated by Merchant. Card Scheme Data from original authorisation must be present in message.

In the event of a Reversal the same Credential on File value used in the original authorisation must be populated. Diners supported from November 2020.

Value	Description
S	Storing Credential on File – valid for Visa and Mastercard Indicates that the Cardholder Initiated Transaction (CIT) is being processed with the intention of retaining the cardholder’s details.
U	Unscheduled Credential on File Transaction – valid for Visa, Diners and Amex Represents a Merchant Initiated Transaction (MIT) using a stored credential that does not occur on a scheduled or regularly occurring transaction date.
I	Instalment Transaction using Stored Credential – valid for Visa, Amex, Diners and Mastercard (not currently supported) Represents a cardholder agreement to allow a merchant to initiate one or more future transactions over a period for a single purchase of goods or services.
R	Recurring Transaction using Stored Credential – valid for Visa, Amex, Diners and Mastercard Represents a cardholder agreement to allow a merchant to initiate future transactions for the purchase of goods or services at regular fixed intervals.

1.1.31Tag 31 Merchant Initiated Transaction Indicator

Indicates reason for Merchant Initiated Transaction. Valid for Visa, Diners and Amex. Card Scheme Data from original authorisation must be present in message. Diners supported from November 2020.

Value	Description
01	Resubmission Allows a merchant to resubmit an authorisation that has been declined due to insufficient funds after delivery of goods or services. 14 day time limit.
02	Delayed Charge Allows a merchant to process a supplemental charge after original services and respective payment has been processed. 120 day time limit.
03	Reauthorisation Allows the processing of split or delayed ecommerce shipments. Allows the extension of authorisations relating to hotel stays, car rentals and cruise lines. 120 day time limit.
04	No-Show Allows a merchant to perform a No-Show transaction in accordance with the merchant’s cancellation policy.

 

1.1.32Tag 32 Debt Repayment Indicator

Indicates a Debt Repayment Instalment Transaction. Used in conjunction with MCC 6012 in the Financial Institution Data Field where applicable.

Required for authorisation and authorisation reversal.

Y = Debt Repayment Transaction

1.1.33Tag 33 Elavon Token

Used in Elavon Tokenised Transactions Carries the Tokenised Card Number in Authorisation Requests and Tokenisation Request Responses. Maximum length 19.

1.1.34Tag 34 Current Elavon Token Type

Used in Elavon Tokenised Transactions. Identifies the Elavon Token Type being used in the current transaction.

1.1.35Tag 35 Requested Elavon Token Type

Used in Elavon Tokenised Transactions. Requests a new Elavon Token Type. To be agreed with Elavon before use.

1.1.36Tag 36 Card Brand

Used in Elavon Tokenised Transactions. Identifies the Card Brand of a Tokenised PAN. Returned in Response Messages.

Value	Description	Value	Description
VI / VE / VD	Visa Credit / Electron / Debit	UD / UP	Union Pay
MC / MD	Mastercard Credit / Debit	JC	JCB
AX	American Express	4B	Spanish Domestic
DC	Diners	GC	Giftcard

 

1.1.37Tag 37 Elavon Token Original Presented Card PAN

Used in Elavon Tokenised Transactions. Carries the last four digits of the card PAN originally presented for Elavon Tokenisation in transaction response messages (excluding 1316 - Elavon Tokenisation Response). Must be printed on receipts/retained to match transaction records in the event of a dispute being raised.

1.1.38Tag 38 Payment Account Reference (PAR) Number

Carries a unique reference number assigned to a cardholder’s card PAN. This value remains constant across tokenised and non-tokenised transactions. The PAR provided by the scheme during authorisation and is returned to the terminal in the response message.

1.1.39Tag 39 3D Secure Version Number

Indicates if the transaction has been processed under 3D Secure Version 1 or Version 2 rules. Mandatory for all 3D Secure transactions.

Elavon currently supports 3D Secure Version 2 for Visa, Mastercard, and American Express.

Value	Description
1	3D Secure Version 1
2	3D Secure Version 2

 

1.1.40Tag 40 Directory Server (DS) Transaction ID

Carries the Directory Server (DS) Transaction ID generated during 3D Secure Version 2 authentication. Supported by Mastercard and UnionPay.

1.1.41Tag 41 Transaction Record of Charge (ROC) Value

Carries a unique value created by the terminal solution for an authorisation request. The value is returned unaltered in the authorisation response and used in any subsequent related transactions including settlement where applicable. This value will be fed to schemes/issuers as Record of Charge (ROC) value.

1.1.42Tag 42 Mobile POS (MPOS) Acceptance Device Indicator

Indicates if an MPOS device is Hardware or Software Based.

Value	Description
0	Hardware Based MPOS – dedicated MPOS terminal with dongle (with or without keypad)
1	Software Based MPOS – off the shelf mobile device

 

1.1.43Tag 43 Deferred Authorisation Indicator

Indicates when authorisation has been deferred i.e. due to technical issues that prevent a proper authorisation being obtained while the cardholder is present.

This indicator must be used for every deferred authorisation request.

Y = Deferred Authorisation

1.1.44Tag 44 Strong Customer Authentication (SCA) Status Indicator

Indicates POS capability in relation to SCA requirements.

Value	Response
1	Single-Tap Capable – indicates that the solution supports contactless with online PIN and can request SCA without requiring an additional tap.
2	Ecommerce Step-Up Capable – indicates that the solution is capable of stepping up a transaction from unsecured ecommerce to 3D Secure Version 2 authentication if requested by issuer.
3	Single-Tap Transaction with Duplicated Data – indicates in request messages that a contactless Online PIN transaction is being processed following a Single-Tap request using data from the original tap.

 

1.1.45Tag 45 Strong Customer Authentication (SCA) Exemption Indicator

Indicates that exemption from SCA is requested for the transaction.

Value	Response
3	Secure Corporate Payment (SCP) – supported for Mastercard, Visa, Diners, UnionPay, and Amex.
4	Transaction Risk Analysis (TRA) conducted by Approved Outsource – supported for Mastercard, Visa, Diners, and UnionPay.
5	Transaction Risk Analysis (TRA) conducted by Elavon Fraud Services – supported for Mastercard, Visa, Diners, and UnionPay.
7	Low Value Payment (LVP) – supported for Mastercard, Visa, Diners, and UnionPay.

1.1.46Tag 46 Multi-Currency Processing Transaction Indicator

Indicates that the transaction has been processed using Multi-Currency Processing (MCP). MCP allows merchants to offer local currency to international customers but receive a guaranteed settlement amount in their home currency of choice. Supported for Mastercard, Visa and Diners.

3 = MCP Transaction

Please note: Diners support is related to your funding method (i.e. Elavon or Diners funding). Please speak to your Elavon representative for further information.

1.1.47Tag 47 Elavon Journey ID

Unique ID number used to indicate cardholder authentication via Elavon services. Please contact Elavon for more information.

1.1.48Tag 48 In-App Digital Payment Cryptogram

Mastercard: carries the Token Authentication Verification Value (TAVV) from a Mastercard DSRP (In-App Ecommerce) transaction only when processed under the enhanced rules (Mastercard AN 2941). Tag is required in conjunction with Tag 49.

Value should be 20 bytes of Hex which is Base 64 encoded to 28 characters.

American Express In-App Ecommerce: carries Amex Token Data Block A.

1.1.49Tag 49 Remote Commerce Acceptor Identifier

Mastercard: Carries a unique identifier agreed by the Merchant with wallet providers. This value is validated during authorisation processing. Value can be a maximum of 105 characters in length, converted to Base 64 encoding bringing the value length to a maximum of 150 characters

1.1.50Tag 50 3D Secure Capability Indicator

Indicates the highest version of 3D Secure Version 2 / EMV 3D Secure supported by solution. Formatted as follows: X.X.X - e.g. 2.1.0

1.1.51Tag 51 Free Trial and Promotional Offer Indicator

Indicates that a transaction is being processed at the end of a free trial/promotional period. Only required for the first transaction following the trial/offer.

1 = Charge at end of Free Trial/Promotional Offer

1.1.52Tag 52 Source IP Address

Carries the original submitter's (payer's) source IP address. Value is alphanumeric and can be of variable length.

Example: IPv4 = 172.1.1.10 / IPv6 = 2001:0DB8:AC10:FE01:0000:0000:0000:0000

1.1.53Tag 53 Merchant Action Code

Tag carries additional guidance on what steps to take in the event of a decline. If the Tag is absent from the response message no Merchant Action Code is available.

Value	Response
01	Updated / Additional Information Needed Obtain new account information
02	Try Again Later
03	Do Not Try Again
04	Token Requirements Not Fulfilled For This Token Type
21	Payment Cancellation Do not resubmit transaction

1.1.54Tag 54 Visa Commercial Choice Agreement ID

Tag carries the Visa Agreement ID for Commercial Choice Program Users. Returned in Response Messages and must be populated at Settlement.

Supported for U.S. cards at participating U.S. region merchants.

Please note: supported from November/December 2021.