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
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
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
Download File – By File *
**
Purpose *– To download a selected file by a specific file name.
Action: *
From the main menu, the user will navigate to: Batch - Download File - By File.*
Action: *
Select the date range that the file was created/uploaded by manually changing the default dates above or clicking on the calendar icon next to each date and select each date in the calendar that is displayed.
Then click on Search. The result of your search will then be displayed.
Action: *
Select the filename of the file you want to download. The following page will be displayed. Your selected file is displayed for you to download. Click on "Download". Select the file format you wish to obtain from the drop down (either the default Fixed File Text format or XML) and then click on Download.
You can n
Application Parameters *
**
/ Purpose /* – This function is used to allocate application ID(s) that a User is only allowed to have access to. This application refers to specific product and what a merchant uses to process transactions through iVeri.
Example below indicates that when you select a particular Application ID an Administrator can configure what functions can this user perform in a particular Application ID. If no function is associated to an Application ID, no access is granted to that user.
Administrator can configure what Transaction Types a user can perform on a specific Application ID.
If no Transaction Types are configured for a user, the user will be unable to process transactions for any of the Application IDs.
/ Action /*:
Select the product and Live Application IDs you
* Shopping Carts *
**
iVeri Lite plug-in is available for download for the following Shopping Cart platforms:
WooCommerce: https://www.iveri.co.za/docs/woocommerce-6 [1]
OpenCart:
https://www.iveri.co.za/docs/opencart-14 [2]
VirtueMart:
https://www.iveri.co.za/docs/virtuemart-15 [3]
[1] https://www.iveri.co.za/docs/woocommerce-6
[2] /docs/opencart-14
[3] https://www.iveri.co.za/docs/virtuemart-15
* Authorisation Reversal *
*
Unreserve the funds previously reserved on the cardholder’s account.
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 = "
Batch is a payment solution that allows for bulk payment uploads using the iVeri system. It enables a merchant to create and process large volume, card not present transactions.
Batch requires merchants to create a file in a specific format and to upload It securely to the iVeri Payment Gateway for processing. Alternatively, merchants can also use the Create Batch function to manually create batches for uploading and processing. iVeri automatically creates the batch in the required format.
Batches are uniquely identified and can be set up to be processed on a date in the future. This is ideal for month ends that fall on a weekend or a public holiday.
Batch merchants are able to return to iVeri Back Office and view the status of their batch once it has been processed.