Integration Features

A number of the below terminal features will need to be configured via mx51 Payments. If you would like a feature enabled on your test terminal please direct this request to your mx51 Payments contact.

Supported Features

Pairing & unpairing: This is the creation of a set of shared encryption secrets between the POS and the EFTPOS terminal, and it’s required before any other communication can take place. The process needs to be triggered on both the POS and EFTPOS terminal to begin and requires the user to accept a matching code on both devices to complete the pairing process. Unpairing is the dropping of these secrets.

Integrated Settlement: A settlement is an instruction by the EFTPOS terminal to the bank to finish its day's trading. The merchant will receive all funds prior to the settlement instruction in the next deposit. The POS has the option to store the settlement information for reconciliation.

Integrated Settlement Enquiry: This feature is a request to the terminal to return the current or a previous date's settlement report. It allows the user to request a settlement report from the EFTPOS terminal without requiring a settlement. The request will trigger the terminal to prompt the merchant to select the current day or another date and then return the report to the POS.

Transaction Modal UI: Spice will handle the UI for all transactions. It is required for the POS to send an API transaction request, and Spice will return the transaction result. Spice will handle the following transaction modal UI:

  • Purchase; And all events related to Purchase
  • Refund
  • Signature Transaction
  • MOTO
  • Transaction Recovery
  • Pre-Authorisation

Terminal-based Printing: ability to enable printing from the EFTPOS terminal rather than the POS.

Signature Handle Event: By default, Spice will handle Signature transactions within the Transaction Modal UI. By enabling 'Confirm customer signature on Terminal' within Spice device settings, the terminal will now prompt the operator to accept or decline transactions from the EFTPOS device. Refer to Signature Transactions for more information.

Auto close of Dialog windows: Option to auto-close the transaction alert window after 2 seconds, On or Off.

Transaction Theme: Choose between Light or Dark theme for the transaction alert window.



Transactional

Purchase & refund: A positive/negative transaction driven from the POS to Spice. This includes displaying errors to the user and POS-based signature acceptance/decline functionality.

MOTO: This is a card not present transaction: used when a customer’s card is not physically available to a merchant to complete a transaction. The POS must flag a transaction as MOTO and the card details of the customer must be entered manually into the EFTPOS terminal.

Signature Transaction: In the event a signature is required to verify a transaction the POS will receive a response with the signature receipt to print. Spice will display a signature Accept/Decline message to the user. The POS will then need to query Spice to obtain the result. More information on this workflow can be found here.

Transaction Recovery: In the event that the POS or Spice crashes a recovery workflow is required. Information on how to implement this recovery can be found here.

Pre-Authorisation: This feature is a set of requests that manage the authorisation from a customer to the merchant to debit the customer’s card in future. It is used in situations where the future cost of goods and services is unknown or as a security/deposit for goods and services currently being provided. Examples include bar tabs, hotel check-ins and vehicle rental.

Pay at Table: This feature is designed for hospitality dining environments but can be implemented for other uses. Pay at Table changes the integration model by allowing the EFTPOS terminal to initiate a transaction. When Pay at Table is initiated on the EFTPOS terminal it will send a request to the POS to return a table total or held sale. The cardholder can then complete payment on the EFTPOS terminal and once completed the EFTPOS terminal will update the POS to close the table or sale.

For detailed information on Pay at Table please see the feature page Pay at Table.

Spice Configurations

Enabling Pay At Table: Pay at Table



POS driven features

Ping Test: Prior to each transaction, the POS is required to use the HTTP Ping end-point to ensure Spice is running and paired. Information on how to implement the ping test can be found here.

POS-based Cashout: Cashout is a transaction type that requests funds from the customer's bank to be withdrawn and then those funds are to be provided by the merchant. Cashout is a unique transaction type and needs to be implemented independently of a purchase transaction. This feature allows the merchant to enter the Cashout amount into the POS and then request a Cashout transaction for that total to the EFTPOS terminal. Note: Cashout is only available when selecting Savings or Cheque.

POS-based Purchase with Cashout: This transaction type combines a purchase and a Cashout transaction into a single request. It is used when a customer requests to withdraw funds from the merchant while completing a purchase. The Cashout amount is entered into the POS along with the purchase. Cashout with purchase is a unique transaction type and needs to be implemented independently of purchase and Cashout. Note: Cashout is only available when selecting Savings or Cheque.

POS-based Surcharge: If a POS supports surcharges this value can be passed through to the EFTPOS terminal in a separate field.

POS-based Tipping: This feature allows tips entered into the POS to be included with the purchase request to the EFTPOS terminal.

Suppress Merchant Password (MOTO and/or Refund): During a MOTO or Refund transaction the merchant is required to provide a password on the EFTPOS terminal. The password requirement can be suppressed as part of the transaction message from the POS. This is only recommended if the POS has implemented user roles.

Integrated Receipts: The EFTPOS terminal relies on the POS to print receipts and settlement reports from the POS printer.

Integrated Settlement: A request driven by the POS to settle the EFTPOS terminal via Spice. A settlement is an instruction by the EFTPOS terminal to the bank to finish its day's trading. The merchant will receive all funds prior to the settlement instruction in the next deposit. The POS has the option to store the settlement information for reconciliation.

Integrated Settlement Enquiry: This feature is a request to the terminal to return the current or a previous dates settlement report. It allows the POS to request a settlement report from the EFTPOS terminal without requiring a settlement. The request will trigger the terminal to prompt the merchant to select the current day or another date and then return the report to the POS.



Terminal driven feature

Terminal-based Surcharge: This feature automatically adds a predefined surcharge to a purchase transaction at the time the card is presented to the terminal. The POS is required to accept the surcharging field in the response back from the EFTPOS terminal.

Terminal-based Tipping (Hospitality Only): This feature allows tips entered into the EFTPOS terminal once a purchase request has been sent from the POS. The POS is required to accept the additional tipping field in the response back from the EFTPOS terminal.

Terminal-based Cashout: This feature asks the cardholder to enter their desired Cashout amount into the EFTPOS terminal at the time of completing a purchase. The POS is required to accept the additional Cashout field in the response back from the EFTPOS terminal. Note: Cashout is only available when selecting Savings or Cheque.