Paymentus Auth Retail Transaction UML

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

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

City of the customer's mailing address.

Country code of the customer's mailing address.

Customer's mailing address (line 1).

State code of the customer's mailing address.

ZIP (or postal) code of the customer's mailing address.

10-digit phone number that can be used for discussing any processing issues with the customer during the day time.

Email of the customer. Used for payment and subsequent payment action notifications.

First name of the customer.

Last name of the customer.

Middle name of the customer.

Account number of the customer.

External unique identifier of the payment.

Note: External reference number must be unique. Payment will be rejected as a duplicate payment (in current, or any subsequent file) if external reference number is repeated for the same account.

Current payment operation made by the customer.

Amount of the payment.

Code of the payment type.

Payment reference number. This value will be zero if no payment is found.

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.

Credit card or bank account number of the customer.

Unique identification number of the bank.

Bank transit number.

Name of the account holder (or credit cardholder name).

Credit card expiration month (2 difits).

Credit card expiration year (4 difits).

CVV or CVD of the credit card.

Name of the bank.

Type of payment method (e.g. credit card type).

Optional additional payment amount to be included as part of the transaction, for example a donation.

Convenience fee determined by configuration.

Payment error description (if occured).

Bill payment amount.

Date in the mmDDyyyyHHmmss format.

Note: Only present within sale response.

Current status of the payment (Accepted/Failed).

Short description of the payment status.

Unique Paymentus payment reference number.

Note: Only present within sale and void responses.

Total amount charged from the customer.

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

Unique user login ID.

Password of the user, corresponding to the login ID.