Article7 min readUpdated
Cash on Delivery UX and Payment Options Page Design
Cash on delivery UX for Indian stores: payment method order, COD confirmation, prepaid discount display, fees and every state of the payment options page.
A tiffin-box seller in Durgapur lists a steel lunch box for ₹649. Half of her first orders are cash on delivery. A third of those are refused at the door. She blames the couriers. The real problem is on the payment screen: shoppers tap COD in one second, with no confirmation and no sense of commitment. Cash on delivery UX is the design of the COD option on the payment screen: how it is shown, what it costs, what the shopper must confirm, and what happens at the door. Cash on delivery, or COD, means the shopper pays the courier in cash or by UPI when the parcel arrives.
This guide covers the payment options page as a whole, with COD as its hardest part. UPI payment screens are covered in UPI payment UX and checkout design. The page before this one is the address step, and the cart comes before that: cart and wishlist screen design.
Why must an Indian store offer cash on delivery?
An Indian store should offer COD because many first-time online shoppers, especially in smaller towns, do not yet trust paying before they see the product. COD lowers the first-purchase worry. It also costs the store more, so the design must guide each shopper to the best choice honestly.
COD brings real costs: couriers charge a handling fee, cash settles days later, and refused parcels cost shipping both ways. Some stores limit COD to certain PIN codes or order values. The screen can show the costs clearly and reduce refusals.
Never remove COD to hide a problem. If you must restrict it, say when it is available. For a store serving first-time internet users in towns outside the big cities, COD is often the option that gets the first order.
What order should payment methods appear in?
List the method most shoppers use first, show its offer, and keep COD visible but placed after the prepaid methods. A common order is UPI, cards, net banking, wallets and then cash on delivery.
Order is a design decision, not a neutral list. Put methods in this order and change it with your own order data:
- UPI. Apps such as Google Pay and PhonePe as tappable icons, plus "Enter UPI ID". It is the most common way to pay in Indian apps.
- Cards. Credit and debit, with a clear field for card number, expiry and CVV.
- Net banking, wallets and pay later. Only the ones you support.
- Cash on delivery.
Use radio buttons so only one option is open at a time. Open the chosen method in place, below its row, rather than on a new screen. Show the final amount at the top and bottom of the screen: "Amount to pay ₹899". If COD adds a fee, the amount changes when COD is selected, and the change must be visible at once.
How do you show a prepaid discount without pressure?
Show the saving in rupees on the prepaid option and let COD stand beside it without shame. For example: "UPI, save ₹50" and "Cash on delivery, ₹40 extra fee". Both numbers must be true and calculated from the real order.
Rules for prepaid discount display:
- State the saving as a rupee amount on the method row, not only a percentage.
- Show the effect on the total: "Pay ₹849 with UPI" or "Pay ₹939 with cash on delivery".
- If COD has a fee, label it "Cash handling fee" and show it before the shopper selects COD, not as a surprise on the next screen.
- Do not use red warnings or guilt words such as "Missing out" next to COD. Shoppers notice, and the tone feels like a trap.
- Do not change the displayed MRP or product price between prepaid and COD. Change only the fee or discount line.
- Never show the prepaid discount on the payment page for the first time. Mention it earlier, on the product page and in the cart: "Extra ₹50 off on UPI".
Check that the discount survives a returned order. If a prepaid order is returned, the refund should be the amount paid, and the screen should say so in the refund flow. The refund screen and the payment screen must agree on the money.
How should COD confirmation and limits work?
A COD confirmation is a short step after the shopper picks COD, where she confirms her phone number and the amount she will pay at the door. Its purpose is to make the order a real promise and to reduce refused parcels.
Design the confirmation as a bottom sheet, not a full page:
- Heading: "Confirm cash on delivery".
- Amount: "You will pay ₹939 to the courier when the order arrives".
- Phone check: "We will send an OTP to +91 98XXXXXX10". OTP means one-time password, a code sent by SMS. The OTP check is optional and fits stores with many refusals.
- Payment at the door: "You can pay in cash or by UPI to the courier."
- Buttons: "Confirm order" and "Choose another method".
Say the limits plainly, before the shopper reaches the sheet:
| Situation | Wording |
|---|---|
| Order value too high | "Cash on delivery is available for orders up to ₹5,000. Pay by UPI for this order." |
| PIN code not covered | "Cash on delivery is not available for 713216. Pay online to get this delivered." |
| Fee applies | "Cash handling fee ₹40 added to your total." |
| Item excluded | "This item is prepaid only." |
The value limit of ₹5,000 above is an example. Set your own and say it.
After the order, send a message by SMS or WhatsApp: "Order confirmed. Pay ₹939 to the courier on delivery." Repeat it on the day of delivery. A reminder reduces the surprise of a shopper who forgot she must have cash ready. See notification UX for push, SMS and WhatsApp.
What states does a payment options page need?
A payment options page needs states for loading, method selected, processing, success, failure, timeout and unavailable methods. Payment is the moment of greatest worry, so every state needs a clear sentence.
- Loading. Show the method rows as grey blocks. Show the amount first, since it is known.
- Method selected. Open the method's detail below its row.
- UPI pending. "Open your UPI app and approve the request of ₹899. We are waiting." A timer of about 5 minutes with "Cancel and try another method".
- Processing. "Do not press back. We are confirming your payment."
- Success. "Payment received. Order placed." With the order ID and the tracking link.
- Failure. "Payment failed. No money was taken, or any amount taken will be returned by your bank." Only write that second sentence if it matches your payment partner's rules. Offer "Try again" and "Use another method".
- Timeout. "We did not hear back from your bank. Check your UPI app before paying again." This avoids double payment.
- Method unavailable. Grey the row and say why: "Net banking is not available now".
For the payment partner's own screens, test how the shopper returns to your page. A shopper who finishes a UPI payment and lands on a blank page will pay twice.
What does the screen look like from top to bottom?
From top to bottom, the page shows the order summary, the amount, the methods in order, the selected method's details and one primary button whose label matches the method. The button label changes with the method.
- Short order summary: items, delivery address, delivery date. Collapsible.
- Amount to pay, large.
- Offer line: "Extra ₹50 off with UPI" if applicable.
- Method list, with UPI at the top.
- Details of the selected method.
- Primary button: "Pay ₹849" for UPI, "Place order" for COD. Do not write "Pay" on a COD button, because nothing is paid yet.
- Trust line: "Secure payment. Returns within 7 days". Use your own policy.
Fix the button at the bottom of the screen on mobile. Show the total beside it so the shopper never loses sight of the amount.
What mistakes should you avoid?
The worst mistakes are hiding COD, adding a last-second COD fee, making prepaid look like the only safe choice and leaving the shopper confused after a failed payment.
- Making COD a small text link, or removing it from small orders.
- Showing a fee only after the shopper taps "Place order".
- Using the same button label for every method.
- Skipping the double payment protection after a timeout.
When I design checkout screens, I draw the failed and pending states first, because the happy path takes care of itself. If your store needs a payment screen designed with COD, UPI and refunds working together, see my UI and UX design service or get in touch.
Frequently asked questions
Should cash on delivery be the default payment option?
+
Usually no. List UPI first for most shoppers and keep COD visible after the prepaid methods. For returning shoppers, preselect the method they used last.
How can a store reduce refused COD parcels?
+
Add a short confirmation step with the exact amount, send an SMS or WhatsApp reminder, and optionally verify the phone number with an OTP. Honest fees and limits also help.
How should a COD fee be shown?
+
Label it Cash handling fee, show the amount in rupees on the COD row before the shopper selects it, and update the total at once when COD is chosen.
What happens if a UPI payment times out?
+
Tell the shopper to check her UPI app before paying again, show a pending state and avoid creating a second payment. Confirm the status before placing or cancelling the order.
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.