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.
* * The following section covers the details of POS Device integration (particularly PIN based transactions). PIN transactions are encrypted either using Triple DES DUKPT or Triple DES Master/Session encryption architecture. The combination of Acquirer and type of device used determine the encryption architecture chosen.
iVeri provides facilities where PIN transactions can be process in either mode Live or Test.For security reasons, a key cannot be used in both modes Live and Test. Therefore, a device is either loaded for mode Test or mode Live.
A Device that is to be used for mode Live must be injected with a key within an iVeri Trusted Centre using the appropriate encryption architecture.A Device that is to be used for mode Test may be injected by a merchant, or within the Trusted https:
JSON Response*
**
{
"MerchantReference": "Roland20190212.5",
"Command": "Void",
"DeviceSerialNumber": "81546628",
"Result": {
"Description": "Void Approved",
"Code": "0"
}
JSON Request *
**
{
"Command": "AuthorisationReversal",
"DeviceSerialNumber": "81546628",
"MerchantReference": "Roland20190212.4",
"Amount": 1004,
"OriginalMerchantTrace": "292741.287656655810"
}
JSON Response *
**
{
"MerchantReference": "Roland20190212.1",
"Amount": 1001,
"CardAcceptorID": "1732668",
"AuthorisationCode": "228849",
"Product": "Indigo",
"TransactionDateTime": "2019-02-12 08:31:36",
"DeviceSerialNumber": "81546628",
"MerchantTrace": "292738.287656296274",
"Result": {
"Description": "Approved",
"Code": "0"
},
"DisplayAmount": "R 10.01",
"OriginalMerchantTrace": "292732.287654448218",
"TransactionTypeDescription": "Refund",
"MerchantName": "ArchRetail",
"Command": "Credit",
"Version": "0482.01",
"TransactionIndex": "{B4767088-68BC-40FD-A4A3-695B0822BF18}",
"AcquirerReference": "01431:09014052",
"PAN": "4923........1826",
"TransactionCertificate": "{8a80fe66-4032-4cd9-b9f6-763762417e46}"
}
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”
}
Point 1.
Point 2.
Point 3.
Point 4.