- 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
CyberSource data is additional transaction data which iVeri Payment Technologies Ltd needs to process orders within CyberSource's fraud screening solution.
Device Fingerprinting
In order to successfully implement Device Fingerprinting, a 1-pixel image file (which cannot be seen) and two scripts need to be placed in the <body> tag of the merchant’s checkout page*. This will ensure a 3-5 second window in which the code segments can complete the data collection necessary to create a fingerprint for the device making the order.
Below are the code segments for implementing Device Fingerprinting:
<p style="background:url(https://h.online-metrix.net/fp/clear.png?org_id=<org ID>&session_id=<merchant id><session ID>&m=1)"></p> <img src="https://h.online-metrix.net/fp/clear.png?org_id=<org ID>&session_ id=<merchant id><session ID>&m=2" alt="">
<object type="application/x-shockwave-flash" data="https://h.online-metrix.net/fp/ fp.swf?org_id=<org ID>&session_id=<merchant id><session ID>" width="1" height="1" id="thm_fp"> <param name="movie" value="https://h.online-metrix.net/fp/fp.swf?org_id=<org ID>&session_id=<merchant id><session ID>" /> <div></div> </object>
<script src="https://h.online-metrix.net/fp/check.js?org_id=<org ID>&session_ id=<merchant id><session ID>" type="text/javascript"> </script>
|
Parameter |
Data Type |
Description |
|
Org ID |
AN |
Will be supplied by iVeri Payment Technologies Ltd to the merchant. |
|
Session ID |
AN |
The session ID is a string variable (letters and numbers only) that must be unique for each merchant ID. Any string that are already generating, such as an order number or Web session ID. However, do not use the same uppercase and lowercase letters to indicate different session IDs. This is the same value that must be send to iVeri in the DeviceFingerprintID field. |
|
Merchant id |
AN |
Will be supplied by iVeri Payment Technologies Ltd to the merchant. |
Coding for CyberSource data
The following is a code snippet in C#:
enterprise.openElement("CyberSource");
enterprise.setTag("DeliveryMethod", Virtual);
enterprise.setTag("DeviceFingerprintID", sessionId);
enterprise.setTag("BillTo_FirstName", billTo_FirstName);
enterprise.setTag("BillTo_LastName", billTo_LastName);
enterprise.setTag("BillTo_Street", billTo_Street);
enterprise.setTag("BillTo_City", billTo_City);
enterprise.setTag("BillTo_Country", billTo_Country);
enterprise.setTag("BillTo_Email", billTo_Email);
enterprise.setTag("BillTo_IPAddress", billTo_IPAddress);
enterprise.closeElement();