First Data LP Auth Retail Transaction UML

FirstData LP specific low-level representation of Retail Transaction produced by Forward Transformation Process within Authorization Process.
During Generation Process, FirstData LP specific interchange message is generated from this object for authorization. Consequently, all fields of the object are mapped into message segments/elements.

The first line of the customer's billing street address.

The numeric portion of the street address.

Credit card number.

The numeric expiration month of the credit card

Expiration year of the credit card

Reference to the entity that represents real-time financial transaction.

The total dollar amount of this transaction including subtotal, tax, and shipping

Billing city

Company name

This field should contain the merchant store name or store number

CSC code of the credit card.

Indicates whether the card code was supplied. We use such values:
- provided
- not_provided

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.

Customer's name

The order Id to be assigned to the transaction. For sale and pre-authorization transactions, this field must be unique. For void, credit and post-authorization transactions this field must be a valid Order Id from a prior Sale or pre-authorization transaction.

The type of transaction. We use such values: Sale, Void, Credit

Billing phone number. The number shouldn't contain dashes.

The result of the transaction, which may be approved, declined, or blockedbecause of fraud.

Authentication results returned from Verified By Visa and MasterCard Secure Code.

The Address Verification System response for the transaction.

The approval code for the transaction

Any error message associated with the transaction.

Reference to the entity that represents a group of real-time transactions which must be settled together.

Any message returned by the processor

The reference number returned by the credit card processor.

A server time-date stamp for the transaction. Used to uniquely identify a specific transaction where one order number may apply to several individual transactions

The time and date of the transaction server response.

Name of the file where SSL key is stored in.

Password of SSL key.

U.S. state of billing address. For international addresses, this field can be used for the province or territory

This field is returned with every successful transaction. If you want to run a void or other transaction against an existing order ID, you may need to pass the Tdate field to identity the specific transaction you want to void.

The type of terminal that is sending the transaction. We use such value:
- POS (for an electronic cash register or integrated POS system)

Track data 1 of the credit card.

The source of the transaction. We use such values:
Eci - if order was received via email or Internet
MOTO - mail order/telephone order
Retail - face to face

The userid field is an optional custom field to track customers.

Billing ZIP or postal code.