Trust Commerce Auth Retail Transaction UML

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

Type of transaction action (e.g. "sale", "preauth", "postauth", "credit", "void", "store", and so on).

Part of the total amount in the transactions that is assigned to Healthcare Eligible.

Part of the total amount in the transactions that is assigned to Healthcare Eligible.

Street of the merchant's mailing address.
Personal address information of the merchant.

Transaction amount in cents (for example, $1.00 would be submitted as "100").

The "avs" response code returned by the address verification system (AVS).

Alphanumeric code used to retrieve customer payment card and ACH information for future, one-time and recurring/installment transactions.

The name of the input field that contained the blacklisted value; this can be one of the following: “name”, “cc”, “ach”, “zip”, “address1”, “state”, “country”, “email”, “phone”, or “ip”.

The input value that triggered the blacklist decline; for instance, if the decline was due to a blacklisted IP address, the offending IP address would be returned here.

Cardholder primary account number (PAN) (for example, a credit or debit card number).

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

Indicates whether TrustCommerce should decline the transaction on behalf of the integrator if the CSC does not match as reported by the card issuing bank. Only used if “cvv” is provided.

City of the merchant's mailing address.
Personal address information of the merchant.

Country of the merchant's mailing address.
Personal address information of the merchant.

Customer identification number assigned by TrustCommerce.

The three- or four-character field located in the front or back of the card. * For Visa, MasterCard, and Discover, this is a three-character field located on the back of the card to the far right.

For American Express, it is a four-character value located on the front of the card above the primary account number.

This field should be assigned if the “cvv” field is not submitted. Possible values include “present”, “notpresent”, and “illegible”. By default, it will be treated as “notpresent” although some processors may treat it otherwise if this field is not submitted by the integrator.

• The “present” value states that the integrator did not provide the card code stated above even though it was present.
• The “notpresent” value states that the integrator did not see a card code.
• The “illegible” value states that the integrator could not read the card code.

In all cases, this field is used when the CSC is not submitted. By submitting a CSC, the merchant is stating that the CSC is present and the value is the “cvv” indicated above. Only used if “cvv” is NOT provided.

Used to indicate the transaction request is a test or demo transaction regardless of account status.

Indicates whether transaction request is processed via TC Link or TC Vault.

Email of the merchant for discussing any processing issues or sending notifications.

Track1 or Track2 data encrypted at the swipe device.

Payment card expiration date in “MMYY” format.

The actual numeric score (0 to 100) assigned by TrustCommerce CrediGuard to the transaction.

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

Indicates that the processor's qualification of eligibility of the provided card number is required.

Indicates a submission of an IIAS eligible transaction.

Identifier that is used for processing sale transactions under Billing ID provided by a processor.

Password that is used for processing sale transactions under Billing ID provided by a processor.

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.

Name of the customer.

Six-digit numeric code used to force the transaction.

A field the integrator may choose to use if there are multiple operators that are potentially entering transactions. The operator field is only used for reporting within TrustCommerce systems.

Indicates whether partially authorized transactions are supported by the system or not.

The TrustCommerce Link password associated with the aforementioned CustID.

The payment number associated with the transaction. It is required for both recurring and installment payment transactions and is required for a transaction to be flagged as recurring.

Phone number of the merchant for discussing any processing issues.
Personal information of the merchant.

Indicates whether debit card is identified in UniPay by BIN.

Indicates whether debit card is identified on the processor's side by BIN.

Purchase level provided by TrustCommerce.

Purchase order number "purchaseordernum" is provided by the customer.

Authorization response code (result of the authorization).

Response to AVS verification of the transaction.

A status of "baddata" indicates that no transaction was attempted because one or more fields were invalid. In this case, the field error will indicate the problem, and the offender field lists the offending input fields.

See the specification of the processor for more information.

The response code as sent to TrustCommerce from the processing platform.

The textual description of what this code indicates, as documented in the processing platform’s messaging documentation.

Indicates whether the credit card type is commercial.

Response to CVV verification of the credit card.

Type of response status.
When status is set to "decline", the "declinetype" field contains corresponding information about declined transaction. See the specification of the processor for more information.

A status of "error" indicates an error occurred while processing the transaction. See the specification of the processor for more information.

Response offenders.

Partial amount received in response file if the partial authorization is supported by the system.

Type of the response status of the transaction.

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

Date of the shipping.

The address of the destination where the goods are being shipped. If this field is not provided, TrustCommerce will send blanks.

The city of the destination where the goods are being shipped. If this field is not provided, TrustCommerce will send blanks.

The country of the destination where the goods are being shipped. If this field is not provided, TrustCommerce will send blanks.

The name of the customer to whom the goods are being shipped. If this field is not provided, TrustCommerce will send blanks.

The same destination where the goods are being shipped before. If this field is not provided, TrustCommerce will send blanks.

The state of the destination where the goods are being shipped. If this field is not provided, TrustCommerce will send blanks.

The ZIP (or postal) code of the destination where the goods are being shipped. If this field is not provided, TrustCommerce will send blanks.

State of the merchant's mailing address.
Personal address information of the merchant.

"Y" or "N".

This function pushes credit card data to TrustCommerce Citadel and returns a billingID. This enables merchants to charge the cardholder and keep a record on file for use at a later date. The store function only pushes data to citadel if the sale/preauth is approved. The BillingID is returned in the sale/preauth transaction response. The sale/preauth is associated with the BillingID record.

The amount of tax, in cents, charged for this order. If the order is tax exempt, you may omit this field or set the field to "0".

Can be set to "localsales" or "taxexempt" to indicate the specific tax status of the order.

This discretionary field can be used as a merchant-specified transaction identifier for searching and reporting. In some cases, the value of this field is passed through to the financial institutions.

This is the amount of the tip (in cents) to be included in the “postauth” request (for example, $1.00 would be submitted as “100”).

This field indicates the number of installments. It is required for installment payment transactions.

Unique identifier assigned to each transaction regardless of the status.

Indicates that the transaction is assigned to MOTO industry.

This is a brief string that contains the precise reason for the velocity decline:
• The first part of the string contains a velocity type, either “global”, “zip”, “ip”, or “cc”.
• The second part of the string contains a time period, either “1day”,
“3day”, “15day”, or “30day”.
• The third part of the string contains an indicator of the type of violation, such as “count” if the transaction count for the velocity type and time period was exceeded, or “total” if the dollar amount sum was exceeded.

This is the value that exceeded the velocity rule; for example, if the rule were a limit on CC# usage, this would be set to the last four digits of the credit card number.

Indicates that payment card (credit or debit) information is valid.

ZIP (or postal) code of the merchant's mailing address.
Personal address information of the merchant.