Merchants have limited counter space but need a payment solution
Merchants without a brick and mortar location need to be able to process payments with a loyalty + CRM feature
Restaurants owners want to be able to take a payment terminal directly to the table or outside for curbside pick up
Merchants with unreliable internet want to be able to process payments effortlessly
Our organization wants to lower hardware costs while increasing our quality bar
Early UX Flow explorations
We needed a solution that allowed for consumers to check-in or skip the check-in process
We needed clear communication for who each screen was intended for, hopefully avoided a hot potato experience.
Solution also required reward redemption for consumers
Early UI explorations based of Cpax screens.
Most of the consumer facing screens were already designed. What we needed was UI specially for the merchant and for the interaction between the consumer and merchant.
What did reward redemption look like on a single device solution?
What would checking-in look like on this device?
Would we change the UI depending on who was handling it (more consumer or merchant UI?)
The trickiest part of the experience…
This part of the experience requires both the consumer and merchant to interact with the device.
The consumer should select the reward or at least know the options available to select
The merchant must approve the reward and apply the discount
MVP solution for Upax
Error states for Upax
Manual Entry Payment
An MVP requirement for this product was allowing payment through manual entry.
Batching
Another feature required was batching - the ability for a merchant to run a report on any amount of days to get a sales summary. This was a precursor before Transaction History.
Transaction History
Prototype