Clearhaus Auth Retail Transaction UML

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

Total amount of the transactions including discount and tax. Amount in minor units of given currency (e.g. cents if in Euro).

The value of this parameter is assigned to you by Clearhaus.

Approved amount of the transaction.

Transaction ID used to identify the original transaction.

CSC code of the card.

Month of the card expiration date.

Year of the card expiration date.

Credit card or bank account number.

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

Code of the currency used for transaction.

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 partition and data management, to make it easy to determine the ownership of a record within the database.

Date when transaction was processed.

Identifies whether transaction is recurring.

Reference number of the transaction.

Gateway generated response code.

Gateway generated response message.

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

Sign API key of the transaction.

Name of a sign key used by the processor as additional authorization level. It is necessary to specify it when processing Bank Debit Card (ATM Card) without CSC.

Text that is placed on cardholder’s bank statement.

3-D Secure PARes.

Processor's ID of the transaction.

Type of the transaction.

Suffix to the URL to which the request is sent.