Vantiv Lowell Batch Transaction UML

Entity that represents a batch transaction as it is defined in Vantiv Lowell's batch processing specification.

Account number of the customer.

The accType element is a required child of the echeck, originalAccountInfo, and newAccountInfo elements defining the type of eCheck account used in the transaction.
We use such values:
Checking, Savings, Corporate

The element addressLine1 define the address information in both the billToAddress and shipToAddress elements.

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

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

The avsResult element is an optional child element of the fraudResult element. It 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.

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

The city element defines the customer’s city name in the billToAddress and shipToAddress elements. In the customBilling element, city defines the location of the merchant for card-present transactions.

A value assigned by the merchant to identify the consumer.

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 length of the token is the same as the length of the submitted account number for credit card tokens or a fixed length of seventeen (17) characters for eCheck account tokens.

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. For example, when you submit a Capture transaction, you include the litleTxnId for the associated Authorization.

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 message element contains a brief definition of the response code returned for the transaction.

The name element defines the customer name in both the billToAddress and shipToAddress elements.

The name element is required for Echeck transactions. If you do not submit the customer name in an Echeck transaction, Litle returns Response Code 330 - Invalid Payment Type.

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.

If you submit the wrong <orderSource> value, Litle returns the response code 370 - Internal System Error - Contact Litle.

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

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

The state element defines the customer’s state name in both the billToAddress and shipToAddress elements.

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.

Litle Batch processing supports all transaction types except Voids and eCheck Voids, which are handled as Online transactions only. We use such transaction types as:
ES - eCheck Sales Transaction
EC - eCheck Credit Transaction
S - Sales Transaction
C - Credit Transaction

The type element defines the card type in terms of prepaid, credit, debit, FSA, or unknown.
We use such values:
VI -Visa Credit, Visa Debit,
MC - MasterCard Credit, MasterCard Debit,
AX - Amex,
DI - Discover,
DC - Dinners
or empty

Reference to the entity that represents provider charge transaction information.

The ZIP element defines the customer’s postal code in both the billToAddress and shipToAddress elements.

Although the schema specifies the maxLength of the <zip> element as 20 characters, in practice you should never exceed 10 characters in your submissions.