How to Accept Online Payments on Your Website in India

To accept online payments on your website in India, you need a business bank account, KYC documents, an account with a payment gateway or aggregator, and a checkout that is connected and tested. Customers can then pay by UPI, cards, net banking or wallets. This guide explains the options, the steps and the checks to do before launch.

What you need before you start

Payment providers do not hand over a live account to anyone. They check who you are and where the money will go. Gather your documents first, so approval is not delayed by missing papers.

• A bank account in the name of your business or proprietor, where settlements will arrive.
• Identity and business documents as the provider asks, which usually include PAN and address proof. Requirements differ by provider and business type.
• A working website with clear product or service details, contact information and policy pages, because providers often review the site before approving.
• GST details if you are registered, since they affect invoices.

Rules change from time to time, so always follow the checklist shown by the provider you choose rather than a list from an old article.

Payment methods Indian customers expect

Indian shoppers are used to paying in several ways, and offering the familiar ones reduces drop-offs at checkout.

• UPI: pay through an app or a UPI ID. It is the most familiar method for many buyers, especially on phones.
• Debit and credit cards: still important for higher-value orders and for customers who like to use card rewards.
• Net banking: useful for customers who prefer to log in to their own bank.
• Wallets: some buyers keep balances in wallet apps and like to use them.
• Cash on delivery: not an online payment, but many stores for physical goods still offer it. It brings its own handling and return costs.

Which methods are available depends on the provider and on your account approval. Ask which ones will be switched on for your business before you commit.

Also think about where your customers are. A buyer paying from a phone in a small town may prefer UPI, while a business buyer may want a card or net banking so the payment is easy to record. Offering two or three methods that suit your audience is usually better than a long, confusing list.

Payment gateway vs payment link vs aggregator

These terms get mixed up, so here is a plain explanation.

A payment gateway is the technology that securely passes payment details from your checkout to the banks and back. An aggregator is a company that lets many small businesses use one shared set of banking arrangements, so you can start without negotiating separately with each bank. Many popular services you will hear about in India work as aggregators and also provide the gateway. A payment link is a web address you create for a particular amount and send by WhatsApp, SMS or email. The customer opens it and pays.

A link is a good start if you sell a few services or take advance payments by chat, because it needs no website integration. A full checkout integrated into your site suits stores and anyone with many orders, since the customer pays without leaving your brand experience. Whichever route you choose, your plan to accept online payments on your website should start with a small test order. Compare features, support and clarity of terms rather than only the headline charges, and ask for the current fee schedule directly from the provider.

Steps to accept online payments on your website

The exact screens differ by provider, but the order is almost always the same.

1. Decide what you sell and how: fixed-price products, services with advance payment, donations or subscriptions each need a slightly different setup.
2. Choose a provider: compare supported payment methods, settlement terms, support quality, refund tools and how well it works with your website platform.
3. Submit KYC and website details: upload the documents requested and share your site address and policy pages.
4. Wait for approval: you may receive test credentials first and live credentials after verification.
5. Integrate with your site: use a plugin, an app or custom code, depending on your platform.
6. Test everything in test mode: place successful, failed and cancelled test payments and check the emails and order status.
7. Switch to live mode: replace test keys with live keys and make one small real payment yourself.
8. Monitor the first week: check orders, settlements and customer messages closely after launch.

On a Shopify or WooCommerce store, much of the integration is a configuration task. On a custom site, a developer connects the provider's code to your order system. Our payment gateway integration service covers this kind of work.

KYC and settlement basics

KYC means know your customer. The provider verifies your identity, business and bank account before sending money to you. This is a safety requirement, and it can take longer if documents are unclear or names do not match across PAN, bank and business records. Make sure the name on your bank account matches your documents.

Settlement is the transfer of collected money from the provider to your bank account. Providers usually pay out after a set number of working days, and the timing can vary by provider, by account type and by your risk profile. New accounts are sometimes settled more slowly at the start. Weekends and bank holidays also affect timing.

Plan your cash flow around this delay. If you pay suppliers on the same day a customer pays you, check how soon money will really arrive. Ask the provider for its current settlement terms in writing, and keep a record of the fees charged, because they are deducted before the money reaches you.

Refunds and failed payments

Refunds are part of normal business, so set them up before the first order. Most providers let you refund a payment from their dashboard, either fully or partly, and the money returns to the customer's original payment method. How long it takes to appear depends on the bank and payment type, so tell customers a realistic window instead of promising an exact day.

Failed payments are different. A customer may be charged while the order shows as failed, usually because of a network drop. Good providers reconcile these and send the money back automatically, but you should still watch for them. Keep a clear refund and cancellation policy on your site and link it near the pay button. Our guide to legal and policy pages for Indian online stores explains what to cover.

GST invoice basics

If your business is registered under GST, your customers generally expect a proper invoice for each sale. A typical invoice shows your business name and address, your GSTIN, an invoice number and date, a description of what was sold, the amount, the tax charged and the buyer's details where needed. Many store platforms and accounting tools can create these automatically after payment.

Tell the customer clearly whether the price shown includes tax. Keep the payment records and invoices together so your accountant can reconcile them with the provider's statements. This is general information only and not legal or tax advice, because rules depend on your business type and turnover. Please confirm your invoicing and registration requirements with a qualified chartered accountant.

Security and card data

You do not want to store card numbers on your own server. A reputable payment gateway handles card data on its secure pages or fields, and it carries the heavy compliance work known as PCI DSS, the security standard for card data. When you use its hosted checkout or approved plugin, sensitive details never touch your website.

You still have jobs to do. Use HTTPS across the whole site, keep your platform and plugins updated, protect admin logins with strong passwords, and never share your secret API keys on chat or in public code. If a key leaks, replace it at once. Our website security checklist for small business covers the wider basics.

Test before you launch

Test mode lets you run through the full journey with pretend money. Do not skip it. Check at least these cases:

• A successful payment, and whether the order shows as paid.
• A failed payment, and whether the customer can try again.
• A cancelled payment, with the order left unpaid.
• Confirmation emails or WhatsApp messages reaching the right address.
• The invoice and the amount shown, including shipping and tax.
• A refund from the dashboard.
• Checkout on a real phone, not only on a laptop.

After switching to live mode, make one small genuine payment with your own money and refund it. That confirms the live keys are correct. Our website launch checklist can help you cover the rest of the launch.

Checkout trust tips

People abandon payment pages when something feels unsafe or unclear. A few simple habits help.

• Show the final amount, including shipping and tax, before the customer reaches the pay button.
• Display your business name, address, phone and email clearly.
• Link refund, shipping and privacy policies near checkout.
• Keep the payment page fast and readable on small phones.
• Offer the familiar methods, especially UPI.
• Do not make guest customers create an account if it is not needed.
• Send a clear confirmation message right after payment.

These points are not tricks. They simply reduce doubt for a shopper who is about to share money with a business they may not know.

When to ask for help

If you sell a few items, a payment link or a ready plugin may be enough to start. If you have a store, subscriptions, donations, a booking system or a custom order flow, a developer can connect the provider properly, test edge cases and set up emails and invoices. We have built 900+ websites and Shopify stores, and Ragnar Studios gives a custom quote after understanding your requirements. Provider charges are paid directly to the provider and are separate from our fees. See our ecommerce website development service for store builds.

Frequently asked questions