First Data Token Transaction UML

Represents tokenization transaction as it is defined in Trust Commerce's tokenization specification.

Contains the credit card account number which identifies the customer. The account number is left justified with trailing spaces.

Identification number of the used application.

Reference to the client.

Identifier of the merchant. Assigned by the processor.

Identifier of the merchant. Assigned by the processor.

Expiration date of the associated credit card.

Tokenized value of the merchant account number.

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.

Identifier of the merchant. Assigned by the processor.

Method of Payment (MOP) associated with the transaction.

Order number associated with the transaction. Assigned by the merchant.

Date when response message received from the processor was received.

Code of the response message recieved from the processor.

Specific identifier. Assigned by the processor.

Identifier of the terminal. Assigned by the processor.

Reference to the entity that represents token transaction information.

Identifier of the merchant. Assigned by the processor.

Third Party Processor ID - The TPP ID is mandatory on all Authorization requests submitted by Third Parties who have been issued one by First Data. If you were assigned a Third Party Processor ID, you are required to send this additional format record.
If you were not assigned a Third Party Processor ID, this record should not be sent.

Datawire address where the transactions are sent to.