HPG Auth Retail Transaction UML

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

Account Number being paid.
This field is optional.

When Tokenization is not available and encryption is allowed on the server, the field contains encrypted credit card number or bank account number.
Note: if encryption is not allowed on the server and tokenization is not properly configured, transactions will fail and will not be either processed or persisted.

Mailing address of the cardholder (street line).

The authorization code sent from the CC Processor.

The additional reference sent from the CC Processor.

The original amount authorized. (Does NOT include convenience fee).

The original amount authorized. (Does NOT include convenience fee).

Represents the expiration date of the card used in the transaction. Usually printed on it's front side. Format: MMYY.

Credit card number.

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

City of the merchant's mailing address.

The amount of the convenience fee of this transaction (Can be $0.00)

The amount of the convenience fee of this transaction (Can be $0.00).

The amount of the convenience fee, can be 0.00.

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.

Name of the cardholder written on the credit card.

The Origin to apply the payment to.
This field is provided by HPG Implementation.

Phone of the merchant's mailing address.

Not used by API, it is returned in the result information to assist with Async calls or tracking.

Gateway generated response code.

0 – Success
100 – Failure

Gateway generated response message.

A description of the response if there was an error.

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

State of the merchant's mailing address.

Total amount of authorization (including base amount and convenience fee amount).

Total фmount of authorization (including base amount and convenience fee amount).

Type of the original transaction.

Unique identifier for transaction.
This field is required for voids.

ZIP code of the mailing address of the cardholder. Max 5 characters.