India's payment stack combines UPI, cards, bank transfers and digital identity/data services. Operators need to assess customer eligibility, acceptance coverage, regulatory obligations and the chosen provider's actual commercial terms. UPI transaction counts and card adoption figures cannot be compared as market shares without the same period, channel, metric and denominator.
UPI — Account-to-Account Acceptance
Unified Payments Interface (UPI) is operated by NPCI (National Payments Corporation of India). Check current NPCI statistics for transaction volumes and their period; a count covering both person-to-person and merchant activity is not a checkout acceptance share. Confirm the customer account, app and supported payment flow for the integration.
UPI uses payment addresses and supported QR/app flows. Distinguish an app brand from the bank or authorised provider delivering the service, and confirm current participation and eligibility rather than relying on an old app-volume split.
The selected-merchant schedule remains deferred until a post-Diwali date still to be notified. The Department of Financial Services' FAQ describes a planned 0.4% MDR on selected P2M transactions above ₹2,000, capped at ₹300 for payments of ₹75,000 or more. P2P transfers, payments up to ₹2,000, qualifying P2PM micro-merchants, and UPI AutoPay mandates remain outside the prescribed MDR; certain sectors have separate rates. A merchant must model its transaction and category mix rather than assume the whole rail costs zero, and confirm the final implementation notice before quoting fees.
Confirm current NPCI and provider documentation for each cross-border corridor, visitor wallet or small-value flow. Merchant acceptance abroad, a bilateral transfer linkage and access to a domestic product are different capabilities; availability of one does not establish the others.
Payment Aggregator Framework
RBI's September 2025 Directions distinguish PA-Online, PA-Physical and PA-Cross Border. A bank does not require PA authorisation; a non-bank entity operating as a PA must seek it and be incorporated in India. A gateway within the separate PG definition is outside this PA Direction's scope. Determine the actual legal entity, activity and funds flow before applying the framework.
Section 6 sets minimum net worth of ₹15 crore at application and ₹25 crore by the end of the third financial year after authorisation. These are application/capital conditions, not a claim that every payment technology provider needs the same licence. The payment aggregator licensing guide provides further context; verify the proposed entity's current permission and product scope directly.
Card Market and RuPay
Cards and UPI serve overlapping customer and payment needs. Cards issued, cardholders, credit-card penetration and transaction share have different denominators; this page does not establish a comparable population penetration percentage or a current issuance growth rate.
RuPay debit treatment and bank-funded UPI merchant pricing are separate questions. The selected-UPI schedule remains deferred until a post-Diwali date still to be notified. Do not transfer that schedule to cards or infer that all debit-card acceptance is free. Obtain the applicable scheme/product rules and the merchant's actual acquiring quote.
EMI: compare the specific issuer, merchant, customer and product eligibility, amount, tenure, processing charges and merchant-funded subvention. A “No-Cost EMI” label does not establish universal availability above a single amount, no customer charges of any kind or a guaranteed conversion advantage.
Aadhaar eKYC and the India Stack
India Stack brings together several digital infrastructure capabilities. Evaluate each service's permitted use and access conditions separately:
Aadhaar: Identity services operated by UIDAI. Confirm the permitted authentication/eKYC route, eligible requesting entity, consent and applicable access conditions. Identity verification does not itself establish creditworthiness or guarantee a particular onboarding cost or time.
DigiLocker: A document-sharing capability. Confirm the documents and integration available for the chosen use case and the user-consent requirements; do not assume every document-collection step disappears.
Account Aggregator (AA): A consent-based financial-data-sharing framework. Check participant and recipient eligibility, the available data and the permitted purpose. Access to data is not a guarantee of instant underwriting or approval.
UPI: As described above — the payment execution layer.
Measure onboarding completion, operational effort and customer outcomes for the chosen integration; no universal efficiency or conversion improvement is assumed.
BNPL
For BNPL or card instalments, identify the actual lender, borrower eligibility and contractual product. Merchant-funded EMI and another provider's deferred-credit offer need not have the same charges, customer terms or integration conditions; no common market-share or minimum-ticket claim is established here.
For an instalment-credit integration, establish the actual regulated lender, provider role, customer disclosures, affordability/eligibility process and repayment/dispute terms. Do not assume every product must use an NBFC partnership, that the presence of a named lender proves compliance or that one checkout route is inherently lower risk.
Crypto and Digital Assets
A tax treatment, registration or adoption ranking does not establish that a particular digital-asset payment product is permitted or appropriate for a merchant. Before offering one, verify the current legal entity, activity, applicable regulatory position, tax and reporting obligations, banking access and customer protections. This guide does not certify a crypto provider, assert SEBI oversight of all token platforms or predict a provider's INR launch.
Regulatory Environment
Use the actual Indian rules and the proposed activity to determine obligations. For PA business, start with the RBI Directions above. Storage, processing location, privacy, lending, foreign exchange and tax have separate scopes and implementation conditions; do not assume the GDPR is an equivalent compliance checklist or that a blanket all-data localisation sentence resolves a particular architecture.
For an implementation review, identify the controller/processor and regulated entities, data categories and locations, subcontractors, cross-border funds and data flows, contract allocation and the specific applicable provisions. Resolve uncertain scope with the relevant regulator material and qualified local advice before committing the design.
Practical Notes for Operators
Provider selection. Verify the legal contracting entity, current permissions, account/product eligibility, supported methods, commercial terms and reporting. Provider names in another market or a general corporate licence do not establish availability for this merchant and flow. No preferred-vendor or universal startup/enterprise ranking is established here.
Funding. Confirm capture, processing, funds availability, payout initiation and bank receipt separately. The chosen product and account terms determine merchant funding; no universal T+0/T+1 card or UPI payout schedule applies here.
Tax. Establish the applicable services, entity, transaction, tax status and invoicing treatment before modelling indirect taxes or cross-border fees. No universal processing-service GST rate or tax advice is established by this guide.
Banking. Ask the chosen institution for account eligibility, required documents, onboarding dependencies and the applicable foreign-exchange/remittance process. No four-to-eight-week account-opening commitment or preferred-bank list is established here.
Language. Test onboarding, checkout and support language with the actual customer population. Do not substitute a national language assumption for evidence about the intended users.