Standalone

If the PAY.POS is used standalone, the merchant can enter a description, a reference and an amount. If the payment is started and PAY.POS is activated it reads the card data, encrypts the data. If a PINcode is needed, it will ask for the PIN and encrypt that as well. It sends the data to the Transaction Gateway Unit where the transaction is routed via the different schemes to the issuing bank where the payment is completed.

PAY.POS status icon

Connected - Standalone

The terminal is connected and ready to accept payments

Connected - Cloud ECR

The terminal is connected and ready to accept payments locally or via the Cloud ECR solution

No network - Offline mode active

The terminal does not have an active internet connection, but offline mode is enabled. This means that it is able to accept payments, which will be processed once the terminal is back online. The terminal will attempt to process the payment once accepted.

No network - Offline mode deactivated

The terminal does not have an active internet connection and no fallback methods are activated. This means that the terminal will try to process the payment, but might fail and show an processing error

PAY.POS iOS - MAT mode

Since version 1.3.0, it is possible to accept offline transactions using your MAT mode. There are a few differences between the iOS MAT and Android MAT you must know before using it.

The first one, is that every MAT needs to be below the CVM limit (for most schemes in the NL, this is 50.00 or less). iOS MAT does not allow a pincode capture during offline mode, thus every transaction above CVM limit while MAT mode is enabled, will result in card read failures.

The other difference is that you either run PAY.POS in normal mode or MAT mode. Normal mode will try to process the transaction as you already are used to. When you switch to MAT mode, all transactions need to be below this CMV limit even though you are connected to the internet. PAY.POS will try to process all MAT as soon as possible (so if you are connected to the internet, it will immediately try to process the MAT). You can recognise if PAY.POS is in MAT mode by this banner on the main screen:

PAY.POS retry flow

With the release of version 1.3.12, we've added a specific retry flow. A short schematic drawing of this new flow is shown below

• If no networking issues occurred during processing, the transaction will be relayed directly
• If something happens during DNS resolving, connecting to PAY servers or uploading the request, PAY.POS will retry to upload the payment payload after 3 seconds
  • If the same issue happens during the retry, PAY.POS will show an error and stop attempting (unless you've enabled the Offline queue option)
• If the connection drops while PAY.POS is waiting for a response from the PAY servers, it will wait for 5 seconds and uses it's internal payment identifier to fetch the transaction status
  • If PAY.POS succeeds fetching the status, it will uses that status
  • If the PAY servers does not recognise the payment identifier, it will return an error which will be shown by PAY.POS
  • If a network issue happens while fetching the transaction status, PAY.POS will show a "networking issue" error