The players in an iVeri transaction generate the following fields to identify an individual transaction:
|
Player |
Individual transaction identifier |
|
Merchant |
Merchant Trace |
|
iVeri Gateway |
RequestID |
|
Acquirer |
Acquirer Reference |
The players in an iVeri transaction generate the following fields to identify a transaction sequence:
|
Player |
Transaction sequence identifier |
|
Merchant |
Merchant Reference |
|
iVeri Gateway |
Transaction Index |
A MerchantReference is a unique identifier defined by the Merchant for a transaction sequence within a limited time period. A MerchantReference is mandatory (for initial transaction requests and optional for follow-up requests). It typically corresponds to an invoice or ticket number (a transaction sequence).
A MerchantTrace is a unique identifier for each request sent to the gateway and is an optional parameter. The MerchantTrace corresponds to a database index that was generated before a request was sent to the gateway. In short, the MerchantTrace refers to a particular step in the transaction sequence.
[Example]:
For a Debit followed by an immediate Void (cancellation of ticket etc):
The MerchantReference remains the same for both steps of the transaction sequence,
while the MerchantTrace is different for the Debit and Void.
A single MerchantReference can be associated with many MerchantTrace's.
Similarly, a single TransactionIndex can be associated with many RequestID's.