Field 48: Additional Private Data

Format: LLLVAR…999

Description: This will be used to send requests and responses related to services not dealt with by other fields. This data element 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 48.

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

• TAG: This sub-field contains a 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: 2 bytes BCD (first nibble will be zero filled).

• 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: 1 byte BCD. (Tag 18 uses 2 bytes BCD).

• 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 001 (Item Number)

In a Single Message configuration, Tag 001 (Item Number) will increase in value incrementally from 000 to 999 with each approved transaction in a given batch. Once the maximum value of 999 is reached the batch must be closed resulting in the batch number increasing by 1 and the Item Number reverting to 000.

The Item Number should be set to 000 for the first item in a batch.

The Elavon host will return the Item Number value in the appropriate 1110, 1210, 1230 or 1430 response message. The POS device or partner host system should supply this value in Field 48 of the next transaction in order to confirm that it received the previous response.

Dual message solutions should default this field to 001.

Tag 002 (Elavon STAN)

The Elavon STAN will be returned to the POS or partner host system in the event of an approval of a sale transaction. This data must be provided to the Elavon host in the event of a reversal of the aforementioned sale transaction. This sub-field must be populated irrespective of whether single or dual message processing is used.

Tag 003 (Elavon Date and Time)

The Elavon Date and Time will be returned to the POS or partner host system in the event of an approval of a sale transaction. This data must be provided to the Elavon host in the event of a reversal of the aforementioned sale transaction. This sub-field must be populated irrespective of whether single or dual message processing is used. In the event of a Time-Out the date and time of the original transaction being reversed must be used.

Tag 004 (Elavon RRN)

The Elavon RRN value will be returned to the POS or partner host system in the event of an approval of a sale transaction. This data must be provided to the Elavon host in the event of a reversal of the aforementioned sale transaction. This sub-field must be populated irrespective of whether single or dual message processing is used.

Tag 005 (Elavon Void Item Number)

The Elavon Void Item number will only be populated in single message operation. The Elavon Void Item number must be provided to the Elavon host in the event of the reversal of a previously authorised sale (1200), refund or force (1220) transaction.

See section 4: Important Message Fields, Additional Private Data – Field 48 for more information on the use of these Tags.

Tag 017 (Forex Generic Info) / Tag 018 (Forex Data)

Tags relates to foreign exchange rate data. Each will contain subfields constructed as follows:

Note: As per Numeric encoding, if the length of tag is an odd number, leading zero is added in the left nibble of the first byte of the right-justified tag data.