Article6 min readUpdated
Wallet UI Design: Balance, Add Money and History
Wallet UI design for Indian apps: how to show the balance, build the add money flow, and design transaction history, statements and receipts.
By Tithi Mondal, UI/UX Designer
A tiffin service in Durgapur lets customers keep a prepaid balance in its app. A customer opens the app on a Monday morning and sees "₹240". Does that mean ₹240 available today, or ₹240 including yesterday's pending order? If the screen cannot answer in one second, the customer will message support.
A wallet is a stored balance inside an app that a user adds money to and spends from. Wallet UI design is the work of showing that balance honestly and making every movement of money easy to trace. This post covers the balance, the add money flow, the transaction history screen, and statements and receipts. For the payment step itself, see my post on UPI payment and checkout UX.
What should a wallet screen show first?
A wallet screen should show the balance, the main action and the latest activity, in that order. The user opens the wallet with one question: how much do I have, and what just happened.
From top to bottom:
- A label: "Wallet balance".
- The balance, in large type: "₹1,240.50".
- One main button: "Add money". A second, quieter button may say "Send" or "Withdraw" if the product offers it.
- A heading "Recent activity" with 3 to 5 transactions.
- A link: "See all transactions".
Keep the balance as the largest element on the screen. Do not put offers, banners or a cashback carousel above it. For where the wallet lives in an app, see app home screen design.
How should you display the balance?
Display the balance as one number with a clear label, the rupee sign, and two decimal places only when paise matter. Then separate money the user can spend from money that is held.
- Available balance: what the user can spend now.
- On hold: money reserved for a pending order or payment, with a small "What is this?" link.
- Total: shown only if holds exist.
Use the rupee symbol and the Indian digit grouping, such as ₹1,24,000. Align numbers to the right in lists so the digits line up. Add a show and hide icon for the balance, because people use phones in public places. Remember to hide the number in the app switcher preview only if the business asks for it.
If the app serves users abroad, show the local currency only where the business has decided it, and never a converted number that looks like a promise. Colour matters too: do not show a zero balance in angry red. Say "₹0. Add money to start" and move on.
How should the add money flow work?
The add money flow should take the user from "Add money" to a confirmed balance in 3 screens: amount, payment, result. Show the limits before the user types, not after an error.
- Amount screen. A big input with the rupee sign. Quick chips below it: ₹100, ₹500, ₹1,000, with the user's last amount as a chip. A line under the input: "You can add ₹10 to ₹50,000 at a time." The real limits come from the business and its advisers.
- Payment screen. Show the UPI apps installed on the phone, and other methods the business supports. The details of that screen belong in the checkout flow.
- Result screen. Three outcomes: success, pending, failed.
Wording for each result:
- Success: "₹500 added to your wallet. New balance: ₹1,740."
- Pending: "We are waiting for your bank to confirm. Your money is safe. We will update your balance and send a message."
- Failed: "The payment did not go through. If money was taken from your account, it is usually returned by your bank. Check your transaction history for the status."
Be careful with that last sentence. The refund time is the bank's matter, so do not state a number of days unless the business has confirmed it. Pending is the state that causes most support messages. Make it visible in the history too, with a status chip that changes when the payment resolves.
What does a good transaction history screen look like?
A good transaction history screen is a list grouped by date, where every row shows who, what, how much and what status, and where a tap opens the detail. The user reads it to answer one question: where did my money go.
Each row has:
- An icon or initials for the other party.
- A title: "Paid to Sharma Tiffin Service" or "Added from UPI".
- A line below: date and time, and a reference in small grey type.
- The amount on the right: "-₹180" or "+₹500". Use a minus or plus sign, not colour alone, so colour-blind users can read it.
- A status chip only when the status is not "Success": Pending, Failed, Reversed.
Group rows under headings such as "Today", "Yesterday" and "12 November". Add filters at the top: All, Added, Spent, Refunds. Add a date range and search when the list grows long; see search and filter UX design for the patterns. Load the list in pages, and show a loading skeleton, not a blank screen.
For an empty history, write something useful: "No transactions yet. Add money to get started." with an Add money button. More on this in empty states, loading and error screens.
How should statements and receipts work?
Statements and receipts give the user proof of a transaction, so they must be easy to open, share and download. A tap on any row opens a detail screen that works as a receipt.
The detail screen shows:
- The status, in large words: "Payment successful".
- The amount and the date and time.
- The other party and the payment method.
- A transaction ID with a copy button.
- A "Share receipt" button, which opens the phone's share sheet. Many users will send it on WhatsApp.
- A "Need help with this payment?" link that opens support with the transaction already attached. See in-app chat and support screen design.
For statements, offer a "Download statement" button with a date range: This month, Last 3 months, Choose dates. Show a clear result: "Your statement is ready" with a Share button, or an email option if the business supports it. For a business wallet, receipts may need tax details; see invoice and quotation screen design. What a receipt or statement must contain is a matter for the business and its compliance or legal adviser. The designer lays out the fields that the adviser lists.
Which wallet states and mistakes should you plan for?
Plan for every state of the money, because a wallet is where trust is won or lost. The states below are the ones most often forgotten.
| State | What the screen should say |
|---|---|
| Zero balance | "₹0. Add money to start." |
| Money on hold | "₹200 is held for your order and will be released if it is cancelled." |
| Pending add money | "Waiting for bank confirmation." |
| Failed payment | Reason, next step and a Retry button |
| Reversed or refunded | "₹180 returned to your wallet" with the original transaction linked |
| Offline | "You are offline. Showing your last balance from 10:42 am." |
| Limit reached | "You have reached the limit for today. You can add money again tomorrow." |
The mistakes I see most:
- Showing a balance with no time or label, so users doubt it.
- Hiding fees until the last step.
- Using only colour to separate credits and debits.
- Giving transactions vague names such as "Payment" with no party.
- Letting a pending payment look the same as a successful one.
- Sending users to a support form to find a receipt that the app already has.
Limits, holds, refunds and record keeping are rules the business must confirm with its compliance or legal adviser before screens are final.
If you are planning a wallet or any money screen, I can map the flow with you through my UI/UX design service.
Frequently asked questions
What is the difference between available balance and total balance?
Available balance is the money a user can spend now. Total balance includes money that is on hold for pending orders, so show it only when holds exist.
How many transactions should the wallet screen show?
Show 3 to 5 recent transactions on the wallet screen and a link to the full history. The full history screen then groups rows by date and adds filters.
Should a wallet app let users download statements?
Giving users a way to get statements and receipts builds trust. The exact requirements depend on the business, so confirm them with a compliance or legal adviser.
How do you show a pending add money payment?
Show a status chip that says Pending, explain that the bank has not confirmed yet, and update the row when the result arrives. Also send a message when it resolves.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.