LPB Medoro Auth Retail Transaction UML

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

Authorization action code.

Identifies that capture takes place immediately (a sale in one transaction). If not specified, it will be set to sale-auth.
True in case of SMS, false in case of DMS. If this element is not included in XML, by default its value is set to “true”.

Address where bill or invoice would be sent.

City associated with the billing address.

Country code associated with the billing address.
Country in ISO 3166-1 alpha 3 format.

Email address associated with the billing address.

Name of a person who will receive bill or invoice.

Phone number associated with the billing address.

ZIP (or postal code) associated with the billing address.

The CSC code of the card.

The expiry date of the card.

Should be included only in case a cardholder wants to use credit card data from previously registered token. On payment form cardholder would have to confirm the masked credit card data instead of entering it manually.

Credit card or bank account number.

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

Amount that would be transferred to merchant’s account. Hold from remaining funds would be removed immediately. Deposit amount should be smaller than payment amount and larger than 0, written in minor currency units. In case it is not included in XML, full payment amount would be transferred.

Dynamic descriptor appearing on cardholder’s credit card statement for the transaction. Is allowed to be included in XML only when dynamic descriptor feature is enabled.

A code that identifies encountered system error.

Description of encountered error, e.g. incorrect data, encryption/decryption error.

Name of the gateway key file.

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

Index of merchant’s RSA public key used for data encryption of the payment in progress.

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.

A unique code provided by LPB system to a merchant for identification purpose.

Name of the merchant key file.

Number of payment processing mode.

Payment amount in minor currency units.

Order payment currency.

Order description that will be shown on Payment Form.

Unique code for order identification.

Cardholder’s authentication request.

Identification number of the payment.

IPv4 address (dotted-decimal notation).

Response for payment authentication request. Returns after the first enrollment with response ACS URL.

Response for a payment authentication response received from cardholder’s card issuer ACS.

Cardholder’s card issuer bank’s ACS web address where cardholder was sent for 3D Secure authentication.

Response authorization action code, ISO 8583 field 39.

Response approval code, ISO 8583 field 38.

Cardholder’s authentication verification value retrieved in response to a request.

A response containing order description.

Electronic commerce indicator response.

Status on whether cardholder’s credit card is enrolled in 3D Secure or not, retrieved in response to a request.

Response message identification number.

Unique code for payment identification retrieved in response to a request.

Date and time (in EET – Eastern European Time) when payment was last updated, retrieved in response to a request.

Date and time (in EET – Eastern European Time) when payment was initiated, retrieved in response to a request.

Number of payment processing state that payment is currently in, retrieved in response to a request.

Status on whether cardholder passed 3D Secure authentication, retrieved in response to a request.

Transaction date retrieved in response to a request.

Transaction identification number retrieved in response to a request.

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

Identifies amount that would be returned to cardholder’s account. Reversal amount should be less than payment amount and more than 0, written in minor currency units. If it is not included, full payment amount would be returned. Can be included in XML if payment is in payment processing state Deposited or Processed.