Field 63: Reserved Private Data III

Format: LLLVARb…999

Description: Field 63 will be used to send requests and responses related to services not dealt with by other fields. This field utilises the Tag, Length, Value (TLV) structure to delineate different sub-elements in the following manner:

<LLL><TAG><LENGTH><VALUE><TAG><LENGTH><VALUE> ………

LLL: This describes the aggregate length of the data in data element 63.

Format: 2 bytes BCD (first nibble will be zero-filled).

TAG: This sub-field contains an alphanumeric or numeric value describing the data that is to follow in the length and value fields. The tag values and the actual data they represent are outlined in the table below.

Format: 1-byte BCD.

LENGTH: This sub-field contains a numeric value that may vary from 0 to 99 describing the length of the data that is to follow in the value sub-field.

Format: 2 bytes BCD (first nibble will be zero-filled).

VALUE: This sub-field contains the data associated with a particular tag. The length of this data should be the same as that indicated in the length sub-field.

Format: see table below for individual tag formats.

Tag

Description

Format

Length

01

DUKPT Key Serial Number

b 20

20

02

CVV2 (CVC2)

an 4

4

03

CVV2 (CVC2) Result Code

an 1

1

04

Moto/EC Indicator

n 1

1

05

Ignore TID Indicator

an 1

1

06

Mobile Acceptance Indicator

an 1

1

07

Payment Facilitator Indicator

an 1

1

08

Partial Approval Indicator

an 1

1

09

Address Verification Data

an 49

49

10

Address Verification Response Data

an 1

1

11

Transaction Identifier

an 20

20

12

3D Secure Cardholder Authentication Verification Value
(CAVV/AEVV)

an 20

20

13

Universal Cardholder Authentication Field

an 32

32

14

Financial Institution Data

an 30

30

15

Acceptance Indicator for Card Scheme Data

an 1

1

16

Card Scheme Data

an 22

22

17

Instalment Payment

an 34

34

18

Unattended Acceptance Terminal Indicator

(CAT – Cardholder Activated Terminal – Level Indicator)

an 2

2

19

Dual Brand Override Indicator

an 2

2

20

Alphanumeric Terminal ID

an 8

8

21

MasterPass Enabled Merchant Flag

an 1

1

22

Digital Wallet Data

an 5

5

23

Accountholder Authentication Value (AAV) Collection Indicator

n 1

1

24

MasterCard Assigned ID

an 6

6

25

Unique Transaction Response Reference Number

an 11

11

26

Payment Facilitator Additional Information

an 92

92

27

DCC Reference Number

n 14

14

28

Transit Transaction Data

n 4

4

29

PAN Association Data

an 27

27

30

Credential on File Indicator

an 1

1

31

Merchant Initiated Transaction Indicator

an 2

2

32

Debt Repayment Indicator

an 1

1

33

Reserved for Future Use

an 19

19

34

Reserved for Future Use

an 2

2

35

Reserved for Future Use

an 2

2

36

Reserved for Future Use

a 2

2

37

Reserved for Future Use

n 4

4

38

Payment Account Reference (PAR) Number

an 35

35

39

3D Secure Version Number

n 1

1

40

Directory Server (DS) Transaction ID

ans 36

36

41

Transaction Record of Charge (ROC) Value

an 39

39

42

Mobile POS (MPOS) Acceptance Device Indicator

n 1

1

Note: Support for Tag 16 (Card Scheme Data) and Tag 25 (Unique Transaction Reference Number) in Response Messages is mandatory.

Tag

Name

Description

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

1-2

Hexadeccimal F's

16

3-5

Base Derivation Key ID

24

6-7 +3 bits of byte 8

Terminal Device ID

19

Bits 4-8 of byte 8+ byte 9-10

Encryption Counter

21

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

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

 

American Express Values:

Value Description

Y

Match

N

No Match

U

Unchecked

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

05

IgnoreTID Indicator

Terminal ID will be ignored by Elavon Authorisation Host, but passed to schemes and included in Response Messages. Elavon Host will refer to the Elavon Merchant ID provided in the message. The Ignore Terminal ID Indicator is not compatible with Single Message (Host Based) configurations.

Value

Description

Y

Ignore Terminal ID. Terminal ID assigned by customer

06

Mobile Acceptance Indicator

This field indicates that the point of acceptance is a mobile device or tablet computer

Value

Description

M

Mobile Device Used

07

Payment Facilitator Indicator

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

Value

Description

Y

Payment Facilitator

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.

Value

Description

Y

Supports Partial Approval responses

09

Address Verification Service (AVS) Request Data

Contains address data of 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's billing address.

 

Postal Address

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

^..^

10

Address Verification Service (AVS) Response Data

AVS result code.

Value

Response

Description

N

No Match

Match is not exact. Post code and/or address do not match.

U

Unavailable

Address information is unavailable or Issuer does not support AVS.

Acquirer has re-presentment rights.

F

Exact Match

The match is exact. Both post code and address match.

No re-presentment rights.

11

Transaction Identifier (XID)

Verified by Visa XID value / America Express Safekey XID Value

Value will be received from the Merchant Plug-In (MPI) in BASE64. This should be converted to a HEX string. The first 20 characters of the HEX string should be used to populate this Tag.

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

Note: For tokenised Verified by Visa transactions, this field will carry the TAVV (Token Authentication Verification Value).

12

3D Secure Cardholder Authentication Verification Value (CAVV/AEVV)

Value will be received from the Merchant Plug-In (MPI) in Base64. This should be converted to Binary Code Decimal (BCD). The first 32 characters of this value should be used to populate this field.

Scheme

Contents

Verified by Visa

CAVV

American Express SafeKey

AEVV

Diners ProtectBuy

CAVV

MasterCard SecureCode

Not Applicable

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

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

13

Accountholder Authentication Value (AAV)

MasterCard Secure Code AAV value.

Value is received from the Merchant Plug-In (MPI) in BASE64. The first 28 characters of this BASE64 value should be used to populate this Field. This is applicable for MasterCard and Maestro ecommerce acceptance only.

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

Note: AAVvalue is not mandatory for tokenised transactions.

Formally called Universal Cardholder Authentication Field (UCAF).

14

Financial Institution Data

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

  • MCC 6012 – Visa/MasterCard – see Debt Repayment Field

  • MCC 6050 – MasterCard

Position

Type

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.

Example: Post code 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**

15

Card Scheme Data Acceptance Indicator

Flag in requests to indicate that Card Scheme Data can be received and processed on the partners host or terminal.

Advise Elavon if Card Scheme Data cannot be supported.

Value

Description

Y

Card Scheme Data Supported

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.

Visa

Position

1

2-16

17-20

21-22

Value

ACI Value

Transaction ID

Validation Code

ALP / Product ID

 

MasterCard

Position

1

2-16

17-20

21-22

Value

M

BankNet Ref. Nbr

BankNet Date

Spaces

 

Discover

Position

1

2-16

17-20

21-22

Value

D

NRD

Track Data Condition Code (LF-space-filled)

Spaces

 

AMEX

Position

1

2-16

17-20

21-22

Value

A

Transaction ID

Spaces

Spaces

 

Union Pay

Position

1

2-17

8-17

18-20

21-22

Value

B

STAN

Date and Time

Settlement Date

Space-filled

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.

Position

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:

Value

Description

B

Bi-Weekly

M

Monthly

W

Weekly

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

19

Dual Brand Override Indicator

Denotes the brand selected by the customer at the Point of Interaction. Only applies to dual branded cards. Only supported for Union Pay cards at present.

Value

Description

UP

Union Pay

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.Alphanumeric Terminal IDs are not compatible with Single Message (Host Based) configurations.

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.

Value

Description

Y

MasterPass supported

22

Digital Wallet Data

Position

Name

Description

1

Digital Wallet Type

Value

Description

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

 

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.

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

MasterPass Only: Maestro Basic Checkout

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).

25

Unique Transaction Response Reference Number

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

Note: This tag should not be used in request messages.

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.

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.

28

Transit Transaction Data

Position

Type

Description

1-2

n 2

TransitTransaction Type Indicator

Value

Description

01

Pre-Funded

02

Real-Time Authorised

03

Post-Authorised Aggregated

04

Authorised Aggregated Split Clearing

05

Other

06

Post-Authorised Aggregated Maestro

07

Debt Recovery

3-4

n2

Transportation Mode Indicator

Value

Description

00

Unknown

01

Urban Bus

02

Interurban Bus

03

Light Train Mass Transit

04

Train

05

Commuter Train

06

Waterborne Vehicle

07

Toll

08

Parking

09

Taxi

10

High Speed Train

11

Rural Bus

12

Express Commuter Train

13

Para Transit

14

Self-Drive Vehicle

15

Coach

16

Locomotive

17

Powered Motor Vehicle

18

Trailer

19

Regional Train

20

InterCity

21

Funicular Train

22

Cable Car

29

PAN Association Data

PAN Association Data provided as part of a Transit Transaction.

Position

Type

Description

1

an 1

Account Number Indicator

Value

Description

E

Embossed account number provided by Issuer

L

Pay with Rewards Loyalty Program Operator (LPO) card

M

Primary Account Number

P

PayPass Account Number

R

Pay with Rewards Card

V

Virtual Card Number

2-20

n 19

Account Number.

20-24

n 4

Expiration Date.

Format: YYMM

25-27

an 3

Product Code (see Appendix C).

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.

If the transaction is initiated by the cardholder (Cardholder Initiated Transaction (CIT)) then Field 22 (POS Data Code), Byte 7 (Card Data Input Mode) will be set to A (Credential on File) but this Field is not required.

In the event of a Reversal the same Credential on File value used in the original authorisation must be populated.

Value

Description

S

Storing Credential on File

Valid for Visa and MasterCard.

Indicates that the transaction is being processed with the intention of retaining the cardholder’s details for future Recurring, Instalment or Unscheduled transactions.

U

Unscheduled Credential on File

Only valid for Visa.

Represents a transaction 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 and MasterCard.

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 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.

31

Merchant Initiated Transaction Indicator

Indicates reason for Merchant Initiated Transaction. Card Scheme Data from original authorisation must be present in message. Only valid for Visa.

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.

32

Debt Repayment Indicator

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

Field 60 (Reserved Private Data III), Tag 04 (Mail Order/Telephone Order/Ecommerce Indicator) must equal 1 (Mail/Telephone Order) or 2 (Recurring) or 3 (Instalment).

Required for authorisation and authorisation reversal.

Value

Description

Y

Debit Replayment Transaction

33

Reserved for Future Use

Reserved for Future Use

34

Reserved for Future Use

Reserved for Future Use

35

Reserved for Future Use

Reserved for Future Use

36

Reserved for Future Use

Reserved for Future Use

37

Reserved for Future Use

Reserved for Future Use

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.

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.

Value

Description

1

3D Secure Version 1

2

3D Secure Version 2

40

Directory Server (DS) Transaction ID

Carries the Directory Server (DS) Transaction ID generated during 3D Secure Version 2 authentication. Must be present for all MasterCard 3D Secure Version 2 transactions.

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.

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