What Indian shoppers expect at checkout
An Indian online buyer expects to pay by UPI in a few taps, to see cash on delivery if it is offered, to know before paying whether you deliver to their pincode, and to receive a confirmation on their phone within moments. If any of these is missing or confusing, many will abandon the cart and buy where it feels easier.
This guide walks through each part of the checkout from the buyer's side: payment options, address and phone checks, what happens when a payment fails, confirmations and refunds. It is meant for shop owners, manufacturers and brands planning or fixing an online store. Choosing which payment gateway company to sign up with is a separate decision, covered in our guide to choosing a payment gateway for Indian SMEs.
UPI at checkout: intent, QR and UPI ID explained simply
UPI (Unified Payments Interface) is run by the National Payments Corporation of India (NPCI). On your store, UPI is offered through your payment gateway, and the customer always approves the payment in their own UPI app with their UPI PIN. What changes is how the request reaches that app.
| Flow | How it works for the buyer | Where it fits best | What can go wrong |
|---|---|---|---|
| Intent (app switch) | Buyer taps "Pay by UPI", picks an installed UPI app, sees the amount filled in and enters the PIN | Shopping on a phone | Buyer switches back too early or the browser loses the session |
| QR code | A QR code for this order appears on screen and the buyer scans it with any UPI app | Shopping on a computer or tablet | QR expires if the buyer takes too long |
| UPI ID entry | Buyer types their UPI ID and approves a request in their app | Where the gateway still supports it | Typing errors; buyer does not notice the request |
On a phone, the intent flow is usually the shortest path. On a computer, a QR code is natural because the buyer's phone is in their hand. NPCI has tightened rules around request-style (collect) payments for some transaction types in recent years, so ask your gateway which UPI flows it currently supports rather than assuming all three are available.
Test UPI on at least two different UPI apps and on both Android and iPhone before launch. App switching behaves differently across browsers and devices.
Cash on delivery: keep it, but set rules
Many buyers, especially first-time customers and buyers in smaller towns, still prefer to pay on delivery until they trust a store. Removing COD entirely can cost you those orders. Offering it without limits, however, exposes you to refused parcels that you pay to send and to return.
Sensible COD rules include a maximum order value for COD, COD only for pincodes where your courier offers it, a phone or OTP confirmation step before a COD order is dispatched, and blocking COD for buyers with repeated refusals. Some stores also offer a small discount for paying online, which nudges buyers towards UPI without forcing them. Whatever you decide, the rules should be visible before the buyer reaches the last step.
Cards, net banking and wallets
Debit and credit cards remain important for higher-value orders and for buyers who prefer card rewards. Domestic online card payments require an additional authentication step, usually an OTP from the bank, so the card page should not look like a dead end while that OTP arrives. Under Reserve Bank of India rules, ordinary merchants should not store customers' full card numbers; "saved card" convenience works through tokens handled by the card networks and your payment gateway, not through your own database.
Net banking is still used by some buyers and for business purchases. Show the payment options your gateway supports, but order them sensibly: UPI first on phones, then cards, then net banking and others.
Address, pincode and phone checks before payment
Many delivery problems begin as checkout problems. Put a pincode checker on the product page so a buyer in a town you do not serve finds out before adding to cart, not after paying. At checkout, fill in the city and state from the pincode, include a landmark field (Indian addresses often depend on it), and limit fields to what the courier actually needs.
Verify the phone number with an OTP, at least for COD orders, because a wrong number makes delivery and refunds difficult. Allow guest checkout with phone and email rather than forcing account creation; you can offer to save details after the order is placed.
When a payment fails or stays pending
Every store sees failed and pending payments: a bank server slow at month-end, a buyer who closed the UPI app, an OTP that arrived late. What matters is how your store responds. A payment has three states that your system must handle: success, failure and pending. The worst outcome is money debited from the buyer while your store shows "order failed", followed by the buyer paying twice.
- Confirm payment status from the gateway's server-to-server notification, not only from the buyer's browser returning to your site.
- Show a clear pending message that says what will happen next, rather than an error.
- Offer an easy retry with a different payment method when a payment genuinely fails.
- Hold stock for unpaid orders for a set time, then release it automatically.
- Reconcile daily: any captured payment without a confirmed order should be either confirmed or refunded the same day.
Order confirmation by SMS, WhatsApp and email
Buyers want proof within seconds that their order went through. A good confirmation includes the order number, items, amount paid or due on delivery, delivery address, expected dispatch and how to contact you. Follow it with dispatch and delivery updates.
SMS reaches every phone, including feature phones, but transactional messages must follow TRAI's DLT registration rules, explained in our DLT registration guide. WhatsApp messages can carry richer order details and need pre-approved templates through the WhatsApp Business API. Our comparison of SMS and WhatsApp for customer alerts helps you choose which to use for each message.
Refunds and returns from the checkout side
Refunds for prepaid orders normally go back to the original payment method through your gateway, and the admin panel should let staff approve full or partial refunds without logging into several systems. For COD orders there is no original payment to reverse, so you need a way to collect the buyer's bank or UPI details safely and record the refund against the order.
Show the buyer the status of their return and refund in their order history or by message, and state your timelines in your refund policy. The policy pages themselves belong in your launch preparation, covered in our e-commerce launch checklist for India.
How MATROP builds checkout, and when a simpler setup is enough
In MATROP's e-commerce development work, payment and shipping rules are agreed in the planning stage, before any design. We integrate the payment gateway you choose with UPI, cards and COD rules, add pincode serviceability, shipping and delivery notifications, and give your team an admin panel for orders, invoices, returns, refunds and approvals. Checkout is tested on real devices, including failed and pending payment cases, before launch.
You may not need a full store yet. If you take a few orders a week through WhatsApp or Instagram, payment links from your gateway and a simple order register can serve you well until volume justifies a proper checkout. When orders, returns and stock start slipping through the cracks, that is the time to build one.
Questions people ask
Should we charge extra for cash on delivery?
That is a business decision, but if you do, show the charge clearly on the product page and at checkout before the customer places the order. A charge that appears only at the door causes refusals and complaints.
A customer's money was debited but our store shows the order as failed. What should we do?
Check the final status in your payment gateway dashboard first, because pending payments often settle within a short time. If the payment was captured, confirm the order or refund it; never ask the customer to pay again until you have checked.
Do customers need a separate app to pay by UPI on our website?
No. Your payment gateway offers UPI at checkout, and the customer pays using whichever UPI app is already on their phone.
Is a printed or static UPI QR code on the checkout page enough?
It can work for a handful of orders, but someone must match every payment to an order by hand. A QR code or UPI request generated by the payment gateway for each order links the payment to that order automatically.
