This section explains how to implement a follow up/subsequent transaction using the TransactionIndex returned from an initial/previous transaction processed successfully.
Merchants that wish to accept payments from regular customers without worrying about PCI DSS burdens of storing or retaining the card number have an option of submitting a unique identifier associated with the customers card number from a previously successfully processed transaction. In iVeri's realm, the identifier which the merchant can pass on subsequent transactions is called the “TransactionIndex”. This variable is an iVeri Gateway generated identifier commonly found in Gateway responses to the merchant.
Initial Transaction
When a merchant sends a transaction request(POST) to the iVeri Gateway, the response returned to the merchant generally contains a number of variables, some of which are important when performing subsequent transactions, in order for the merchant to implement subsequent transactions the following variables must be stored on the merchants database.
- Lite_TransactionIndex
- Ecom_Payment_Card_Number
- Ecom_Payment_Card_ExpDate_Month
- Ecom_Payment_Card_ExpDate_Year
Subsequent Transactions
When TransactionIndex is used on subsequent transactions, regular customers do not have to re-supply the card data details however this ONLY works if the merchant developer has made provisions for the following:
- Ability for the merchant to identify the customer, usually by means of user sign-in
- The merchant has successfully processed a transaction on the customers card at some point in time using the iVeri Gateway
- That the customer's profile is mapped to the correct Tokenised card details (TransactionIndex, Expiry date etc) returned on the initial or previously processed transaction
Subsequent Transactions implementation
On the request to the Gateway, the merchant developer has to pass all the required variables that pertain to a subsequent transaction so as to make sure that the iVeri Gateway handles the request appropriately.
Variables that should be present in the request to the iVeri Gateway are as follows:
- The Lite_PanFormat must be set to TransactionIndex
- Set the Lite_TransactionIndex to the actual TransactionIndex value e.g {000000-000000- 000-0000 0000000}
- Set the Ecom_Payment_Card_Number to the Dotted PAN value
Note: These variables are defined in 8.2 iVeri specification. In addition to these the merchant will still need to pass all the other required variables.