FirstData Nashville Token Transaction UML

Represents tokenization transaction as it is defined in FirstData Nashville's tokenization specification.

Identification number of the application used.

A system-generated number provided by the merchant, the System Trace Number uniquely identifies a transaction.

Time, Local Transmission response.

For Point-of-Service (POS) terminals sending credit card transactions identifies the hour, minute and second a transaction is sent. If submitted, it must be POS terminal time and match the printed receipt.

It is always recommended that merchants must submit relevant Time, Local Transmission (Bitmap 12) value for Amex and Discover (JCB (US Domestic only), and Diners) transactions. However, if Bitmap 12 is not populated, First Data will submit Eastern Time (ET) as the time for local transmission. It should be however, taken into consideration that not all merchants are based out of East Coast of United States.

This is the time stamp of the transaction, and as a Regulation E requirement it should be printed on the Debit Receipt given to a customer. It does not change on subsequent transactions (i.e., on debit reversals).

For any merchant sending Debit/EBT card transactions, this field must be sent with the request. It is assigned by the terminal.

On 0400 (Debit/EBT) reversal message the time of the transaction must match the Transmission Date/Time in the original 0200 (Debit/EBT) request.

Primary Account Number.

This field identifies the card member‘s account number. Unlike most numeric fields, the Primary Account Number is left-justified. In this case, the rightmost byte is padded with a ½ byte binary zero (e.g., a three-position field, X ‘03 12 30‘).

Not included for check transactions message.
In the 0200 Financial Transaction messages for EBT Card, this field is mandatory if the Track 2 Data cannot be read.

Processing Code.

A required code is used in conjunction with the message type to define the type of transaction that is by the terminal to the host.

Retrieval Reference Number.

Authorization only — For Credit and debit transactions (excluding Canadian Debit) the retrieval reference number can be any value based on the merchant‘s choosing (e.g. sequential tracking of transactions, fixed value etc.). The value submitted in the request message is then echoed back in response. For example the value of 000000000001 for all transactions can be used. If the merchant leaves the retrieval reference number blank in the request, First Data will assign a unique 12-byte retrieval reference number and the assigned value will be returned in the response.
Authorization with capture — For Credit and debit transactions (excluding Canadian Debit), this is a unique 12-byte reference number assigned to a transaction by the merchant and returned in the response message. The retrieval reference number should increment from …..001 to ….999 and should not be reset on a daily basis until it reaches ….999.
Capture Only – For Credit card transactions the retrieval reference number must be the same value that was submitted in the original authorization request.
Canadian Debit — The POS terminal at the merchant‘s location generates the retrieval reference number and includes it in the transaction request. The host echoes the value back in the response. The terminal must ensure that the number is unique.
Reversals — In a 0400 (Debit/Credit) reversal request message, the retrieval reference number does not have to match the original 0100 (Credit) and 0200 (Debit) request. This is applicable to all transaction type (Credit, Debit inclusive of Canadian Debit). For Host Draft Capture, RRN submitted at the time of authorization should match the RRN submitted in the reversal for Auth and Capture transactions.

Terminal ID.

Contains a code that identifies a merchant terminal. A unique code must be assigned to each terminal/POS device (e.g., a register) in a merchant location. This code will be returned on the host response. In certain instances, the Terminal ID may be assigned by the merchant; in other instances, First Data assigns it. Please check with your First Data representative for details.

The Terminal ID does not conform to the standard definition of alphanumeric fields: it is right justified and zero-filled on the left.
On a 0400 reversal message, this field must match the original 0100/0200 request.

Merchant ID number.

Contains a code assigned to a merchant location. Merchants must use the First Data-assigned Merchant ID (see note below). The Merchant ID does not conform to the standard definition of alphanumeric fields: it is right-justified and zero-filled on the left.

On a 0100 VRU Authorization only (page 2-10), the Merchant ID can be the First Data internal number or a merchant external number.
On a 0400 reversal message, this field must match the original 0100/0200 request.

Used for both Balance Information and Partial Auth transactions in VISA, MasterCard, Amex, Discover (Diners, JCB US Domestic), and Debit. These features are supported only for Pre-Paid Gift, FSA, HRA Accounts.

Transmission Date/Time.

This code identifies the month, day, hour, minute, and second a transaction is sent (MMDDhhmmss). This must be represented in GMT or Universal time.

Network Management Information Code.

Indicates the function of a particular 0800 Test Message.

Reference to the client.

Identification number of the datawire.

Identifier of the object used for references; auto-incremented integer value.

Code of Merchant Account to which instance of this object is attributed to. Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.

A code that defines the message type. The message types and their associated codes are as follows:

Authorization Messages

0100 Authorization Request
0110 Authorization Request Response

Financial Transaction Messages (Debit only)

0200 Authorization/Financial Transaction Request
0210 Authorization/Financial Transaction Request Response

Reversal Messages

0400 Reversal Request
0410 Reversal Request Response

Network Management Messages

0800 Network Management Request
0810 Network Management Request Response

Identification number of the provider.

Getaway generated response message.

Identification number of the service.

Token code of the transaction.

Reference to the entity that represents the initial token transaction information.

URL adresses.

For example, E-commerce URL address.