Design
/
21 - 27 October 2025
Ojire Anywhere — Cash Payments
Designing a cash checkout flow with amount shortcuts, clear change calculations, and accessible receipts.
(Project details)
Company
Ojire
Role
UI/UX Designer intern
Year
21 - 27 October 2025
Making cash checkout clear
I designed the cash payment flow for Ojire Anywhere, covering cash entry, payment confirmation, change, receipts, and transaction records.
The flow helps merchants enter the amount received, check whether it covers the total, and see the change to return before completing checkout.

The design challenge
Cash checkout requires merchants to keep track of three amounts: the total due, the cash received, and the change owed.
My design focused on keeping these amounts easy to distinguish, while supporting both exact payments and payments that require change.
Entering cash received
Merchants can enter a custom amount or use shortcuts to add common cash denominations.
An Exact Amount shortcut fills the cash received field with the total due. Merchants still confirm the payment themselves, keeping amount entry separate from recording the transaction.

Amount shortcuts support quick entry while keeping confirmation explicit.
Preventing an insufficient payment
The Confirm Payment button becomes available only when the cash received covers the total due.
If the amount is too low, a message explains the minimum required. For example, a Rp134.000 purchase cannot be confirmed with only Rp100.000 received.

Clear validation shows when the cash received does not cover the total.
Showing the change to return
When the cash received exceeds the total, the interface displays the change owed.
For a Rp134.000 purchase paid with Rp140.000, the change is Rp6.000. The success screen keeps this amount visible so merchants can return the correct change.
The flow also includes a no-change state for exact payments.

Rp6.000 change

no-change
Payment results clearly distinguish exact payments from payments requiring change.
Confirming the payment record
The flow includes a recording state followed by confirmation that the payment has been recorded.
The result displays the payment amount, payment method, payment ID, and time, giving merchants a reference before returning to sales.

Recording feedback confirms when the cash transaction has been saved.
Making receipts accessible
After payment, merchants can access the receipt through sharing options or a receipt QR code.
The receipt brings together purchased items, discounts, the total, cash received, and change. This keeps the payment breakdown available for customers and later reference.
QR receipt

send receipt

Receipts keep the purchase and cash payment breakdown available after checkout.
Reviewing past transactions
The transaction history and detail screens let merchants revisit recorded cash payments.
Details include purchased items, discounts, the total paid, cash received, and change, connecting the checkout result to a record merchants can review later.

Merchants can revisit cash payments and review their transaction breakdown.
Design takeaway
This flow shows how small interface decisions can support everyday checkout tasks: amount shortcuts reduce repeated entry, validation prevents confirmation of an insufficient amount, and visible change calculations clarify what to return to the customer.
Next project

