JSON Request *
**
{
"Command": "Cancel",
"DeviceSerialNumber": "81546628"
}
JSON Response *
**
{
“Command” : “GetData”,
“DeviceSerialNumber” : “81546628”,
“Data” : “690825518708425”
}
JSON Response *** {
"GatewayInfo": [
{
"Status": "Up",
"StatusSince": "2019-02-12 03:22:45",
"GatewayDNS": "https://portal.iveri.net%22%2C/
"Name": "Gateway Provider",
"Latency": 124
},
{
"Status": "Up",
"StatusSince": "2019-02-12 03:22:47",
"GatewayDNS": "https://portal.iveri.net%22%2C/
"Name": "NBPostilion NBSouthAfrica Gateway Provider",
"Latency": 93
}
],
"DeviceInfo": [
{
"Status": "Disconnected",
"Transactions": 11,
"LastTransactionEnd": "2019-02-11 14:38:51",
"LastTransactionStart": "2019-02-11 14:38:30",
"Version": "IPP350 - RA12105",
"ConnectedSince": "2019-02-11 13:13:50",
"DeviceSerialNumber": "81528455",
"SocketAddress": "192.168.128.85:1030",
"Latency": 312
},
{
"Status": "Idle",
"Transactions": 0,
"LastTransactionEnd": "",
"LastTransactionStart": "",
"Version": "IPP350 - RA11
Appendix A *
**
The prompts are specific to devices so depending on which devices are attached to the Indigo server will determine which prompts are used. These prompts are, in general, loaded onto the device at initialisation so if this has not been done then prompts will not be supported. There is a hardcoded default prompt so that if the Index used from the list below does not happen to be loaded on the device or does not exist on the device then this prompt will be used as a generic request for data to be entered.
* Batch Upload File XML Specification *
**
DiVert Batch Upload File XML Specification *
**
Divert Batch Upload *
This section describes the contents of the Divert batch file uploadable in Backoffice with Command “DivertUpload”. The Divert Backoffice user guide on how to upload the Divert Batch XML file in Backoffice. The same functionality can be implemented using Enterprise API.
The Divert Batch Upload File has the following XML tags:
V_XML Version="2.0" Direction="Request">
<DiVert Version="1.0" Command="DiVertUpload" Count="" Amount="">
<Date></Date>
<Filename></Filename>
<CreateTransactionUrl></CreateTransactionUrl>
<DiVertItem ApplicationID="" Mode="test" Command="Debit">
<Amount></Amount>
<Currency></Currency>
<OrderDescription></OrderDescription>
<MerchantReference></MerchantReference>
<AllowBudgetPeriod>false</AllowBudgetPe
Introduction *
**
This document describes the XML specification of the Batch Upload File and the Batch Result File. The Batch Upload File can be uploaded either from the iVeri BackOffice or by using the iVeriClient software (the latter applies to Enterprise merchants only). The Batch Result File can be downloaded through these same mechanisms.
Note that the Batch Result File is available for download only after processing of the batch has completed. Note that the Reconciliation Status of the individual transactions might not yet be updated, since the reconciliation process only occur the day after processing.
The XML specification of other downloadable XML files is described in the “iVeri Download Files XML Specification” document available from the iVeri website.
* Cardinal Posport Indigo Release Notes V 20231026 ***
The release notes contained in this document are available in iVeri’ s repository in production and can be installed on any Cardinal and or indigo installation on a case-by-case bases as agreed with Customers and or Integrators.
*/ Whats new /*
* PosPort *
"Single Tap" feature has been updated to cater for scenarios where the issuer does not support “Single Tap and Pin”. In such scenarios, the cardholder will be requested to dip the card, eliminating the need for PIN collection. An improvement on the reversal of an authorization has been introduced. Previously, authorizations reversed on a different day presented a challenge, but now the process has been updated so that these authorizations can be efficiently processed as "Authoriza