Minimum development checklist

This page outlines the items a POS product must implement to complete a minimum integration. It should be used as a checklist for POS developers to know what they are required to build.

For more detailed scenarios see the certification test suite.

Pairing

  • The POS must send the correct POS Vendor Id and POS Version through to the EFTPOS terminal, and increment the POS Version once a new build is created
  • The POS can be paired and unpaired with the EFTPOS terminal successfully
  • User can accept or decline the hmac code during pairing
  • When the POS is in a paired connecting state the IP address is editable to the user
  • The pairing screen includes a "Save" button for EFTPOS address and POS ID
  • When paired and connected, and the network disconnects, the connection status updates to paired connecting
  • When unpairing on the POS the user is prompted to unpair on the terminal (see UI Guide)
  • The POS handles terminal instructed key rolling (available in 'enter' + 3 menu)
  • The connection between the terminal and the POS should remain persistent
  • Pairing secrets should not be exposed while pairing, unpairing or rolling the keys
  • The POS must have the option to pair using an automatically generated EFTPOS Address

Transactions

  • POS can process purchase, refund and MOTO transactions
  • POS must support Australian Dollars (AUD)
  • POS prompts user to accept or decline when a signature transaction is initiated
  • If a transaction is declined the sale needs to remain open
  • A user can cancel a transaction from the POS
  • The POS can handle and report correctly on terminal based surcharging
  • Hospitality POS systems need to be able to handle and report correctly on terminal based tipping
  • The pos_ref_id should be unique for each transaction. Retrying a transaction (eg if the PIN is invalid, signature declined etc) should generate a new pos_ref_id

Transaction recovery

  • If there is a network disconnection during a transaction the POS can recover
  • In the event that the POS cannot recover a connection (or does not know the outcome of a transaction) the user is given the option to override as paid, retry or cancel

Receipt printing

  • The POS should provide both merchant and customer EFTPOS receipts.
  • In the event of a transaction that requires a signature, the POS can print the merchant copy and, once the signature has been accepted, print a customer copy

Settlement

  • The POS offers the user the ability to settle the EFTPOS terminal through the POS

Logging

  • The POS should make the mx51 spi.log available for troubleshooting purposes