We were approached by ANZ to build an app to run on their new Android-based payment device called BladePay, that would integrate with the OrderMate POS system and effectively compete with other pay at table solutions in the market. Our app does exactly this, with an emphasis on driving better tips for the venue staff.
How does it Look & Work?
This is the landing screen for oPay. The staff will need to enter their WaiterMate PIN to proceed further into the app.
By pressing the Help icon in the top-right corner, a small settings screen will appear. If for whatever reason the app loses connection to the POS, this is the place where the user would troubleshoot that issue (perhaps guided by tech support).
On this screen we can see all open table accounts and bar tabs, where the user would select an account to make a payment on. This is the last screen that the wait staff will interact with before passing the device over to the customer.
Similarly to the login screen, pressing the cog icon in the top-right corner opens a similar settings screen will appear. Here the user can reconfigure the POS connection (the same as before), but also reauthorise the payment provider.
With ANZ, this can happen when the merchant changes their PIN over in their ANZ merchant portal, so we offer the ability to reauthorise the device.
You can reach this screen by pressing the "Previous Order" button at the bottom-right corner of the account selection screen. This will show details of the last completed transaction. We get this information directly from the card reader. This is useful if the payment device crashed or ran out of power during a payment, and you need to know if the payment went through or not.
This is the first screen seen by the customers in the restaurant. Once this screen has been reached, the wait staff will pass the device to the customers who will carry through the remainder of the process. If a customer is set on the account in the POS, their name will appear up with the table number.
If the user tries to go back from this screen, they'll need to enter their WaiterMate PIN. This prevents customers from trying to access other tables or bar tabs, and prevents them from accessing other app settings.
On this screen the customer can choose to leave a tip for the wait staff that will be added to their payment amount. The tip slider starts at 5%, and will fade out to grey the further towards 0% the slider is placed.
The further the tip slider is pushed to the right, the header colour fades into a strong blue. The customer can also enter a custom amount, if they wish. When the user is ready, they can press Confirm & Pay to start the payment process. At this stage, the payment provider (e.g. ANZ) takes over to do the payment.
Keep scrolling for animations!!
As the tip slider moves, it will latch to the nearest whole percentage, ignoring any decimal places for the sake of simplicity. When the user is happy, they can press Confirm & Pay to move onto the payment.
If the user enters a custom amount, this will then ignore the tip slider. If the user touches the tip slider, the custom amount gets cleared and the tip amount becomes the slider value again.
After a successful payment, the user is asked if they'd like either an SMS or email receipt. In a future release we may also support a physical receipt that would be printed at the POS.
If the user wants a receipt, they'll be prompted to enter their information. Otherwise, they'll be taken right to the next screen.
This is the final screen in the payment flow. Pressing the X in the top-right corner will land the user right back on the PIN entry screen, at which point the wait staff can collect the device back from the customer.
1. What exactly am I looking at...?
It's our new pay at table app for Android. Currently it runs only on ANZ's BladePay device.
2. Does it do split bill?
As of version 1.1.0, YES!
3. Will this be available for our other customers (i.e. non-ANZ) too?
Not right now, this feature is exclusive to ANZ.
4. When an account is in use by oPay, how does it look at the POS?
The account will show up as locked, just as if someone were accessing the table from another WaiterMate terminal.
5. What happens if the device loses WiFi?
Losing WiFi means losing connection to ServerMate. If this happens, any request to ServerMate will be put in a retry queue that gets dealt with quietly in the background. So in the circumstance where the BladePay device is too far from the WiFi to talk to ServerMate, the payment can still be completed over 4G and ServerMate will be notified as soon as the device is back in WiFi range.