Retail Transaction

Represents real-time financial transaction.

Transaction amount that is to be used for settlement.

In most cases Amount and Capture Amount will match. In cases of partial authorizations as well as in some business scenarios, Capture Amount might be less than the Amount. Capture Amount cannot exceed the value in the Amount field.

Indicates whether transaction is confirmed to be settled (captured) or requested to be voided (non-captured).

The field is used in scenarios when a business process requires initial transaction authorization and a subsequent explicit confirmation of the settlement. In such cases transaction is initially sent as unconfirmed (basically void) and when appropriate is confirmed later before the settlement for the day occurs.

Please see Integration Specification for additional details on capture and void operations.

CVV2 of the card that is used in the transaction.

Note: the field is transient and is not present in the database

Indicates whether or not CVV2 was supplied.

Possible values:

P - value was supplied
N - value was not supplied
I - value was not supplied because it could not be read
X - value was not supplied because it was not present on the card

Note: the field is transient and is not present in the database

Response code supplied by the Provider that processed the transaction based on CVV2 value supplied during transaction authorization.

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

Raw parsed response text returned by the Provider for this transaction.

The field is for internal purposes only and should not be exposed to the outside world.

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

Reference to a sub batch that this transaction belongs to.

See Sub Batch definition for additional information.

For swiped transactions only, this field contains track data of the card that is used in the transaction.

Note: the field is transient and is not present in the database

For swiped transactions only, this field contains track data of the card that is used in the transaction.

Note: the field is transient and is not present in the database

Enumeration of possible industry types assigned to this transaction.

Industry Type dictates processing rules and interchange rate that affect this specific transaction.

Date and time when void was issued on this transaction.

Value from the transaction submitter's system.

It is used to assign submitter's specific void transaction id to the transaction, to cross reference this transaction between two systems.

Usually, the value will contain a reference to an entity representing this void transaction in submitter's front-end system.

In cases when submitter doesn't record void transaction as a separate record with a unique id (but rather as an adjustment to the original transaction), the field will not be used.

Description of the void transaction, might be coming from the submitter's system or assigned internally. Usually will contain explanation behind the void.