Net banking, or internet banking, was one of the first ways Indians paid online, and it remains a standard option at almost every Indian checkout. The customer picks their bank, is taken to the bank's own page, logs in, approves the payment and is sent back to the store. Money moves straight from their bank account, with no card and no UPI app involved.
Behind that simple journey are a redirect between three websites, a bank's own authentication, and a confirmation that has to travel back to the merchant. Most of the time it works. When it doesn't, the customer is often left with money debited and an order showing unpaid. This guide explains the flow for customers and merchants, and what to do when it goes wrong.
The flow, step by step
A net banking payment passes between the merchant, its payment provider and the customer's bank:
- 1CheckoutCustomer chooses net banking and their bank
- 2RedirectProvider sends the customer to the bank's payment page with the amount and reference
- 3AuthenticateCustomer logs in and approves with the bank's second factor
- 4DebitBank debits the account and tells the provider
- 5ReturnCustomer is redirected to the store; the provider confirms to the merchant
Two confirmations travel back: the customer's browser returns to the merchant's site, and the provider tells the merchant's server directly, by webhook or through a status check. Only the second is trustworthy. A customer who closes the tab on the bank's page has still paid if the bank debited them, and the merchant has to rely on the provider's confirmation to know.
Who does what
Each party has a distinct role, which is why problems can sit in different places:
| Party | Role |
|---|---|
| Customer | Chooses the bank, logs in on the bank's page and approves the payment |
| Merchant | Creates the order, redirects to the provider, and marks the order paid on the provider's confirmation |
| Payment aggregator or gateway | Maintains integrations with many banks, sends the customer to the right one, receives the result and settles to the merchant |
| Customer's bank | Authenticates the customer, checks balance and limits, debits the account and reports the result |
Net banking integrations are bank by bank, so a provider's net banking can work well for one bank and be degraded for another at the same moment. That's also why a bank's planned maintenance can make its net banking unavailable while other banks work normally.
How the customer is authenticated
The bank, not the merchant or provider, authenticates the customer, using its own login and a second factor such as an OTP or a separate transaction password. RBI's Authentication Mechanisms for Digital Payment Transactions Directions, 2025, which apply from 1 April 2026, require digital payments to be authenticated with at least two distinct factors unless exempted, and for payments other than card-present ones, at least one factor must be dynamic: unique to that transaction. That's why banks ask for something beyond the login password before a payment goes through.
Because authentication happens on the bank's site, the customer should check they're on their bank's genuine page before entering credentials. Our guide to payment gateway security covers the merchant side of keeping payments safe.
Why net banking payments fail
Most failures fall into a few groups:
| What the customer sees | What usually happened | What to do |
|---|---|---|
| Bank page doesn't load or shows maintenance | The bank's net banking or its link with the provider is down | Try another method such as UPI or a card, or try later |
| Session expired | Too long on the bank's page, or the page was left open | Start the payment again from the store |
| Payment declined by the bank | Insufficient balance, or a daily or per-transaction limit set by the bank or the customer | Check balance and net banking limits in the bank's app |
| OTP didn't arrive | SMS delay or a changed mobile number | Wait briefly, or use another method |
| Corporate account payment stuck | The payment needs a second user to approve it | Ask the approver to authorise it in corporate net banking |
| Money debited, order shows unpaid | The debit happened but the confirmation didn't reach the merchant in time | See below; don't pay again until it's resolved |
Money debited but the order isn't paid
This is the case that worries customers most. The bank debited the account, but the store says the payment failed or is pending. Usually one of two things happened: the confirmation is delayed and will arrive, or the payment failed after the debit and the money will be returned.
- Don't pay again straight away. Wait a little and check the order status; delayed confirmations often resolve on their own.
- Find the bank reference for the debit in your account statement or bank app.
- Contact the merchant with the order number, amount, time and bank reference. The merchant or its provider can check the payment's status with the bank.
- If the payment failed, the debit should be reversed to your account. If it hasn't been within the time your bank or the merchant gives, raise a complaint with your bank.
- If the bank doesn't resolve the complaint within 30 days, or you're not satisfied with its reply, you can complain to the RBI Ombudsman at cms.rbi.org.in.
RBI's framework of turnaround times and compensation for failed transactions sets timelines for specific channels such as cards, IMPS, UPI and NACH. It doesn't have a separate row for net banking payments, which is why the merchant and your bank are the first places to go. Our guide to money debited but the payment failed covers the channel-by-channel timelines.
For merchants: getting net banking right
Most net banking problems that reach a merchant's support team are preventable:
- Never mark an order paid from the customer's browser return alone; wait for the provider's webhook or check the status. Our guide to payment gateway webhooks explains why.
- Treat a payment without a final status as pending, not failed, and check it with the provider on a schedule. Bank confirmations can lag.
- Show a clear pending message, and stop customers paying twice for the same order. Our guide to duplicate payments covers the safeguards.
- Track success rate by bank. If one bank's net banking is degraded, show a notice or steer customers to UPI or cards for that bank. Our guide to payment success rate explains how to measure it.
- Reconcile net banking payments against settlement reports like any other method; the reconciliation guide covers the routine.
If you use more than one provider, bank-level performance becomes a routing signal: LILPE's intelligent routing page describes ranking providers on success rate per payment method, and per bank where volume allows.
Net banking, UPI and cards compared
Each method has its place at an Indian checkout:
| Compared on | Net banking | UPI | Cards |
|---|---|---|---|
| Where the customer approves | On the bank's website | In a UPI app with the UPI PIN | With the issuer, usually by OTP (3-D Secure) |
| Limits | Set by the bank and the customer's net banking settings | Set by NPCI and banks, varying by category | The card's limit and the customer's controls |
| Experience on mobile | A redirect to a bank page; can be slower | Usually quickest, especially with an app on the phone | Form entry, then OTP; quick with saved tokens |
| Typical use | Larger payments, customers without UPI or cards, corporate accounts | Everyday payments of most sizes | Credit, EMI, international cards |
Offering all three gives customers a fallback when one route is having trouble. Our guides to UPI transaction limits and how online card payments work cover the other two methods.
Frequently asked questions
How does a net banking payment work?
At checkout you choose net banking and your bank, and you're redirected to your bank's payment page. You log in, approve the payment with the bank's second factor, such as an OTP, and the bank debits your account and confirms to the merchant's payment provider. You're then returned to the store, which marks the order paid once the provider confirms.
Is net banking safe for online payments?
Yes, when you're on your bank's genuine website: you authenticate directly with your bank using two factors, and the merchant never sees your banking credentials. Check the web address before logging in, and never share your password or OTP with anyone.
Net banking payment failed but money was deducted. What should I do?
Don't pay again immediately. Check the order status after a little while, then contact the merchant with the order number and the bank reference for the debit. If the payment failed, the debit should be reversed; if not, complain to your bank, and if it isn't resolved within 30 days, to the RBI Ombudsman.
Which is better, net banking or UPI?
UPI is usually quicker on a phone, especially for everyday amounts. Net banking can suit larger payments within your bank's limits, customers who don't use UPI, and corporate accounts. Many customers use both, switching when one isn't working.
Why is my bank's net banking not working at checkout?
The bank's net banking may be under maintenance or having a problem, or its connection with the merchant's payment provider may be degraded. Try again later or pay with UPI or a card.
Go deeper
Official sources
- RBI — Authentication mechanisms for digital payment transactions Directions, 2025At least two distinct factors unless exempted; for transactions other than card-present, at least one factor dynamically created or proven. Compliance by 1 April 2026.
- RBI — Harmonisation of Turn Around Time (TAT) and customer compensation for failed transactions (20 Sep 2019)Timelines by channel (cards, IMPS, UPI, AePS, NACH, PPIs and others); no separate row for net banking payments.
- RBI — Reserve Bank – Integrated Ombudsman Scheme, 2026: FAQsComplain to your bank first; approach the Ombudsman if there's no reply within 30 days or you're not satisfied; cms.rbi.org.in.
Last reviewed . Examples, amounts and screens marked illustrative are not LILPE figures.
