← Back

Country payment guide

How customers pay in India

India requires method-by-segment planning before PSP selection. Merchants should compare UPI-style account payments, wallets, cards, netbanking, payment links, subscriptions and invoice flows against the buyer journey, then ask each PSP which options can be activated for their entity and industry. Confirm domestic compliance documentation, refunds, failed-payment handling, settlement currency, chargebacks and recurring-payment rules before engineering starts.

Which PSPs and payment routes can you explore in India?

Existing research for India includes Cashfree Payments, PayU India, BillDesk, SBI Payments, PhonePe, Paytm. Explore their products and local payment methods, then use your business and company location to narrow the enquiries.

No local company, or no clear contact route?

These are research leads, not approval or industry-support guarantees. Tell us the market and your company location so we can help you explore further.

11Channel recordsPublic directory entries
AsiaRegionIN
Usually requires a local entityOnboardingFrom structured fields
T+1, Real-time / T+0SettlementVerify on detail pages

Curated market guide

India PSP routes to verify first

Which PSPs or bank routes should a merchant ask first for UPI, cards, wallets, netbanking, and local payment links in India?

4
local_psp_or_aggregator · curated

Indian PSP / gateway shortlist

Cashfree PaymentsPayU IndiaCCAvenueEasebuzz

Use when you need UPI, cards, wallets, netbanking, and payment links through a familiar Indian PSP evaluation.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
acquirer_or_bank · curated

Bank/acquirer or enterprise route

BillDeskSBI PaymentsNTT DATA Payment Services IndiaPlural by Pine Labs

Use when enterprise acquiring, bank-grade reconciliation, or domestic rails are central to the operating model.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
direct_scheme_or_wallet · curated

UPI wallet and scheme route

PhonePePaytmAmazon PayZaakpay (MobiKwik)

Use when checkout strategy depends on consumer wallet/UPI brand recognition and direct or PSP partner access must be verified.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
international_psp · curated

Cross-border or specialized PSP route

PayGlocalDecentroJuspay

Use when the merchant needs cross-border, orchestration, or embedded finance support and will verify eligibility case by case.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
KYB prep

Documents to prepare

  • Company registration and PAN/GST or foreign-entity onboarding question
  • Beneficial-owner and signatory ID
  • Website/app URL, product category, refund policy
  • Bank account and settlement-currency requirements to verify
  • RBI/KYC or regulated-business questions where relevant
Due diligence

Questions to ask

  • Can my current merchant entity onboard for this market, or is a local company required?
  • Which local payment methods are actually enabled for my merchant category and transaction model?
  • Which documents are required for KYB, website/app review, tax review, and beneficial-owner checks?
  • Which checkout flows, APIs, plugins, hosted pages, refunds, disputes, webhooks, and reconciliation files are supported?
  • Which payout currencies, FX handling, reserves, chargeback process, taxes, and support SLAs should be confirmed before launch?
Contact route fallback

If the official contact route is unclear

If public contact details are not specific enough, ask LocalPayMap to identify the right official form, PSP sales route, or local acquiring partner before committing engineering work.

  • Which local payment methods are actually enabled for my merchant category and transaction model?
  • Which documents are required for KYB, website/app review, tax review, and beneficial-owner checks?
  • Which checkout flows, APIs, plugins, hosted pages, refunds, disputes, webhooks, and reconciliation files are supported?
  • Which payout currencies, FX handling, reserves, chargeback process, taxes, and support SLAs should be confirmed before launch?

How customers actually pay here

India checkout often involves UPI, domestic and international cards, RuPay, netbanking, wallets, and cash-on-delivery in some ecommerce categories. The right mix depends on buyer segment, ticket size, provider eligibility, local entity setup, and risk review. Confirm UPI availability, limits, confirmation, refunds, disputes, settlement, reconciliation, and payout route before treating any method as default.

  • UPI is a major Indian payment route to evaluate, but availability and operating rules depend on provider and merchant eligibility.
  • PhonePe, Google Pay, Paytm, and other apps may be buyer entry points into UPI rather than separate merchant contracts.
  • RuPay, Visa, and Mastercard can matter for higher-value and credit-driven purchases.
  • Netbanking can remain relevant for bill-like or higher-value one-off payments.
  • Cash-on-delivery should be evaluated only with logistics, returns, and reconciliation costs included.

Payment methods to prioritise first

Evaluate UPI early for Indian buyers, then compare domestic cards including RuPay, netbanking, wallets, and cash-on-delivery only where your fulfilment model supports it. UPI access, transaction limits, confirmation flow, refunds, settlement, and reconciliation depend on provider setup and merchant eligibility, so confirm those details before you promise the route in checkout. Treat the launch order as a test plan based on buyer mix, ticket size, and approval requirements.

  • Shortlist UPI early where your audience expects it, then verify provider access, limits, pricing, refunds, and settlement.
  • Add RuPay plus Visa and Mastercard to capture higher-value and credit purchases.
  • Turn on netbanking if you sell subscriptions, fees or anything invoice-like.
  • Treat wallets as incremental coverage rather than a separate project.
  • Only offer cash on delivery once your returns process can absorb it.

How merchants usually connect

Merchants commonly investigate aggregators, gateways, cross-border receivables providers, and in-store acquiring routes rather than integrating each payment method separately. Treat Razorpay, Cashfree Payments, PayU India, CCAvenue, BillDesk, Juspay, Easebuzz, Instamojo, Paytm for Business, PhonePe, Skydo, Xflow, PayGlocal, Tazapay, Pine Labs, and Mswipe as candidates to verify, not proof that your entity or vertical is approved. Ask which methods are enabled for your account, which entity and bank details are required, and where settlement lands.

  • Ask aggregators which UPI, card, netbanking, and wallet routes are actually approved for your entity and industry.
  • Payment links may suit smaller sellers, but identity verification and settlement requirements still apply.
  • Cross-border receivables providers can be relevant for foreign entities, subject to trade documentation and provider approval.
  • Offline collection routes should be evaluated separately from online checkout.
  • Always confirm whether settlement goes to an Indian bank account or to an account abroad.

Operating without a local company

Do not assume a foreign entity can access Indian domestic payment routes on the same terms as an Indian company. Domestic UPI, card acquiring, rupee settlement, recurring mandates, data handling, documentation, and payout abroad depend on provider licensing, merchant entity, bank-account setup, product category, risk review, and India foreign-exchange rules. Some cross-border receivables or international acquiring routes may support selected foreign merchants, but the exact route must be confirmed before build work starts.

  • Ask whether UPI, RuPay, domestic cards, netbanking, and wallets require an Indian entity or bank account for your setup.
  • Confirm whether a cross-border card or receivables route can support the actual goods or services sold.
  • Expect additional documentation, trade evidence, and longer review for cross-border collection.
  • Recurring billing and mandate flows need separate confirmation.
  • Compare local-entity setup only after volume, compliance cost, and operational ownership are clear.

What to ask a provider before you sign

Treat the first call as a checklist, not a demo. Ask which methods are live for your industry rather than which methods exist on the website, because approval is granted method by method. Ask what documents onboarding needs and how long approval has actually taken for merchants like you. Ask how settlement works: which account, which currency, on what cycle, and what happens around holidays. Ask who owns the dispute and refund workflow, and what evidence you must supply. Ask about additional authentication on card payments, because it changes success rates. Ask what happens if volume spikes or your category is reclassified. Finally, ask for the fee schedule in writing, including refund, dispute and payout charges.

  • Confirm which payment methods are approved for your specific industry, not just supported in general.
  • Get the full document list and a realistic onboarding timeline before you commit engineering time.
  • Ask exactly which account and currency receives settlement, and on what cycle.
  • Clarify who handles disputes and refunds, and what evidence you must provide.
  • Request every charge in writing, including refund, dispute and payout fees.

Fees, settlement and FX

Public pricing is only a first filter. Actual pricing changes with country, industry, volume, settlement currency, integration method and contract terms, so confirm against the provider's official pricing page or a written quote before you go live. Beyond the headline rate, the numbers that decide your margin are the settlement cycle, the payout fee, the refund and dispute charges, and the spread applied when rupees are converted. Ask whether settlement is net or gross, whether a rolling reserve applies, and how long funds are held before a first payout. If you collect into a foreign account, model the conversion cost as a real line item rather than a rounding error, and get the reference rate in writing.

  • Public rate cards are a starting filter and never a commitment.
  • The settlement cycle and payout fee often matter more than the headline percentage.
  • Refund and dispute charges should be quoted separately and in writing.
  • Ask how the rupee conversion rate is set if you settle in another currency.
  • Check whether a reserve is held against your balance and for how long.

Industry notes

For ecommerce, digital goods, games, short drama, SaaS, subscriptions, B2B, and services, method priority should be tested against buyer segment, ticket size, entity eligibility, recurring-payment rules, FX, refund process, and provider approval. UPI, cards, RuPay, netbanking, bank transfer, and cash-on-delivery can each be relevant in different cases, but none should be promised until the provider confirms support for your entity, industry, and settlement route.

  • For ecommerce, compare UPI, cards, RuPay, netbanking, and cash-on-delivery with returns and reconciliation costs included.
  • For digital goods, games, and short drama, confirm low-ticket payment flow, limits, refunds, and dispute handling before launch.
  • For SaaS and subscriptions, verify recurring card, mandate, retry, cancellation, and evidence rules in writing.
  • For B2B and services, align invoice currency, collection route, trade evidence, and payout currency.
  • Keep industry approval separate from generic method support.

Risks, compliance and common mistakes

The biggest planning risk for foreign sellers is not the checkout, it is getting money out. Rupee balances sit inside a controlled foreign exchange framework supervised by the Reserve Bank of India, so repatriation depends on your documentation, your provider's licence and the nature of the transaction. Cross-border settlement is slower than domestic settlement and is the step most teams underestimate. Storage of certain payment data is regulated locally, so ask where card and transaction records will live. Wallet-style balances sit under prepaid instrument rules, which means your partner needs the right authorisation. Operationally, additional authentication on card payments lowers success rates when it is implemented badly, and UPI has a formal complaint and reversal process even though it carries no card-style chargeback.

  • Plan repatriation and supporting documents before you plan the checkout.
  • Cross-border settlement into a foreign account takes longer than domestic rupee settlement.
  • Ask where card and transaction data is stored, because local storage rules apply.
  • Confirm your partner holds the right authorisation for wallet-style balances.
  • UPI carries no card chargeback but it does have a formal complaint and reversal process.

Next actions

Next actions for India

Use these internal paths to move from market research to provider outreach without assuming eligibility, pricing, settlement, or local-entity access.

Questions merchants ask

Do I need a local company to accept payments in India?

It depends on the route. Domestic acquiring, UPI, rupee settlement, and some recurring flows may require an Indian entity, local bank account, or locally approved partner, while some international acquiring or cross-border receivables routes may support selected foreign merchants. Confirm entity, bank, documentation, payout currency, and industry requirements with each provider in writing.

Which payment method should I add first in India?

Evaluate UPI early when account-to-account or QR behavior matters, then compare RuPay, Visa, Mastercard, netbanking, wallets, and other routes against buyer segment and provider eligibility. Confirm provider support, pricing, payment confirmation, payout timing, refunds, disputes, reconciliation, transaction limits, and support ownership before treating any method as the launch default.

How long does settlement take in India?

Settlement timing is provider- and contract-specific. Ask for the payout cycle, first-payout rules, reserve policy, holidays, failed-payout process, settlement currency, FX conversion, refund timing, dispute handling, and reconciliation files in writing before launch.

What does it cost to accept payments in India?

Public pricing is only a first filter. Actual pricing changes with country, industry, volume, settlement currency, integration method and contract terms, so confirm against the provider's official pricing page or a written quote before you go live. Look past the headline percentage at payout fees, refund and dispute charges, any reserve, and the spread on currency conversion. Those four items usually move your margin more than the transaction rate does.

Can I get paid in USD or EUR from Indian customers?

Possibly, but the route depends on provider licensing, India foreign-exchange requirements, trade documentation, merchant entity, product category, and contract terms. Ask the provider to confirm collection flow, payout currency, FX spread, evidence requirements, refunds, disputes, and whether the route is available for your exact business.

What are the chargeback and refund risks in India?

Card payments carry standard scheme chargeback rights, so keep delivery evidence, clear descriptors and a visible refund policy. UPI works differently: there is no card-style chargeback, but there is a formal complaint and reversal process, and reversals still hit your books. Refunds on account-to-account payments can take longer to reflect than the original payment. Agree dispute handling, evidence formats and any per-case fee with your provider before launch.

Can a small shop accept payments in India without a website?

Yes. Most aggregators issue a static or dynamic collection code and hosted payment links, so you can take UPI and card payments over chat, social media or in person with no site at all. Reconciliation appears in the provider dashboard. Instamojo and the merchant products from Paytm for Business and PhonePe are common choices for this. You still need to complete identity verification and link a bank account.

Public sources