Wallet Top-Up
Trigger: Customer initiates a credit top-up in Hiro App Products: Hiro App · Hiro Platform Outcome: Wallet balance increases; customer can proceed with machine activation
Flow
Customer opens Hiro App → navigates to Wallet
│
▼
Customer selects top-up amount
(predefined denominations available + custom amount field;
maximum RM1,000 per top-up)
│
▼
Customer selects payment method
│
├─ eWallet (QR code / deep link)
└─ Credit / debit card
│
▼
App sends top-up request to Hiro Platform
(customer ID, amount, payment method)
│
▼
Platform initiates payment with the appropriate gateway
(gateway varies by payment method — see Payment Gateways)
│
├─ Payment FAILED
│ Platform returns failure to App
│ App shows "Payment failed, please try again"
│
└─ Payment SUCCESS
│
▼
Platform credits wallet balance
(adds top-up amount to customer's stored balance)
│
▼
Platform records top-up transaction
(timestamp, customer ID, amount, payment method)
│
▼
Platform returns new balance to App
│
▼
App shows updated wallet balance + top-up confirmationTop-Up Entry Points
| Entry Point | When |
|---|---|
| Wallet screen | Customer proactively tops up |
| Insufficient credit prompt | Triggered during machine activation when balance is too low |
Transaction Fee (Malaysia)
| Top-Up Amount | Transaction Fee |
|---|---|
| Below RM30 | Customer pays the fee (added on top of the top-up amount) |
| RM30 and above | Hiro absorbs the fee (customer pays only the top-up amount) |
There is no minimum top-up amount — customers can top up any amount. However, the fee structure incentivises larger top-ups.
Notes
- Wallet balance is stored and managed entirely by Hiro Platform
- Predefined denominations are available, plus a custom amount field; maximum RM1,000 per top-up
- Top-up transactions have their own separate history section (not mixed with laundry order history)
Related Flows
- Machine Activation — App — wallet balance is checked during this flow
