Payvision Auth Retail Transaction UML

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

The amount element defines the amount of the transaction. Supply the value in cents without a decimal point.

Review the Appendix of your acquirer, provided separately, to check how to format this parameter.

Street address for AVS verification. Review the Appendix of your acquirer, provided separately, to check how to format this parameter.

Indicates the entity that provides the AVS response.

Indicates the result of the AVS check.

ZIP Code for AVS verification. Review the Appendix of your acquirer, provided separately, to check how to format this parameter.

The specific code returned by the acquiring in the CDC field, indicating whetehr the transaction is approved or not.

The specific code returned by the acquiring in the CDC field.

The specific code returned by the acquiring in the CDC field in text message.

Month part from the expiry date, specified on the credit card.

Year part of expiration date, specified on the credit card.

Card Guid obtained during a RegisterCard operation

Card holder name as it appears in the card.

Card identifier obtained during a RegisterCard operation

Credit card number.

Reference to the entity that represents transaction of type Sale.

ISO 3166 Country code (numeric) that indicates the country where the transaction took place.

ISO 4217 Currency code (numeric) that indicates the currency of the transaction.

A code that reflects the outcome of the CVV2/CVC2 check.

The CVV code must be sent for E-Commerce transactions. This field is optional depending on the merchant account.

Second part of dynamic descriptor. Check the Appendix of your acquirer, provided separately, to know how to format this parameter.

First part of dynamic descriptor. Check the Appendix of your acquirer, provided separately, to know how to format this parameter.

Special code that identifies the type of occurred error.

Special text message from the provider about occurred error.

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

This value is provided by Payvision and is used to authenticate a merchant.

This value is provided by Payvision and is used to authenticate a merchant.

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.

This value represents the type of the merchant account that will be used to perform the transaction. Valid values are:

1 – E-Commerce
2 – Mail Order / Telephone order
4 - Recurring

Friendly message indicating the result of the card registration.

Type of request from the client.

This value indicates if the card was successfully registered or not. A 0 means OK, different than 0 means error.

The codes represent group of common errors, in some cases you will be able to obtain a detailed code in the CDC.

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

This value is the order number or tracking code, it can contain any alphanumeric value with a maximum length of 100 chars. The value must be unique during 24 hours.

UTC date and time in which the transaction was processed by Payvision.

Guid obtained with an Authorize transaction.

ID, obtained with an Authorize transaction.