UPI is central to digital acceptance, but domestic collections, recurring commerce and export receipts have different onboarding and regulatory requirements.
An India payment strategy should begin with where the merchant is incorporated, which customer it serves, and what happens after checkout. UPI is a network—not a substitute for a payment aggregator, banking relationship, fraud program or export documentation.
India’s UPI is an NPCI-operated instant bank-to-bank payment system; the RBI’s 2025 payment-aggregator framework governs relevant provider activities.
These are different operating workflows. Select the closest scenario, then compare the rails and vendors with its constraints in mind.
For India-based commerce, start with UPI, cards and netbanking, then compare reconciliation and failed-payment handling.
SaaS, memberships and utility billing need mandate support, notification logic and retry paths—not just one-time checkout.
Indian exporters must evaluate cross-border payment aggregators, permissible transaction types and documentation, not assume local UPI capabilities work overseas.
Use this table to separate the payment method from the provider, the merchant contract and the underlying settlement mechanism.
Prominent for consumer and merchant payments through supported PSP and bank channels.
Merchant category, collection method, refund process, limits and payment status webhooks.
Source / product docs ↗Online and POS card acceptance through acquiring and payment aggregators.
Issuer/authentication performance, effective fees, refunds, and chargeback support.
Source / product docs ↗Subscriptions require consent, mandates, retries and clear customer controls.
Supported mandate rail, subscription recovery and applicable RBI e-mandate rules.
Source / product docs ↗Relevant where customers choose a direct banking workflow.
Bank coverage, redirect completion, settlement and operational fallbacks.
Source / product docs ↗International checkout into an Indian business often requires specialised settlement and transaction documentation.
PA-CB scope, allowed flows, FX spread and proof-of-remittance documents.
Source / product docs ↗Choose your operating use case before requesting a quote. A “supported country” label rarely tells you which legal entity, channel and settlement flow is included.
For India-based commerce, start with UPI, cards and netbanking, then compare reconciliation and failed-payment handling.
SaaS, memberships and utility billing need mandate support, notification logic and retry paths—not just one-time checkout.
Indian exporters must evaluate cross-border payment aggregators, permissible transaction types and documentation, not assume local UPI capabilities work overseas.
Authorities determine the operating framework. A provider’s merchant contract and first-party product documents then determine what your business can actually use.
The RBI’s September 2025 Master Direction consolidates its payment-aggregator rules, including cross-border activities. Verify authorisation and the specific entity delivering services.
RBI Master Direction ↗NPCI describes UPI as instant transfers between bank accounts. Merchants still need an authorised acquiring/PSP path and supported onboarding.
NPCI UPI FAQs ↗Cross-border merchant collections must be checked separately from domestic payment aggregation; ask how invoices, transaction purpose and settlement are evidenced.
RBI PA-CB framework ↗These are starting points for diligence, not endorsements or claims that each company can serve every merchant. We link directly to evidence and record meaningful limits.
Evaluate local collections and, separately, its published international payment gateway for eligible Indian sellers.
Evaluate UPI, cards, business tooling and integration for domestic Indian merchants.
Compare domestic acceptance, recurring use cases and enterprise integration.
Use NPCI materials to understand UPI and RuPay operating rails and participant roles.
Tick these off as you collect written answers. The selections stay on your device only; nothing is transmitted to PaymentSolutions.app.
We favour central banks, supervisory authorities, payments-system operators, standards bodies and original vendor documentation. Evidence categories show what each link supports.
Regulates payment aggregators and consolidates cross-border scope.
Read source ↗02 / Network operator / OfficialDefines UPI instant payment functionality and basic mechanics.
Read source ↗03 / Network operator / DataOfficial market and ecosystem reporting.
Read source ↗04 / Regulator / IndexUseful entry point for current RBI directions and updates.
Read source ↗05 / Provider / ScopeFirst-party documentation of offered international collection and settlement flows.
Read source ↗Provider features and regulatory scope can change. Each source is identified by type so merchants can distinguish authoritative policy from product marketing. Where a provider supports one country or payment method, this is not assumed to cover all legal entities, transaction types or channels. Reconfirm important claims directly before contracting.
No. NPCI operates UPI as an interoperable instant-payment system. Merchants generally obtain access through eligible banks, aggregators or PSP arrangements, with separate onboarding and settlement.
Eligibility depends on the acquiring and merchant setup. Do not infer domestic UPI acceptance from a provider’s general “India support” statement; confirm legal entity, settlement and product restrictions.
Not necessarily. Recurring mandates and authentication requirements can differ from one-time payments. Confirm current RBI requirements and the provider’s exact mandate workflow.
No. Export receipts introduce cross-border aggregator and foreign-exchange considerations, including settlement and transaction documentation.
Use the merchant assessment to convert this research into a practical list of requirements.
Build your payment brief ↗