Choosing a payment gateway
A payment gateway connects your website or app to banks, UPI and card networks, so customers can pay online and you can receive the money. India has several good choices, and the right one depends on your business.
Popular gateways at a glance
| Gateway | Often chosen for | Notes |
|---|---|---|
| Razorpay | Stores, startups, subscriptions | Wide set of payment methods and good developer tools |
| PayU | Education and larger businesses | Long-established with many options |
| Cashfree | Marketplaces, payouts and UPI | Strong payout features |
| CCAvenue | Established e-commerce | Many payment options, including international |
Features and fees change, so always check current terms before you decide.
What to compare
- Fees per transaction and any setup or yearly charges
- Payment methods you need, such as UPI, cards, netbanking and wallets
- How quickly money is settled in your bank
- Quality of support and documentation
- Whether it works with your platform, such as WooCommerce or a custom app
Fees: what to ask about
- Transaction fee for each payment method
- Any setup, yearly or minimum charges
- Charges for refunds, failed payments or disputes
- How taxes on the fee are shown
- Different fees for international cards, if you need them
One gateway or two?
Depending on your transaction volume and reliance on online sales, operating with a single payment provider or dual gateways can make a decisive difference to your revenue stability.
A single gateway
When to choose one gateway
- Startups, small retailers, and service businesses launching their first online payment setup
- Centralizing all transaction fees, daily bank payouts, and refund processing in a single merchant dashboard
- Minimizing development complexity, ongoing API maintenance, and initial onboarding paperwork
Limits of one gateway
- If the gateway experiences temporary downtime or banking network latency, transactions fail until service is restored
- Limited leverage to negotiate lower platform processing fees across varying transaction sizes
Two gateways
When to choose two gateways
- High-volume e-commerce stores where even 15 minutes of payment gateway downtime causes lost orders
- Intelligent fallback routing that directs shoppers to a secondary gateway if the primary bank network slows down
- Separating domestic UPI and NetBanking from international credit cards (such as Stripe alongside Razorpay or Cashfree)
Limits of two gateways
- Requires managing dual merchant contracts, duplicate KYC compliance filings, and separate dashboard reconciliations
- Increases checkout frontend integration complexity and ongoing webhook event verification
Getting approved
Documents you usually need
- PAN of the business or the owner
- Proof of business registration, depending on its type
- A current bank account in the business name
- GST details, where applicable
- Identity and address proof of the owner or director
What your website must show
Gateways review your website before they approve it. Make sure it is live and professional.
- A clear description of what you sell, with prices
- Contact details and a business address
- Privacy policy, terms and conditions
- A refund and cancellation policy
- Working pages, with no placeholder text
How long approval takes
Test keys are often available at once, so development can start. Live approval depends on the gateway and on how complete your documents and website are, and may take several working days.
How integration works
The payment flow in plain steps
- The customer chooses to pay, and your site creates an order
- The gateway opens a secure payment page or window
- The customer pays by UPI, card or netbanking
- The gateway tells your server whether the payment succeeded
- Your site marks the order paid and sends a receipt
Why webhooks matter
A customer may close the browser after paying. A webhook is a message the gateway sends your server directly, so the order is still marked paid. We treat the webhook as the source of truth and verify its signature, so fake messages are ignored.
Test mode and live mode
- Build and test with test keys and sample payments
- Try failed, cancelled and delayed payments
- Switch to live keys only after everything passes
Test cases we run before launch
- A successful payment by each method
- A failed payment and a retry
- A customer who closes the page after paying
- A payment confirmed late by the gateway
- A full and a partial refund
Payment links and QR codes
If you do not need a full checkout, you can send payment links or show a QR code. This works well for service businesses and small sellers.
Payment methods
What customers expect
| Method | Why it matters | Watch out for |
|---|---|---|
| UPI | The most common way to pay in India | Failed payments need an easy retry |
| Cards | Used for higher-value orders | Extra verification can lose some buyers |
| Netbanking | Familiar to many customers | Bank pages can be slow |
| Wallets | Quick for repeat buyers | Limited reach |
| EMI and pay later | Helps with expensive items | Needs gateway approval |
Cash on delivery
Some customers still prefer to pay on delivery. We can add it with OTP confirmation, or a small advance on risky orders, to cut returns.
Subscriptions and recurring payments
Memberships, classes and software plans often need repeat billing. Many gateways support recurring payments, including UPI-based mandates, but rules and limits change, so we check the current options with you before we build.
Payments inside mobile apps
Apps need a smooth in-app checkout that returns the customer safely to the app after paying, even if the UPI app opens in between. Our app development team builds this flow and tests it on real phones.
Payment page checklist for your website
- Prices, taxes and delivery charges visible before payment
- Payment buttons that work on small screens
- A clear message after success, failure or delay
- Contact details for payment problems
Refunds, failures and reconciliation
Failed and duplicate payments
- Clear messages and an easy retry when a payment fails
- Protection against paying twice for one order
- Automatic checks when the status is unclear
When something goes wrong: a simple response plan
- Check the gateway dashboard first to see the real payment status
- Match the payment to the order using the reference number
- Tell the customer clearly what happened and what you will do
- Refund or complete the order within a promised time
- Note the cause and fix the underlying problem
Refunds
Full and partial refunds can be started from your admin panel. The money may take several working days to reach the customer's bank, so tell customers what to expect.
Disputes and chargebacks
Sometimes a customer questions a charge with their bank. Keep clear records: the order, delivery proof and messages. Respond within the time the gateway gives you. Good product pages and a clear refund policy prevent most disputes.
Settlement and reconciliation
The gateway pays out to your bank account after a settlement period that depends on the provider. We build reports that match each order to its payment and settlement, so your accountant can reconcile easily. For online stores, see our e-commerce development page.
Reconciliation checklist for your accountant
- Each order shows its payment reference
- Refunds are linked to the original order
- Gateway fees and taxes are shown separately
- A daily or weekly report matches bank settlements
GST invoices
The system can generate tax invoices for each paid order, with the right GST details.
Security
How we keep payments safe
- Card details are entered on the gateway's secure page, not stored on your server
- HTTPS on every page, on suitable web hosting
- Secret keys kept out of public code
- Signature checks on every gateway message
- Logs and alerts for unusual activity
Your responsibilities as the business
- Keep your gateway login and keys private
- Give staff only the access they need
- Check settlement reports regularly
- Update your website software and hosting
Where we integrate payments
Websites, stores and apps
- WooCommerce and custom online stores
- Booking and registration systems built by our web development team
- Mobile apps built with our app development team
- Subscriptions and recurring payments where the gateway supports them
A worked example: a small online store
Before
Customers pay by bank transfer and send screenshots, and orders are confirmed by hand.
What we build
- Checkout with UPI, cards and netbanking
- Orders marked paid from the gateway's verified message
- Automatic receipts and GST invoices
What changes
- Fewer manual checks and mistakes
- Faster confirmation for customers
- Reports that match your bank settlements
For different businesses
Stores need smooth checkouts, see ecommerce and retail. Booking systems need seat holds and refunds, see ticketing and booking. Institutes need fee payments and receipts, see education.
Mistakes and questions
Common payment mistakes
- Marking orders paid only from the browser, not from the gateway message
- No test of failed or delayed payments
- Missing refund and privacy policy pages, which delays approval
- No plan for reconciling payments with orders
Questions to ask before you hire
- Which gateways have you integrated, and on which platforms?
- How do you handle failed, duplicate and delayed payments?
- How will refunds and reports work?
- Who holds the gateway account and keys?