* View – Transactions History *
**
* Purpose *- To view a list of all transactions performed for a selected Date or Period.
* Action: * In the menu bar, Mouse over mPress, Transactions, View, Transaction History. Click on the Application ID you wish to view Transactions.
If you only have one Application ID, this page will NOT be displayed, and you will be automatically taken to the Choose Date/Period page. Select the Date or Date range and click on Search. This will bring up the list of ALL transactions performed for your selection.
Choose a specific Application ID
Choose a date range to start your Search
* Action *: Allows you to get details pertaining to a specific transaction – available when clicking on the actual transaction detail.
Once edit is selected click on submit to continue th
Authentication - Manage client certificate* ** Certificate Expiry and Dependency on Intermediate CA:
Certificate Expiry and Dependency on Intermediate CA: Server Certificate Expiry: A server certificate has a specific validity period, typically ranging from one to two years. This expiry date is hard-coded into the certificate at the time of issuance by the Intermediate CA. When the server certificate reaches its expiry date, it is no longer considered valid, and a new certificate must be issued to maintain secure connections. Dependency on Intermediate CA: The server certificate's validity also depends on the validity of the Intermediate CA that issued it. If the Intermediate CA's certificate expires before the server certificate, the server certificate will no longer be trusted, even i
Users
– Certificates - Manage server certificates*
**
Purpose * – This certificate is auto generated and is used as an internal iVeri certificate.
Transactions
– View- Transaction History*
Purpose * - To view a list of all transactions performed for a selected Date or Period.
Action: * In the menu bar, Select Enterprise, Transactions, View, Transaction History. Click on the Application ID you wish to view Transactions.
If you only have one Application ID, this page will NOT be displayed, and you will be automatically taken to the Choose Date/Period page. Select the Date or Date range and click on Search. This will bring up the list of ALL transactions performed for your selection.
Choose a specific Application ID
Choose a date range to start your Search
Action: * Allows you to get details pertaining to a specific
transaction – available when clicking on the actual transaction detail.
Transaction – Subsequent Transaction *
**
Purpose * - To take further action on a transaction which has already been successfully processed. You can convert an Authorisation to a Sale or process a sale Refund.
Action: *
Click on the appropriate Application ID in which you can view transactions that have been processed. Once the transactions details are displayed you, perform refunds, or do a debit
Action: *
Select the Date on which the original transaction took place from the drop down menu or select a period if you are not sure of the exact date and click on Search. This will bring up a summary list of all the transactions which match your search selection.
Action: *
Scroll through the summary list until you find the transaction you want to take the action on. To make sure that it is the
*
*
* Parameter description ***
Command *
Authorisation *
Debit *
Credit *
AutohorisationReversal *
Void*
GetData*
Cancel*
GetHMAC*
GetSystemInfo*
Parameter*
In*
Out*
In*
Out*
In*
Out*
In*
Out*
In*
Out*
In*
Out*
In*
Out*
In*
Out*
In*
Out*
Description*
AcquirerCode
O
O
O
O
O
The Acquirer ISO code returned for this transaction. Note that the success or failure of this transaction MUST be determined by the Result Code and NOT by the AcquirerCode nor the AcquirerDescription. This is only made available as extra information and may not exist in all response.
AcquirerDescription
O
O
O
O
O
The Acquirer ISO description returned for this transaction. Note that the success or failure of this transaction MUST be determined by the Result Code and NOT by the AcquirerCode nor the AcquirerDescription
Example Message Format *
**
Network Topology**
The generic solution is premised on the following network topologies and depends on whether or not the Indigo Server and/or the POS Server, if it exists, are located inside or outside of the merchant’s location.
At the point that a payment by the customer must be made the POS Till or POS Server will, using the protocol described in this document, contact the Indigo Server which will control the appropriate device to prompt for payment from the cardholder. Once the required card details have been collected on the device the Indigo server will process the transaction to the iVeri Gateway before returning a response to the POS Till or POS Server which will then be able to close the invoice created and indicate to the cashier at the POS Till that the invoice has been paid.
I
How to measure the network performance *
**
The following commands should be executed on the Indigo server and the destination should be the connected Devices. If there is any variation from a network point of view between the location of the various devices connecting to an Indigo Server, then they should be tested separately.
Windows
PS C:\Users\roland> ping -n 1000 -l 512 192.168.128.14
Pinging 192.168.128.14 with 512 bytes of data:
Reply from 192.168.128.14: bytes=512 time=1ms TTL=63
Reply from 192.168.128.14: bytes=512 time<1ms TTL=63
Reply from 192.168.128.14: bytes=512 time<1ms TTL=63
Reply from 192.168.128.14: bytes=512 time<1ms TTL=63
.
.
.
Reply from 192.168.128.14: bytes=512 time<1ms TTL=63
Reply from 192.168.128.14: bytes=512 time<1ms TTL=63
Reply from 192.168.128.14: bytes=512