-
- Introduction
-
- Network Topology
- Latency, Jitter and Lost Packets
-
- How to measure the network performance
-
- Transaction Life Cycle
-
- REST Endpoints
-
- Parameter description
-
- Example Message Format
-
- Initial Transaction
-
- Authorisation
-
- JSON Request
-
- JSON Response
-
- Payment
-
- JSON Request
-
- JSON Response
-
- Followup
-
- Settlement of a previously successful Authorisation
-
- JSON Request
-
- JSON Response
- Refund of a previously successful Sale Transaction
-
- JSON Request
-
- JSON Response
-
- Reversal of a previously successful Authorisation
-
- JSON Request
-
- JSON Response
-
- Sale
-
- JSON Request
-
- JSON Response
-
- Void
-
- JSON Request
-
- JSON Response
-
- Cancel
-
- JSON Request
-
- JSON Response
-
- GetData
-
- JSON Response
-
- GetHMAC
-
- JSON Request
-
- JSON Response
-
- GetSystemInfo
-
- JSON Request
-
- JSON Response
-
- Appendix A
-
- Ingenico RA1 based devices
-
- Appendix B – QA Environment for Development and Certification
-
- Appendix C – Test Plan
-
- Appendix D – Receipt Requirements
-
- Appendix F – Reconciliation
-
- Appendix G – Postman
- Introduction
- Introduction
- Network Topology
- Network Topology
- Latency, Jitter and Lost Packets
- How to measure the network performance
- How to measure the network performance
- Transaction Life Cycle
- Transaction Life Cycle
- REST Endpoints
- REST Endpoints
- Parameter description
- Parameter description
- Example Message Format
- Example Message Format
- Initial Transaction
- Initial Transaction
- Authorisation
- Authorisation
- JSON Request
- JSON Request
- JSON Response
- JSON Response
- Payment
- Payment
- JSON Request
- JSON Request
- JSON Response
- JSON Response
- Followup
- Followup
- Settlement of a previously successful Authorisation
- Settlement of a previously successful Authorisation
- JSON Request
- JSON Request
- JSON Response
- JSON Response
- Refund of a previously successful Sale Transaction
- JSON Request
- JSON Request
- JSON Response
- JSON Response
- Reversal of a previously successful Authorisation
- Reversal of a previously successful Authorisation
- JSON Request
- JSON Request
- JSON Response
- JSON Response
- Sale
- Sale
- JSON Request
- JSON Request
- JSON Response
- JSON Response
- Void
- Void
- JSON Request
- JSON Request
- JSON Response
- JSON Response
- Cancel
- Cancel
- JSON Request
- JSON Request
- JSON Response
- JSON Response
- GetData
- GetData
- JSON Response
- JSON Response
- GetHMAC
- GetHMAC
- JSON Request
- JSON Request
- JSON Response
- JSON Response
- GetSystemInfo
- GetSystemInfo
- JSON Request
- JSON Request
- JSON Response
- JSON Response
- Appendix A
- Appendix A
- Ingenico RA1 based devices
- Ingenico RA1 based devices
- Appendix B – QA Environment for Development and Certification
- Appendix B – QA Environment for Development and Certification
- Appendix C – Test Plan
- Appendix C – Test Plan
- Appendix D – Receipt Requirements
- Appendix D – Receipt Requirements
- Appendix F – Reconciliation
- Appendix F – Reconciliation
- Appendix G – Postman
- Appendix G – Postman
Introduction
Introduction
Network Topology
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.
Illustration 1 shows where all the POS Tills are able to connect directly to the Indigo Server locally and the POS Till manages the creation of an invoice which needs to be paid by a customer. In this scenario there is no POS Server and the POS Tills effectively act independently of each other.
Illustration 2 shows where all the POS Tills are able to connect directly to the remote Indigo Server and the POS Till manages the creation of an invoice which needs to be paid by a customer. In this scenario there is no POS Server and the POS Tills effectively act independently of each other.
Illustration 3 shows where the POS Tills connect directly to the POS Server which, in turn, connects to the local Indigo Server. In this case the POS Server acts on behalf of the POS Tills, creating the invoice which needs to be paid by a customer and connecting to the Indigo Server on behalf of the POS Till which is performing the transaction. In this scenario the POS Server co-ordinates the creation of invoices between the POS Tills.