** * Payment Features * ** Depending on the acquirer involved, iVeri Lite has the capacity to offer the following * payment methods * :
Card:
VISA MasterCard AMEX Diners UPI Mobile Money
EcoCash M-Pesa Additional payment methods:
MasterPass Visa Checkout Visa Account Funding Transactions Mastercard Funding Transactions Account-to-Account Transfer:
Ozow *Other functionalities available:*
*3DSecure: *iVeri Lite, being an e-commerce product, allows for 3DSecure protocol for payer authentication in online transactions, if configured accordingly.
To learn more about 3D Secure, visit None [1] this page . *Fraud Management* *Transaction history reporting* *Merchant Portal - BackOffice*: Merchant Portal includes features that are merchant-specific such as reporting, payment pa
* iVeri Lite Process Flow * **
iVeri Lite requires very little integration and is aimed at Internet merchants who have limited technical resources. Lite transactions are processed on a web site and secured via an SSL certificate without the merchant having to buy SSL since iVeri lite takes care of it on their behalf. Although ideal for websites with small catalogs, iVeri Lite still provides a powerful processing engine.
*/ Process Flow /*
This diagram illustrates the flow of events of an iVeri Lite transaction:
iveri%20Lite%20flowchart%20-%20horizontal%20-%202024 [1]
/*Process Flow Description:*/
(1) The cardholder is at the point in the purchase process where the basket has already been selected and he is now on the brink of paying for it. The website thus knows the price of the basket, t
Release Notes *
**
Release Notes for every iVeri product.
Web Service implementation ***
All methods provided by the web service return a V_XML formatted response. The GetPinBlock method is the only exception. For card present transactions, the GetPinBlock method will return a PINBlock data structure.
The V_XML request and response format is defined by the V_XML.xsd schema, which can be downloaded from https://portal.nedsecure.co.za/schemas/v_xml/7.0/v_xml.xsd [1] Client code must check the respective Result fields to determine if the web service method was successful or not. For a client to call the execute method the client certificate ID must be provided with the HTTP Request
Webservice Gateway Address**
SOAP
Webservic EndPoints
Purpose
Usage
Live and Test: */iVeriWebservice/Service.asmx
HTTP Method:* POST
Submit transactions to iVeri
Gatew
Parameter per Acton *
**
M
Mandatory
O
Optional
C
Conditional
blank
not relevant
Context
Parameter
Authorisation with PAN
Authorisation with Track2
Authorisation with VisaCheckoutCallID
Additional Authorisation with TransactionIndex
AuthorisationReversal with TransactionIndex
Debit with PAN
Debit with Track2
Debit with PIN
Debit with VisaCheckoutCallID
Debit with TransactionIndex
Credit with PAN
Credit with Track2
Credit with TransactionIndex
Void
Balance Enquiry with PIN
PAN Enquiry with PAN
PANToken Enquiry
PAN Enquiry with Track2
Ping
Get Device PIN Key
ThreeDSecureCheckEnrollment
ThreeDSecureValidateAuthentication
RequestForDebit
MasterPassQuickResponseCode
MasterPassPaymentNotification
DynamicCurrencyConversion
MultiCurrencyPricing
Core *
ApplicationID *
M *
M *
M *
M *
M *
M *
M *
M
Create Code *
**
Function: Generate a transactional code that can then be paid for by a cardholder. This code can be represented as a QR code, transferred using NFC or manually entered a device. The code can also be used as part of an In-App payment.
/Create Code Parameters/*
Request
Parameter
Description
MasterPassAction
Mandatory, The action to perform.
MasterPassMerchantID
Mandatory, The merchant id as captured on MasterPass.
MasterPassShortDescription
Mandatory, This will be displayed to the consumer at the time a code
is scanned. Length is 5 to 45 characters
MasterPassCodeExpiryDate
Optional. If this is empty the code will by default expire in 30
minutes from issue. If this value is 0 the code will never expire. This time
is specified in epoch.
Amount
Mandatory, To use a variable amou
* Latency, Jitter and Lost Packets* *
With the above four scenarios in mind the solution relies on the quality of the connections from the POS Till, POS Server and the Devices to the Indigo Server as well as from the Indigo Server to the iVeri Gateway. If any of these connections suffers from high latency or dropped packets the solution as a whole will not perform as required so it is imperative that the networks on which the solution is deployed have adequate bandwidth as well as that they have low latency and zero packet losses. This means that if the networks are shared with other equipment it is important to understand what that equipment is doing and when it is doing it so that it doesn’t impinge on the operational requirements of the Indigo Solution.
The interaction between the Devi
JSON Response *
**
{
"TransactionStatusInformation":
"F800",
"MerchantReference":
"Roland20190212.1",
"DisplayCashAmount":
"R 0.00",
"CardAcceptorID":
"1732668",
"AuthorisationCode":
"228849",
"Product":
"Indigo",
"TransactionDateTime":
"2019-02-12 08:00:48",
"DeviceSerialNumber":
"81546628",
"PANSequenceNumber":
"00",
"Result": {
"Description":
"Approved",
"Code": "0"
},
"CardholderName":
"22112016/P. ",
"CardHolderVerificationMethod": "410302",
"SignatureRequired":
"false",
"TransactionTypeDescription": "Authorisation",
"MerchantName":
"ArchRetail",
"TerminalVerificationResult": "0880008000",
"Version":
"0482.01",
"TransactionIndex":
"{B4767088-68BC-40FD-A4A3-695B0822BF18}",
"AuthorisationRequestCryptogram":
"5E3C53B0D0160098",
"TransactionCertificate":
"{8a80fe66-4032-4cd9
JSON Response *
**
{
"TransactionStatusInformation": "F800",
"MerchantReference": "Roland20190212.2",
"DisplayCashAmount": "R 0.00",
"CardAcceptorID": "1732668",
"AuthorisationCode": "229180",
"Product": "Indigo",
"TransactionDateTime": "2019-02-12 08:06:19",
"DeviceSerialNumber": "81546628",
"PANSequenceNumber": "00",
"Result": {
"Description": "Approved",
"Code": "0"
},
"CardholderName": "22112016/P. ",
"CardHolderVerificationMethod": "410302",
"SignatureRequired": "false",
"TransactionTypeDescription": "Purchase",
"MerchantName": "ArchRetail",
"TerminalVerificationResult": "0880008000",
"Version": "0482.01",
"TransactionIndex": "{00CD9C3B-A138-4E97-AE0D-3CAF4DDF9923}",
"AuthorisationRequestCryptogram": "D642677F6B64BB55",
"TransactionCertificate": "{8a80fe66-4032-4cd9-b9f6-763762