Tithi Mondal

Article5 min readUpdated

UPI Payment UX: Designing Checkout for Indian Apps

UPI payment UX explained: checkout design for Indian apps, plus how to design pending, debited-but-not-confirmed, failed and abandoned payment screens.

By Tithi Mondal, UI/UX Designer

A checkout page that works when everything goes right is easy to design. The hard part is the minute after the user taps Pay. UPI hands the user to another app, the network may drop, and the money may leave their account before your server hears about it. This post covers checkout design for Indian apps, with extra depth on the states most founders forget.

What a good payment page UI contains

A payment page should be calm and boring. Users are handing over money, so surprises hurt.

  • Order summary at the top: Items, delivery fee, taxes and the final amount in rupees, with the amount repeated on the Pay button, for example "Pay ₹549".
  • UPI first: For most Indian users UPI is the most common way to pay, so list it first, not buried under cards.
  • Installed apps as buttons: On Android, show the UPI apps the phone actually has, with their names and icons, so the user taps one instead of typing.
  • UPI ID field as an alternative: Validate the format as they type, and show the account holder name returned by verification if your payment provider supports it, so a typo is caught before payment.
  • Cards, netbanking, wallets and cash on delivery below, only if you truly support them.
  • A trust line: A short note such as "Your payment is processed by your bank" near the button. Keep it factual.

Do not make the user re-enter their address or coupon on this page. Keep them editable but collapsed.

The journey after tapping Pay

Think of payment as a conversation between three parties: your app, the UPI app, and the bank. Your app does not control the second and third, so design for uncertainty.

  1. User taps Pay. Show a full-screen state: "Opening your UPI app".
  2. The UPI app opens, the user approves with their PIN.
  3. The user returns to your app, or maybe does not.
  4. Your server asks the payment provider for the final status.

Never decide the outcome from the user returning to your app. Always confirm with your server. Your screens should reflect what the server knows, not what the user did.

Designing the payment pending state

Pending means the bank or provider has not yet said yes or no. It can last seconds or, sometimes, much longer. This is the screen users fear most, so be specific.

On a pending screen:

  • Say it plainly: "We are confirming your payment. This usually takes a minute."
  • Show a gentle progress indicator and a countdown or checking message.
  • Tell them not to pay again and not to close the app yet. Keep this to one short line.
  • Poll the status automatically for a short period, then switch to a "We will update you" message.
  • Provide a "Check status" button so the user has some control.
  • Save the order as "Payment pending" in their order history so they can find it later.

Avoid spinners with no text. A spinner that runs for two minutes with no explanation looks like a crash.

Debited but not confirmed

This is the most stressful case: the user's bank account shows a deduction, but your app shows no order. It happens when the payment provider and bank take time to reconcile, or the callback to your server fails.

Design a dedicated screen for it. It should include:

  1. A clear headline: "Your payment is being verified."
  2. A reassurance in plain words: "If money has left your account, it will either confirm your order or be returned to your account." Check with your payment provider on the exact timeline and wording you can promise, and show only what is true for your business.
  3. The transaction reference and amount the user can copy.
  4. A way to contact support with the reference pre-filled, including a WhatsApp link, since many users prefer it.
  5. A notification by SMS or push when the status changes.

Behind the screen, build a reconciliation job so your team can match these payments. Design is half of this: the user must never feel ignored.

Failed payment screens

A failure screen should answer three questions: what happened, is my money safe, what can I do now.

  • What happened: Use human reasons where known: "Your bank declined the payment", "The payment timed out", "You cancelled the payment". Avoid raw error codes in the main message. Place them in a small "Details" link for support.
  • Money safe: Say "No money has been taken" only if you are sure. If unsure, use the pending flow instead.
  • Next step: A big "Try again" button, a secondary "Pay another way" button, and keep the cart intact.

Do not send them back to the home screen. Take them back to the payment page with their cart unchanged.

Abandoned payments

Some users open the UPI app and never come back. Perhaps the phone rang, or the PIN was forgotten. Design for them too.

  • Hold the cart or order for a reasonable time and show "Your order is waiting" on the home screen.
  • If a payment was started, check its status when the app reopens, and show the right state straight away.
  • Send one reminder, not five. A single polite WhatsApp or push message is enough.
  • For repeat attempts, show a simple "Resume payment" button.

Summary table of payment states

StateWhat the user needs to seeMain action
SuccessAmount, order number, next stepView order
PendingChecking message, do not pay twiceCheck status
Debited, not confirmedReference, reassurance, support optionContact support
FailedReason, money safe, cart intactTry again
AbandonedOrder waiting, easy resumeResume payment

Small details that add trust

  • Show the amount in the same format everywhere: ₹1,499 with Indian digit grouping where relevant.
  • Keep buttons large and spaced, since many users have budget phones with small screens.
  • Do not auto-advance success screens too fast. Let people read the confirmation.
  • Always email or message a receipt.

For more on what Indian users expect from interfaces in general, read designing apps for Indian users. My mobile app design service covers checkout and payment flows, and you can get in touch to talk about yours.

Frequently asked questions

What should a UPI payment pending screen say?

It should say plainly that you are confirming the payment, ask the user not to pay again, and show a Check status button. Update automatically when the status changes.

Why does money get debited but the order is not confirmed?

The bank has processed the payment but the confirmation has not yet reached your server, or the callback failed. Your app should show a verification screen and your team should reconcile these payments.

Should I show UPI apps as buttons or a UPI ID field?

Both, with the installed apps as the main option. Tapping an app is faster than typing an ID, and the ID field stays as a fallback.

What happens to the cart if payment fails?

Keep it exactly as it was and send the user back to the payment page with a Try again button.

Have a product in mind? Let us design it properly.

Tell me what you are building. I will reply with questions, a rough timeline and a quote.