*
*
* JSON Request *
**
{
"Command": "GetData",
"DeviceSerialNumber": "81546628",
"Prompts: ["05","4D"]
}
This content is called the “IYS” General Merchant Guide, This Learner guide is aimed to provide an overview of the functionality available on the IYS Merchant interface and how merchants would navigate the platform when setting up their own store.
The Guide covers the Back End System that will be utilised by the merchant when setting up their online store and the essential configurations that a merchant must have completed to properly onboard themselves as participants on the IYS Website or App store.
JSON Request *
**
{
"Command": "GetHMAC",
"DeviceSerialNumber": "81535719"
}
Refund of a previously successful Sale Transaction *
Now that we have a grasp of the process and the parameters required for a new BIN request, let's delve into the process of amending or updating an existing BIN.
Navigation Path:*
From the main menu select:
Systems > iVeriDB BIN > Local BIN*
1. Capture the BIN number in the search bar provider. Run the search.
The information related to the BIN will populate.
2. To amend the BIN, select the ‘Edit’ tab.
3. The general information tab will populate with information relating to the BIN.
Since this is an existing BIN you are amending or updating, the BIN number cannot be edited, which is why it appears greyed out.
Update and amend the applicable parameters based on the requested amendments or updates.
The most common parameters that are requested to be amended are ‘Card Number Length’ and ‘Car
JSON Request *
**
{
"Command": "Debit",
"DeviceSerialNumber": "81546628",
"MerchantReference": "Roland20190212.2",
"Currency”: “ZAR”,
"Amount": 1002,
"BudgetPeriod" : 0,
"CashAmount": 0,
"Terminal" : "Roland"
}
JSON Response *
**
{
"MerchantReference": "Roland20190212.1",
"Amount": 1001,
"CardAcceptorID": "1732668",
"AuthorisationCode": "228849",
"Product": "Indigo",
"TransactionDateTime": "2019-02-12 08:23:02",
"DeviceSerialNumber": "81546628",
"MerchantTrace": "292737.287655782251",
"Result": {
"Description": "Approved",
"Code": "0"
},
"DisplayAmount": "R 10.01",
"OriginalMerchantTrace": "292732.287654448218",
"TransactionTypeDescription": "Purchase",
"MerchantName": "ArchRetail",
"Command": "Debit",
"Version": "0482.01",
"TransactionIndex": "{B4767088-68BC-40FD-A4A3-695B0822BF18}",
"AcquirerReference": "01431:09014049",
"PAN": "4923........1826",
"TransactionCertificate": "{8a80fe66-4032-4cd9-b9f6-763762417e46}"
}
Appendix F – Reconciliation *
**
The Indigo Server as well as the iVeri Gateway operates in Host Settlement rather than Terminal Settlement mode which means that a transaction is settled in the cycle that the Host is in when a transaction arrives at the Host. The cycle into which a transaction’s settlement will fall is allocated at the time of the transaction and returned in the AcquirerReference number which is a composite field consisting of the Settlement Cycle Number and the Transaction Trace assigned by the Acquirer.
For the Integrator to be able to generate statements which match the bank statement the integrator needs to produce reports based on the Settlement Cycle number received from Indigo at the time of the transaction. By doing this the value of the settlement deposited into t
* What is IYS? *
Iveri has partnered with an eCommerce 3rd party that specializes in the creation of applications (i.e. mobile and website) that enable merchants to be able to display their goods and services they are selling in order to receive payments (i.e. online payments). Merchants will be able to do this through the use of an App that was created and renamed for iVeri, called IYS – Increase Your Sales.
Utilizing the designated API, it provides merchants the ability to set up their online stores to be able to receive payments based on what they are actively selling, allowing them to categorise and display what they want to present to their end customers.
*Co-partnership with iVeri*
The eCommerce 3rd Party has partnered with iVeri to enable their merchants to be able to implement this