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.
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": "AuthorisationReversal",
"DeviceSerialNumber": "81546628",
"MerchantReference": "Roland20190212.4",
"Amount": 1004,
"OriginalMerchantTrace": "292741.287656655810"
}
Below is a list of mobile applications that support the scanning of MauCAS QR code:
MyT by Mauritius Telecom Blink by Emtel POP by Bank One Juice by MCB WithMe by Maubank MoFinans by Cim (Not yet launched)
*/*The listed mobile applications above may update/*. It is therefore imperative that merchants refer to their Acquirer in Mauritius for the update list.
Point 1.
Point 2.
Point 3.
Point 4.
IYS - General Merchant Guide
**