How do you accept UPI payments on an online store in India?
To accept UPI (Unified Payments Interface) payments on an online store in India, you connect a payment gateway to your checkout, complete the gateway's KYC (Know Your Customer) verification with your business documents and bank account, and switch UPI on as a payment method. Once that is live, a customer selects UPI at checkout, either taps through to their UPI app on a phone or scans a QR code on a desktop, approves the collect request with their UPI PIN, and your store receives a success or failure callback from the gateway. The money does not land in your bank account instantly — it is settled by the gateway on a cycle, typically after a hold period that the gateway defines for your account.
There are three practical routes, and which one you pick depends on how much of a store you actually have. If you have a full storefront with a cart, you want a gateway integrated into checkout so the order is created and marked paid automatically. If you sell a handful of items and take orders over WhatsApp or Instagram, a payment link or a per-amount QR code from a gateway or payment-link provider is enough and needs no development work. If you are on a hosted ecommerce platform — HOD Media is one, and there are others — UPI is usually configured inside the platform rather than coded, because the platform already carries the checkout and the gateway connection. HOD Media's hosted stores support UPI and card payments alongside COD (cash on delivery), so the setup step for a merchant is account verification rather than integration.
What do you actually need before UPI goes live?
Every Indian payment gateway will ask for the same core set of documents before activating live UPI collection. The exact list varies by gateway and by entity type, so treat this as what to have ready rather than a definitive checklist.
You will generally need PAN (Permanent Account Number) for the business or proprietor, a bank account in the business name with a cancelled cheque or bank statement, address and identity proof for the signatory, and your GST (Goods and Services Tax) registration if you have one. Gateways also inspect the website itself: they commonly want a working product page, a contact page, and published terms, refund and shipping policies before they approve live mode.
The website check is where most first-time merchants get stalled. A store with placeholder text, no refund policy, or a domain that does not resolve will fail review even though every document is correct. Getting the store publicly live on a real domain first, then applying for the gateway, is the faster sequence.
What is the difference between UPI intent, UPI collect and a static QR?
UPI intent is the mobile flow. The customer taps "Pay with UPI" on their phone, the browser hands off to Google Pay, PhonePe, Paytm or whichever app they have, and the amount is pre-filled. Intent has the least friction because the customer never types a UPI ID.
UPI collect is the request flow. The customer enters their UPI ID (VPA, or virtual payment address) at checkout, and the gateway pushes a collect request into their app for approval. Collect works on desktop but depends on the customer knowing their UPI ID and noticing the notification, so it drops off more.
A dynamic QR is the desktop equivalent of intent. The checkout page renders a QR encoding that specific order amount, the customer scans it with their phone, and the payment maps back to the order automatically.
A static QR — the printed code taped to a counter — is a different thing. It accepts any amount from anyone and carries no order reference, so reconciling a static QR payment to an online order is manual work. Static QRs are fine for a physical counter and a poor fit for a store with orders to fulfil.
Do you have to use a payment gateway, or can you just share your UPI ID?
You can legally accept UPI into a business account by sharing a UPI ID or QR and asking customers to send the amount. Small sellers do this constantly. It costs nothing per transaction, which is the entire appeal.
The cost shows up elsewhere. There is no automatic confirmation to your store, so someone has to check the bank app and match each payment to an order by amount and time. Amounts collide the moment two customers order the same item. Refunds become a manual transfer with no audit trail against the original payment. And there is no gateway to arbitrate when a customer says they paid and you cannot find it.
A gateway charges a percentage on UPI transactions — the rate depends on the provider, your volume and your negotiated terms, and it changes, so check current pricing directly with the gateway rather than trusting any article including this one. What the fee buys is automatic order marking, refunds against the original transaction, settlement reports, and a reconciliation trail you can hand to an accountant.
The honest dividing line is order volume. Under a handful of orders a week, manual UPI is survivable. Past that, the reconciliation labour costs more than the fee.
How should you choose between gateways?
Do not choose on headline rate alone, because most Indian gateways sit close together on UPI pricing and differ on things that matter more once you are live.
Check the settlement cycle — how many days between a customer paying and the money reaching your bank account. Slower settlement is real working capital tied up if you buy stock to fulfil.
Check whether the gateway is already supported by the platform your store runs on. An officially supported integration means order status, refunds and settlement reports flow into the store without custom code. A gateway that is technically excellent but unsupported by your platform becomes a development project.
Check refund handling. Ask whether refunds are initiated from the gateway dashboard, how long the money takes to reach the customer's UPI app, and whether the transaction fee is returned to you on a refund. Policies differ.
Check what happens on failed and pending UPI payments. UPI has genuine pending states where the customer's bank has debited but confirmation has not returned. A gateway that resolves these cleanly and reports them clearly saves you disputed orders.
And check support access. When a live payment goes missing on a Saturday, the difference between a ticket queue and a phone number is the whole experience.
What usually goes wrong with UPI on Indian stores?
The most common problem is the pending payment that resolves late. The customer's money leaves, your store shows failure, they order again, and now you have a duplicate. Handling this means checking the gateway dashboard for the original transaction before treating a repeat order as new.
The second is UPI transaction limits. Individual UPI payments are capped, and the cap varies by bank and by app. High-value orders can simply fail on UPI, so keeping card or netbanking available at checkout matters if your basket sizes are large.
The third is mismatched business names. If the name on your bank account, PAN and GST registration do not agree, KYC stalls, sometimes without a clear explanation. Fixing the mismatch at source is faster than appealing.
The fourth is invoicing. Accepting the payment is not the same as issuing a compliant document. If you are GST-registered you still need a proper tax invoice against each order — HOD Media generates GST invoices as part of order processing, and other platforms handle it their own way, but it is worth confirming rather than assuming.
Where does UPI sit next to COD for an Indian store?
UPI and COD (cash on delivery) solve different customer objections. UPI removes friction for buyers who already trust you. COD removes risk for buyers who do not yet.
Most Indian stores end up offering both, then watch the mix shift toward prepaid as the brand becomes familiar. Prepaid orders are cheaper to fulfil because there is no cash handling and no courier COD remittance to chase.
HOD Media's hosted stores carry COD, UPI and card payments together, with courier integrations that check serviceability against Indian pincodes and WhatsApp and email automation for order updates. Whether you need a hosted platform at all depends on your order volume and whether you would rather configure a store or build one. If you already run a site you are happy with, adding a gateway to it is the smaller change, and that is a perfectly good answer.