MiGS Auth Retail Transaction UML

MiGS specific low-level representation of Retail Transaction produced by Forward Transformation Process within Authorization Process.

During Generation Process, MiGS 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.

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.

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

Identifier that is used to authenticate you as the merchant while you are using the Virtual Payment Client. Generated and allocated to you by the Payment Server.

The response code generated by the Issuing Bank in relation to the Card Security Code.

Acquirer's Response Code is generated by the financial institution to indicate the status of the transaction.

The amount of the transaction in the smallest currency unit expressed as an integer.

The total amount of the original authorisation transaction.

An identifying code issued by the bank to approve or deny the transaction.

A date supplied by the acquirer to indicate when this transaction will be settled.

The amount of the capture transaction in the smallest currency unit expressed as an integer.

A code issued by the Payment Server for the card type used by the cardholder in the transaction.

The expiry date of the card to be processed for payment.

The number of the card that is used for processing the payment.

Is a security feature used for card not present transactions that compares the Card Security Code on the card with the records held in the card issuer's database.

ASCII text representing the card track 1 data.

ASCII text representing the card track 2 data.

Indicates the transaction type. Must be equal to pay capture, refund, voidCapture, voidRefund, voidPurchase.

The response code generated by the MiGS Payment Server in relation to the Card Security Code.

Should be used for a more accurate representation of the CSC Response:
M: Valid or matched CSC
N: Code invalid or not matched
P: CSC Not Processed
S: Merchant indicates CSC not present on card
U: Card issuer is not registered and/or certified

A unique value created by you to identify the DO. It is used to track the progress of a transaction and allows it to be identified on the Payment Server should a communication's failure occur and the DR is not received.

The unique merchant ID assigned by Payment Processor.

Indicates any errors the transaction may have encountered.

Your own identifier used to identify the transaction with the cardholder. For example, a shopping cart number, an order number, or an invoice number.

Passed back to the cardholder for their records if the merchant application does not generate its own receipt number. Also known as the Reference Retrieval Number (RRN), which is a unique identifier.

The amount of the refund transaction in the smallest currency unit expressed as an integer.

The transaction reference number of the original authorisation or purchase transaction.

Allows to include a ticket number, such as an airline ticket number in the DO. It is stored on the Payment Server database for the transaction and is not returned in the DR.

A unique number generated by the Payment Server for the transaction. It is stored in the Payment Server as a reference and used to perform actions such as a refund or capture.

Allows the merchant to specify the source of the transaction.

This can only be used if the merchant has their privilege set to use this command, otherwise the transaction will be set to the merchant's default transaction source as defined by your Merchant Manager.

Allows the merchant to flag the subtype of transaction for the cardholder's order.

A response code that is generated by the Payment Server to indicate the status of the transaction.

Special AMA user created to allow this function to operate.

Is generated at the card issuer as a token to prove that the cardholder was enrolled and authenticated OK.

Contains the security level to be used in the AUTH message.
'05' - Fully Authenticated.
'06' - Not authenticated, (cardholder not participating), liability shift.
'07' - Not authenticated. Usually due to a system problem, for
example the merchant password is invalid.

The status codes used by the Payment Server.

Generated by the card issuer as a token to prove that the cardholder authenticated OK. This is a base64 encoded value.

The 3-D Secure Electronic Commerce Indicator, which is set to '05' when the cardholder authenticates OK, and '08' when the cardholder is not enrolled. (These values may change depending on the locale or issuer).

The VERes.enrolled field. It will take values:

• Y - Yes
• N - No
• U - Unavailable for Checking.

Included only if payment authentication was used and a PARes was received by the MPI. It will take values:

• Y - Yes
• N - No
• A - Attempted Authentication
• U - Unavailable for Checking.

It is a unique transaction identifier that is generated by the merchant to identify the 3DS transaction.

The password used to authorise the AMA user to access this function.