Cardinal Posport IndiGo

Cardinal Posport IndiGo * ** 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.

Cardinal Posport IndiGo V 20230323

Cardinal Posport Indigo Release Notes V 20230323 *** 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  /* Indigo Ingenico * A change is implemented to make Ingenico devices reboot once a day to comply with PCI requirement. The default time is set to be at midnight. PosPort * Device Status is included as part of the data synchronized from Cardinal into MIS allowing for a better filtering in reports generated from MIS. Allowances that make it possible to enable "CashAdvance" in parallel with "Sale" transaction type have been made SMYL Loyalty  * As part of the loyalty offering on the N700 device, enabli

Query Code * ** Function: Query a code that has been created. Query Code Parameters * Request Parameter Description MasterPassAction Mandatory, The action to perform. MasterPassMerchantID Mandatory, The merchant id as captured on MasterPass. MasterPassCode Mandatory, The result code that must be queried Response Parameter Description MasterPassAction The action that was performed MasterPassShortDescription Short decription linked to the code MasterPassCodeExpiryDate Date until the code is valid. This is in epoch time. MasterPassMerchantName The name of the merchant as captured on MasterPass Amount Amount linked to the code. Currency The currency is tied to the merchant setup. MerchantReference Linked to the code. Query Code – REST Sample * Request Response { "Version" :  "2.0" , "Certifica

Generic POS Channel API Developers Guide

Introduction *** 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. Net

Generic POS Channel API Developers Guide

Generic POS Channel API Developers Guide * **

Transaction Life Cycle

Transaction Life Cycle * ** The following diagrams describe how related stages can be executed during the life cycle of a transaction. There are three diagrams to illustrate the three possible starting points that a transaction life cycle can start from and, once it has started, what follow-up transactions can be performed on them. The data which links transactions together is the MerchantReference which is generated by the POS Till and/or MerchantTrace which is generated by the Indigo Server and returned in appropriate response messages to the POS Till. There is a subtle distinction between a Refund (command = Credit) and Payment (command = Credit); a Refund is the term used when returning money previously taken from a cardholders account by a Sale (command = Debit). A Payment is not link

Void

Void ***

Payment

Payment * **

Reversal of a previously successful Authorisation

Reversal of a previously successful Authorisation * **

Appendix B – QA Environment for Development and Certification

Appendix B – QA Environment for Development and Certification * ** During the development and certification phases of an integration project the Indigo server will be located within iVeri's QA environment and a Merchant Profile for the Integrator performing the integration must be created on iVeri's QA Gateway as well as on the iVeri QA Indigo Server and the resulting credentials distributed to the Integrator. This must be performed by iVeri Support who can be contacted at assist@iveri.com. Please make sure in all communication with Support that they must deal with QA Indigo and the QA Gateway. Network wise, the Integrator must ensure that the POS/Till system which will be communicating to the Indigo server using the Generic POS Channel protocol has outbound internet access to the iVeri QA