Frequently Asked Questions
What does "Integrated Receipts are mandatory" mean?
If the Point of Sale application supports printing receipts, then it is mandatory for the slip generated by the Point of Sale application to include the data that would normally be printed by the EFTPOS Terminal. It is mandatory for compliance/regulation reasons.
If the Point of Sale application does not have any receipt printing capabilities, then it is obviously not mandatory to include anything.
The receipt data to be included will come in the
data.Receipt field of the Transaction API Response.
This is further explained in the Interpreting the Transaction API Response page.
Does SmartConnect support Multi-Merchant EFTPOS Terminals?
Yes, SmartConnect does support multi-merchant EFTPOS Terminals, assuming that the terminal client supports it (the majority of Smartpay's fleet will have this support).
From the point of view of SmartConnect, Multi-Merchant is literally having two pairings for the two different merchants, on the same device.
When requesting a paring code in the Pairing Process, the EFTPOS device will ask for which merchant this pairing code is requested for.
From that point onwards, the pairing process is exactly the same as in the "single-merchant" scenario.
The Point of Sale application needs to provide two separate Register IDs and essentially provide a mechanism in the application for the user to select which merchant to use for the Transaction request, and provide the correct corresponding Register ID to the Transaction request afterwards.
Can one Register be paired to Multiple devices at the same time?
The short answer is yes, it can. But, the relationship needs to be managed appropriately by the Point of Sale application.
Conceptually, as described in the Pairing Process page, the pairing is a relationship between one Register and one payment acceptance device.
However, if the Point of Sale application can support multiple Register IDs and manage the associated with having one Register ID pointing to one device, then the desired outcome can be achieved.
In other words, the Point of Sale application will need to have a concept of a "Device" which is able to store a unique ID (which would be the Register ID from the point of view of SmartConnect) associated to that device, for the purpose of pairing and sending transactions.
It then becomes the responsibility of the Point of Sale device to provide a functionality to the user to select which device to use in each transaction, and send the correct corresponding ID in the request.