* LiteBox Hosted Payment Page *
**
The LiteBox hosted payment page is an e-commerce solution that allows merchants to connect, send payment requests to the iVeri Payment Gateway without redirecting the cardholder away from their website. When implemented, the LiteBox pops up and sits in-front of the merchant’s website. From a merchant/cardholder point of view the LiteBox solution provides a more seamless checkout experience.
An example is available online on None [1] this link . To simulate the LiteBox behaviour, click on “Modal”.
Merchants’ developers can download the JavaScript library that handles the events to generate the button. The library can be found on the following URLs:
For Nedbank acquired merchants located in South Africa, Zimbabwe, Namibia, Lesotho and Swaziland: https://p
3DS 2 Parameters *
**
Request Parameters *
Parameter *
Description *
Merchant ReturnUrl
Mandatory: The URL which the Gateway will post return response
parameters to
ApplicationID
Mandatory: Merchant Application ID generated upon the creation of the
merchant profile on the iVeri Gateway
MerchantReference
Mandatory:
A merchant generated identifier that is unique within a specified time that
identifies a transaction sequence.
Amount
Mandatory:
The total value of the transaction in the smallest unit of the currency
specified (eg in cents)
Currency
Mandatory:
The ISO 4217 currency code of the value of the transaction. e.g., USD or ZAR
or GBP
PAN
Mandatory:
Card number used for transaction
ExpiryDate
Mandatory:
The last month of the validity period of the card, formatted as MMYY or MMYYYY
Card
Void
**
Void should be performed on an event where transactions are not responded to or not completed to the merchant’s application which could be due to a timeout scenario. When used the void message should be performed closer to the time it relates. For more on the use of Void messages, refer to the Ensuring end to end Transaction Integrity
REST
SOAP
Request
{
"Version" : "2.0" ,
"CertificateID" : "{5c4b9c74-0063-4240-9cff-f730675c5bd0}" ,
"ProductType" : "Enterprise" ,
"ProductVersion" : "WebAPI" ,
"Direction" : "Request" ,
"Transaction" : {
"ApplicationID" : "{d8d5a94-8fa0-428d-a539-3a5baf166f7f}" ,
"Command" : "Void" ,
"Mode" : "Test" ,
"OriginalMerchantTrace" : "DIAAAY22734" ,
"OriginalRequestID" : "{9667792F-635A-4121-AC85-E06856ADC3EF}"
}
}
< soap:Envelope xmlns:xsi = "
CyberSource Fraud Management
**
CyberSource data is additional transaction data which iVeri Payment Technologies Ltd needs to process orders within CyberSource's fraud screening solution.
Device Fingerprinting *
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:
PNG Image
<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.onli
/ Nedbank Gateway /* – Applicable for Nedbank acquired merchants located in South Africa, Zimbabwe, Namibia, Lesotho and Swaziland
Website *
URL *
Port *
BackOffice *
[1] https://backoffice.nedsecure.co.za/
443 *
Lite
[2] https://portal.nedsecure.co.za/Lite/Authorise.aspx
Authorization Information
[3] https://portal.nedsecure.co.za/Lite/AuthoriseInfo.aspx
/ CIM Hosted Gateway /* – Applicable for merchants acquired by CIM Finance in Mauritius
Website *
URL *
Port *
BackOffice *
[4] https://backoffice.merchant.cim.mu/
443 *
Lite
[5] https://portal.merchant.cim.mu/Lite/Authorise.aspx
Authorization Information
[6] https://portal.merchant.cim.mu/Lite/AuthoriseInfo.aspx
/ CSC Hosted Gateway */– Applicable for merchants that acquired by banks af
V4.139 7/2/2024
**
Release Notes Overview
The release notes provided in V1 of this document serve as an initial preview of the changes expected in the upcoming production release scheduled for November 12th, 2023, on the Hosted Gateway.
The definitive release notes for deployment in production will be included in V2 of this document.
Summary
The Gateway release notes will contain information related to the new iVeri software release. The release notes will include the impact of software release to the intended target audience.
The release notes will adopt the format outlined below, as applicable:
Compliance - Refers to the adherence of the software to specific industry standards, regulations, or internal policies. This includes ensuring that the software meets legal and regulatory requirem
3D Secure 2 Test Cases BY 3D secure Vendor/MPI *
**
The MPI test cases that should be used are depended on the acquiring bank that holds the merchant agreement or PSP that will be processing the payments on the Gateway on behalf of the merchant
Things to note about the test cards:*
CVV not required Expiry must be current or future date
BANKSERV *
For merchants and acquiring banks in South Africa and Kenya
Frictionless
Full authentication *
Scenario
1 *
Authenticated
Frictionless Transaction *
Test
Values *
Visa*:4069425217889137
MC:*5163426869252246
DINERS*:36135230403232
Expected results -
Lookup *
EnrolledStatus: Y
paresTxStatus: Y
TDS2.transStatus: Y
ECI (Visa): 05
ECI (MCI): 02
ECI (DINERS): 05
PARESVERIFIED: true
PROTOCOL: 3DS 2.1.0
MD_STATUS: 1
MD_ERROR_MESSAGE:
Authenticated
Action
Authorisation Header *
**
When interfacing with the Gateway endpoints, merchants
can include the AuthenticationKey and AuthenticationToken in the headers for
both transaction status queries and transaction submissions.
Headers **
AuthenticationKey*
The key consists of the username. The key and username must be in lowercase
The Username must be encoded to base64 i.e bWVyY2hhbnRwcm9maWxlPTYxNjk1NA
AuthenticationToken*
The token consists of:
AuthenticationSecret *
This is the secret key generated by the merchant
within Backoffice, which the merchant has to store on the merchant’s system.Once the secret is generated, it remains readable in
plain text for a couple of minutes, after which it is hashed. Merchant must copy the secret immediately
after the secret is generated.
If the merchant lose
Gateway Release Notes *
**
The release notes contained in this document will be applied on the Hosted Gateway and Nedbank Gateway Notes
* 3D Secure 2 implementation using the Form Post *
*
Merchant can POST Form variables to the 3DS 2 endpoint, which is redirect over the browser. On completion of the 3D secure process, the Gateway will return the result to the merchant ReturnURL. The result returned to the merchant will either allow for the continuation of the Authorisation/debit instruction or result in the termination of the transaction by the merchant to the customer.
Format: Form Data
* Form Post request Sample *
<form
name="Form1" method="post"action="https://portal.iveri.net/threedsecure/EnrollmentInitial"
id="Form1">
<input
type="hidden" name="ApplicationID"
id="ApplicationID"
value="{ca8a6eae-a469-4b39-bef3-aa029ca3a806}" />
<input
type="hidden" name="ReturnUrl" id="ReturnUrl"
value="https://[domain]/Lite/Result.as