STS Auth Retail Transaction UML

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

The Action_Code tells what type of transaction you are sending.

Reffer to the STS Provider's Specification for more detailes.

Cardholder's street address.

This value is the remaining balance.

Amount approved (Can be less than requested amount – partial approval.)
This field only appears in response to action code 19 transactions.

Authorization number returned when response code = 00. Use this number for follow-on requests such as Void or Add Tip.

R = Retail/Other;
F = Restaurant.
Default is R.

The number of the credit card or bank account.

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

Cardholder's City.

Cardholder's email address.

Cardholder's first name.
This field will have one space in it if the name is not in the database.

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

Cardholder's last name.
This field will have one space in it if the name is not in the database.

No implied decimal.
Only returned for loyalty transaction requests. Required for loyalty requests.

Example: 200 = two hundred.

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.

Merchant number assigned by processor or MSP.

This field can be used to give the merchant additional messages to display on receipts, etc. i.e. a Rewards Message.

Cardholder's primary phone number.

The amount of points of loyalty, present on card.

No Decimals implied.
Required for Action Codes 03 and 04.

Example: 20000 = 20 thousand.

No implied decimal.
Only returned for loyalty transaction requests. Required for loyalty requests.

Example: 200 = two hundred.

S = Swiped;
M = Manual.

Required except for Action Code 12 (Totals Inquiry).

Each two digit response code maps to a specific response, i.e.

00 = Approved/Captured.
01 = Decline/Error

Text associated with the transaction approval or decline Response_Code.

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

Cardholder's State or Provence.

Terminal ID assigned by processor or MSP.

Ticket or invoice number from your system.

The amount of given tips.
Decimal number is required.

Example: $200.00.

Fixed date (month, day, year) and time (hour, minute, second) of transaction.

MMDDYYhhmmss.

Default is N.

N = Non-loyalty;
L = Loyalty.

NA for transactions that don’t include a Points amount.

The amount of transaction.
Required for Action Codes 01, 02, 06, 07, 08 and 11.
Decimal number is required.

Example: $200.00.

This number is populated by the POS system (you) and is echoed back to you in the host response.

Cardholder's postal code.