- Introduction
- Commands & Actions
- Transaction Sequence
- MasterPass
- Visa Checkout
- Foreign Exchange
- Parameter Description & Action
- Gateway Domain Knowledge
- Transaction Result Codes
-
Out Of Band
-
Out of band transaction notification
-
Out Of Band - Merchant Webservice
-
Card on File - Recurring/Adhoc transactions
-
PINBlock encryption via Triple DES DUKPT encryption
-
PINBlock encryption via Master/Session encryption
-
Track2 encryption via Master/Session encryption
-
Track2 encryption via Dukpt encryption
-
Debit with PIN and Balance Enquiry
-
EMV Transactions
-
Coding for EMV data
-
- Tokenization
- SOAP API
- Pos Device Intergration
- Acquire Contact Information
- 3D Secure
-
Enterprise API Samples
-
Transaction Message Examples
-
Merchant Benefits
-
Pre-Auth – “Authorisation with PAN”
-
3D Secure 2
-
Pre-Auth Completion – Follow-up Debit
-
3D Secure 2 implementation using the Pop-Up Method
-
Pre-Auth Reversal – “Authorisation Reversal”
-
3D Secure 2 implementation using the Form Post
-
Refund – “Follow-Credit”
-
Authorisation with 3DS 2 Data
-
Refund – “Initial Credit”
-
Void
-
- Card on File
- Additional Data Transactions
Out of Band Transaction Notifications
Out of Band Transaction notification is a dedicated messaging system that allows merchants to receive their transaction outcome reliable and timeously. The transaction outcome available in the Out of Band notification system contains the same data elements as would be found when doing a transaction look up in the gateway's endpoint or directly from Backoffice. Merchant developers can implement a webservice that will consume the transaction notification payload. The transaction notifications are usually available when the cardholder completes a payment to the merchant.
Format of the OOB Transaction Notification
- The transaction notifications to the merchant are JSON formatted, the body of the message contains a Base64 string of the VXML response. The VXML response parameters are defined in the Output Parameters per action.
Usage: Out of Band notifications are available for any transactions processed by the Gateway, no matter the channel or product.
Prerequisite
- Merchant developer has to implement a Webservice that can consume the transaction results posted to the merchants endpoint, with the sample available in merchant-webservice
- Out of Band Transaction notification must be enabled on the Test/Live application ID(s), this can be actioned by the support team - assist@iveri.com
- The merchant developer has to contact the support team - assist@iveri.com and provide the merchant URL to be used for posting transaction
- The merchant URL should be HTTPS and handle TLS 1.2 connections.