JSON Response*
**
{
"MerchantReference": "Roland20190212.5",
"Command": "Void",
"DeviceSerialNumber": "81546628",
"Result": {
"Description": "Void Approved",
"Code": "0"
}
* 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 Request *
**
{
"Command": "AuthorisationReversal",
"DeviceSerialNumber": "81546628",
"MerchantReference": "Roland20190212.4",
"Amount": 1004,
"OriginalMerchantTrace": "292741.287656655810"
}
Merchant Take on Process - IYS
**
User Group Capture *
Action: *Log on to: iVeri Admin website, navigate to Merchant Profile > select Create
1. Capture all the details on the form.
2. Ensure that the Distributor (Which is iVeri) is set.
3.“Aggregator” option is used should a merchant belong to a listed Payment Aggregator, and this is because the merchant agreement is between the acquirer and the Aggregator. If “yes” assign the appropriate Aggregator from the drop down.
Note: If the merchant does not belong to an Aggregator, the Aggregator field must be left to “None”
Once details are populated, Click on Create.
Important Note:
This Association of an Integrator or Aggregator of a merchant is standard across all products, and across all Take-On Processes This will generate the iVeri Merchant
JSON Request *
**
{
"Command": "Credit",
"DeviceSerialNumber": "81546628",
"MerchantReference": "Roland20190212.1",
"Amount": 1001,
"OriginalMerchantTrace": "292732.287654448218"
}
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
Appendix G – Postman *
**
Developers may want to test the protocol independent of their implementation by making use of Postman.
When configuring Postman, the Headers must have an additional attribute added to set Content-Type to the value “application/json” as shown below.
The Body should be set to the JSON as defined in this document to execute the command that is being tested as shown below:
The result received in the response is displayed in the pane below the request. In this case the device 20605360 is not online so the result informs us of that.
IYS - Cardinal Backoffice Configuration
**
Merchant Profile Login *
Action
LOGIN
Log into the IYS Cardinal BackOffice. Using URL; https://www.backoffice.iys.iveri.com/
Insert your log in credentials.
1.Navigate to “Merchant Profile” and select “Merchant Profile Login” to access the merchant’s profile
2.Insert the Merchant profile credentials and select Go
3.Select the merchant Profile
This screen will appear.
This indicates that you have logged in as the merchant in cardinal.
USER Creation
4. Navigate to User >> Capture
This is to capture the user of the actual IYS Store.
Complete the users information we are creating and select Capture.
/Please Note!/*
The created User will receive an email of their password that was created for this particular merchant(i.e. Merchant Profile Number & the
JSON Response *
**
{
“Command” : “GetData”,
“DeviceSerialNumber” : “81546628”,
“Data” : “690825518708425”
}