Vantiv Lowell Auth Retail Transaction UML

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

The elements addressLine1 defines the address information

The amount element defines the amount of the transaction. Supply the value in cents without a decimal point.

The authCode element it specifies the authorization code from the associated Authorization transaction.

The authenticationResult element defines the Visa CAVV Result code (from Verified by Visa).

The avsResult defines the Address Verification response code returned by the networks.

The BIN element provides the 6-digit Bank (or Issuer) Identification Number of the Issuing Bank. The system returns this value in XML responses when issuing new tokens to replace Visa or MasterCard account numbers. For Discover and American Express cards, this element is empty.

The capability element is a required child of the pos element, which describes the capability of the point of sale terminal.

The cardValidationResult defines the Card Validation response code returned by the networks.

The cardholderId element is a required child of the pos element, which describes the method used for cardholder identification at the point of sale.

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

The city element defines the customer’s city name

This value is used to submit the amount of all Clinical or other qualified medical expenses contained within this purchase.

A value assigned by the merchant to identify the consumer.

The email element defines the email address of the customer

The entryMode element is a required child of the pos element, which describes the method used for card data entry at the point of sale.

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

The litleToken element defines the value of the token. The system returns this value in XML responses when issuing new tokens to replace account numbers.

The litleTxnId element is used to identify transactions in the Litle system. The system returns this element in XML responses. You use it in various requests to reference the original transaction.

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.

The merchantId element is used when you request an Account Update file. This value is a unique string used to identify the merchant within the Litle system.

The message element provides a brief definition of the response code.

The name element defines the customer name.

The orderId element defines a merchant-assigned value representing the order in the merchant’s system.

The orderSource element defines the order entry source for the type of transaction.

Defines the customers phone number.

The postDate element defines the date the transaction was posted. The format is YYYY-MM-DD. It occurs only in response to Online transactions.

Defines the merchant sub-group in the user interface where this transaction will be displayed.

The response element contains a three digit numeric code which specifies either that the transaction is approved (000 code) or declined.

The responseTime element provides a date/time stamp of the response. The format of the element is YYYY-MM-DDTHH:MM:SS.

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

The state element defines the customer’s state name

The tokenMessage element contains a short, human-readable explanation of the tokenResponseCode.

The tokenResponseCode element provides a 3-digit code indicating the results of a transaction involving the conversion or attempted conversion of an account number to a token.

We use such values:
C - Credit Transactions
A - Authorization Transactions
V - Void Transactions

The Credit transaction enables you to refund money to a customer, even if the original transaction occurred outside of the Litle & Co. system.
The Authorization transaction enables you to confirm that a customer has submitted a valid payment method with their order and has sufficient funds to purchase the goods or services they ordered.
You use a Void transaction to cancel a transaction that occurred during the same business day.

Defines the type of account used in the transaction.
We use such values:
VI -Visa Credit, Visa Debit,
MC - MasterCard Credit, MasterCard Debit,
AX - Amex,
DI - Discover,
DC - Dinners
or empty

The user element is a required child of the authentication element. It is a unique identifier of the user/merchant used to authenticate that the message is from a valid source.

The ZIP element defines the customer’s postal code.