India Payments & Fintech Regulation

IN schema world-payments-v1 trajectory: not yet assessed

Last updated · 14 modules · 128 sourced findings · 160 sources in the cumulative register

Jurisdiction brief

Latest update · 25 October 2026

Lead Signal

India's payments market this period delivered two distinct signals rather than one dominant theme: a continued widening of the Reserve Bank of India's non-bank Payment Aggregator roster, and a commercial investment touching the stablecoin-infrastructure end of the market. Spice Money Limited, the subsidiary of DigiSpice Technologies, received in-principle RBI authorisation to operate as a Physical Payment Aggregator (PA-P) on 24 October 2026. This is the licensing track the Reserve Bank uses specifically for aggregators handling face-to-face, physical-point card and payment transactions, as distinct from the online Payment Aggregator (PA-O) authorisation track. The approval extends a roster that already includes Paytm Payments Services, CRED/Dreamplug and Airpay, among others, and reads as incremental expansion along an established licensing pattern rather than a policy shift in how the Reserve Bank treats non-bank aggregators.

Key regulatory facts for India
Regulatory DimensionIndia Standing Position
JurisdictionIndia (IN)
Regulatory ScopePayments & Fintech Regulation (14 modules, 128 sourced findings)
Licensing, Authorisation & Market AccessRBI's consolidated Payment Aggregator Directions, 2025 (effective 15 Sept 2025) rationalised and repealed the 2020/2021 PA-PG Guidelines and the 2023 cross-border PA framework, creating PA-Online, PA-Cross-Border and...
Conduct, Safeguarding & PromotionsCustomer-fund safeguarding for both PAs and non-bank PPI issuers rests on a mandatory escrow account held with a single scheduled commercial bank, with no co-mingling, day-end balance floors, and quarterly...
Stablecoins & Digital MoneyIndia's digital-money posture is CBDC-led and stablecoin-sceptical.
Operational Resilience & Critical InfraOperational resilience for payments rests on the RBI Master Directions on Cyber Resilience and Digital Payment Security Controls for non-bank PSOs (July 2024), the Master Direction on IT Governance, Risk, Controls...
Primary Instruments CitedRBI (Regulation of Payment Aggregators) Directions 2025 (15 Sep 2025) (rbi.org.in), RBI PA Directions 2025 — ₹15cr/₹25cr net worth (rbi.org.in), India Official Instrument (mondaq.com part-i-rbi-proposes-regulation-l), India Official Instrument (businesstoday.in rbi-grants-payment-aggregator-li), Payment and Settlement Systems Act, 2007, s.4(1)
Last Confirmed / Updated2026-11-04 (160 sources in cumulative register)

#

RBI's consolidated Payment Aggregator Directions, 2025 (effective 15 Sept 2025) rationalised and repealed the 2020/2021 PA-PG Guidelines and the 2023 cross-border PA framework, creating PA-Online, PA-Cross-Border and PA-Physical categories, with rolling compliance deadlines through 2026.

Movement — CHANGEDDraft PPI Master Direction 2026 under public consultation, to replace 2021 framework.New draft instrument surfaced this cycle, consultation period closed 22 May 2026.
Horizon · 2026-03-31 (± a quarter)PA-CB net-worth threshold deadlineAdopted, not yet in force · Tier 3 source
Horizon · 2025-12-31 (± a quarter)Offline PA authorisation deadlineAdopted, not yet in force · Tier 2 source
Horizon · 2026-09-15 (± a quarter)Extended merchant-CDD compliance deadlineAdopted, not yet in force · Tier 3 source
Horizon · 2026-03-31 (± a quarter)PA-CB net-worth threshold deadlineAdopted, not yet in force · Tier 3 source
Horizon · 2026-02-28 (± a quarter)PA-P wind-up deadline for non-authorised entitiesAdopted, not yet in force · Tier 1 source
Horizon · 2026-09-15 (± a quarter)Extended CDD remediation deadline for pre-2026 merchantsAdopted, not yet in force · Tier 2 source
Horizon · 2026-09-15 (± a quarter)Merchant CDD compliance extended deadlineAdopted, not yet in force · Tier 3 source
Horizon · 2026-05-22 (± a quarter)Draft PPI Master Direction 2026 consultation closedConsultation · Tier 2 source
Standing sub-brief · as of 27 June 2026 247 words · last cycle 2026-10-25

Licensing, Authorisation & Market Access

India's payment-aggregator licensing perimeter has moved from transition into full operation. The RBI (Regulation of Payment Aggregators) Directions, 2025, issued 15 September 2025 and effective immediately, require non-bank payment aggregators to obtain RBI authorisation under the PSS Act, carrying a Payment Aggregator authorisation under Section 7 with no exemption available. The prudential ladder sets net worth at INR15cr at application, rising to INR25cr by the end of the third financial year, alongside escrow-only settlement and Companies Act 2013 incorporation.

Periodic update · new data 2026-10-25

Licensing, Authorisation & Market Access

Spice Money Limited, the DigiSpice Technologies subsidiary, obtained in-principle authorisation from the Reserve Bank of India to operate as a Physical Payment Aggregator on 24 October 2026. The Physical Payment Aggregator category, commonly abbreviated PA-P, is the Reserve Bank's authorisation track for non-bank entities handling face-to-face, point-of-sale and other physical-channel payment aggregation, distinct from the online Payment Aggregator (PA-O) track that covers e-commerce and digital-channel flows. The in-principle nature of the approval indicates that Spice Money has cleared an initial authorisation stage and would be expected to move through further conditions before any grant of full authorisation, consistent with the Reserve Bank's standard sequencing for aggregator licensing.

This approval extends a roster of non-bank Payment Aggregators that already includes entities such as Paytm Payments Services, CRED/Dreamplug and Airpay. Read against that existing roster, the Spice Money authorisation looks like continuation of an established licensing pattern at the Reserve Bank rather than any shift in criteria, pace, or regulatory posture toward non-bank aggregators. No change to the underlying Payment Aggregator framework itself was evidenced this period; the development is a market-access event for a specific applicant, not a framework development.

Spice Money's existing business is built on last-mile and rural financial services distribution, so the physical aggregator authorisation would, if it proceeds to full authorisation, extend the formal payment-aggregation regulatory perimeter to cover a segment of the market already engaged with physical, assisted-channel transactions rather than purely online commerce. No further detail on conditions attached to the in-principle approval, or on an expected timeline to full authorisation, was located in the sources available this period.

Outlook

The next material marker for this entry is whether Spice Money's in-principle authorisation converts to full Payment Aggregator authorisation, and on what further conditions. Beyond this specific case, the broader question for market access is whether the Reserve Bank's roster of PA-P and PA-O authorisations continues to expand at the same incremental pace, or whether any change in criteria, processing time, or policy emphasis becomes visible across a wider set of applicants in subsequent periods. No signal pointing toward either acceleration or tightening was present in the material reviewed.

4 earlier distinct update(s)
Periodic update · new data 2026-09-28

Licensing, Authorisation & Market Access

The Reserve Bank of India's Payment Aggregator Master Directions, 2025 bring offline Payment Aggregators under authorisation for the first time, closing a gap in the licensing perimeter that had previously applied only to online payment aggregation. Offline PAs — those handling point-of-sale acceptance and same-location instrument transactions — must now apply for RBI authorisation, with existing offline PAs required to submit applications by 31 December 2025 or wind down operations entirely by 28 February 2026. This is a scope-widening development rather than a tightening of existing rules: it extends the authorisation perimeter to a category of non-bank payment intermediary that had not previously required it.

A parallel development affects the PA-CB (cross-border Payment Aggregator) authorisation category: its permitted scope has been liberalised to cover processing of permissible current-account transactions under FEMA, where it had previously been confined to trade transactions only. This is a market-access widening for cross-border payment aggregators, expanding the transaction types they may lawfully process under their existing authorisation.

On the compliance-timeline side, an extended deadline to 15 September 2026 has been granted for merchant customer-due-diligence compliance, but only for merchants onboarded up to 31 December 2025; no equivalent leeway applies to merchants onboarded from 1 January 2026, who face immediate CDD compliance expectations. Non-bank PAs, including the new offline PA-P category, are confirmed as PMLA reporting entities required to register with FIU-IND — an AML-compliance overlap that connects to financial-integrity's coverage of India's reporting-entity architecture but is not analysed further here. Throughout this domain, the bank-versus-non-bank distinction is structurally significant: these authorisation and CDD obligations fall on non-bank payment institutions and e-money institutions, not on banks directly.

Outlook

The two dates to track are 31 December 2025, the offline-PA authorisation application deadline, and 28 February 2026, the wind-down deadline for non-compliant offline PAs. The 15 September 2026 merchant-CDD extended-compliance deadline is the third near-term milestone, after which no further leeway is anticipated for merchants onboarded from 1 January 2026 onward.

Periodic update · new data 2026-09-22

Licensing, Authorisation & Market Access

The Reserve Bank of India's consolidated Regulation of Payment Aggregators Directions, 2025, effective 15 September 2025, rationalises and repeals what had previously been three separate regulatory frameworks — the 2020 and 2021 PA-PG Guidelines and the 2023 cross-border payment-aggregator framework — into a single directions document. The consolidated framework establishes three distinct licensing categories: PA-Online, PA-Cross-Border and PA-Physical, replacing what had been a fragmented, incrementally-built licensing architecture with a single coherent instrument.

The consolidation carries substantive compliance consequences with hard deadlines. PA-P entities that did not submit an authorisation application to the RBI by 31 December 2025 are required to wind up their PA-P operations entirely by 28 February 2026 — a genuine market-exit consequence for non-compliant entities, not merely a procedural lapse. Separately, payment aggregators were given an extended customer-due-diligence remediation timeline running to 15 September 2026 for merchants that had been onboarded before 31 December 2025, reflecting a rolling compliance window built into the same 2025 Directions rather than a new, unrelated obligation.

Taken together, these developments mark a maturing, more prescriptive supervisory posture for India's payment-service-provider sector. The consolidation itself is a structural simplification, but the accompanying deadlines — a hard wind-up date for non-compliant PA-P entities and a rolling merchant-KYC remediation timeline — indicate that the RBI is treating the new framework as an enforceable compliance architecture rather than a restatement of existing practice. Non-bank payment institutions and e-money institutions bear the primary compliance burden of this consolidation, distinct from bank-operated payment aggregators, which sit within existing prudential supervision.

Outlook

The 28 February 2026 PA-P wind-up deadline and the 15 September 2026 extended CDD remediation deadline are the two concrete compliance markers to track through the remainder of this cycle and into early 2026. Both are confirmed, dated obligations under the same 2025 Directions rather than open proposals, and non-compliance carries a genuine market-access consequence for affected payment aggregators.

Periodic update · new data 2026-09-14

Licensing, Authorisation & Market Access

The Reserve Bank of India's Draft Master Direction on Prepaid Payment Instruments, 2026 tightens governance requirements for non-bank PPI issuers, mandating fit-and-proper promoter and director criteria and bringing PPI customer onboarding directly within the RBI's own KYC framework rather than leaving it to issuer-level policy. This consolidates non-bank payment regulation under a same-activity, same-risk, same-regulation principle, narrowing the gap between how banks and non-bank prepaid-instrument issuers are governed. The direction remains in draft form, so its final scope and effective date are not yet settled, and this assessment is probable rather than confirmed.

Separately, the Payment Aggregator authorisation regime under the Payment and Settlement Systems Act 2007 continues without material change: more than 60 entities hold in-principle or final RBI Payment Aggregator authorisation as of 2026, and the net-worth threshold for that category remains at ₹15-25 crore. This is a distinct authorisation category from PPI issuance and from banking licensure, and its continuity this cycle indicates a stable, if still-maturing, market-access structure for payment aggregation specifically, even as the PPI governance standard is being actively raised.

The bank-versus-non-bank distinction is material here: the PPI tightening applies specifically to non-bank PI/EMI issuers, since banks are already subject to RBI's banking-license-level KYC and governance standards. The effect of the Draft Master Direction, if finalised as proposed, would be to narrow rather than eliminate this bank/non-bank regulatory gap.

Outlook

The key near-term development to track is whether the Draft Master Direction is finalised in its current form, amended following industry consultation, or delayed. Any change to the promoter fit-and-proper criteria or the KYC-integration requirement between draft and final stage would materially affect non-bank PPI issuers' market-access planning.

Periodic update · new data 2026-09-08

Licensing, Authorisation & Market Access

The Reserve Bank of India's rewritten Payment Aggregator Directions, reference RBI/DPSS/2025-26/141 and notified 15 September 2025, constitute a confirmed, high-impact, comprehensive rewrite of the licensing and market-access framework for payment aggregators in India. The central structural innovation is the introduction of an Offline PA category for the first time, bringing offline-context payment aggregation into an authorisation regime that had previously applied only to online aggregation. The directions explicitly repeal the prior 2020 intermediary-transactions circular except for decisions already pending authorisation, a confirmed finding that establishes a clean regulatory handover rather than an overlapping dual regime.

The new framework carries distinct compliance timelines for different aggregator sub-categories. Existing offline PAs were required to apply for RBI authorisation by 31 December 2025, a probable-confidence deadline; critically, this leeway is not available for merchants onboarded after 1 January 2026, who face the new requirements immediately upon onboarding rather than benefiting from any transition window. This bifurcation means firms operating offline-PA business lines must track two distinct compliance populations -- pre-existing merchants under a grace period, and new merchants under immediate compliance -- within the same regulatory category.

Cross-border payment aggregators (PA-CBs) see a combined liberalisation and tightening. Their permissible scope is liberalised: PA-CBs may now process any permissible current-account transaction under FEMA, rather than being restricted to trade transactions alone, a probable-confidence expansion of their addressable business. This liberalisation is paired with a new INR 25 crore net-worth requirement, due by 31 March 2026, meaning the broadened scope of permissible activity is conditioned on a materially higher capital base than may have previously applied to smaller cross-border aggregators. Separately, non-bank payment aggregators, including the newly created offline PA-P category, are confirmed as PMLA reporting entities that must register with FIU-IND, carrying this finding through from the AML-adjacent scope of the same directions rather than from original AML analysis produced here.

Throughout this framework, the distinction between bank-affiliated PSPs and non-bank payment institution/e-money-institution aggregators remains operationally significant: the net-worth threshold, authorisation deadlines and PMLA registration obligations bear most directly on the non-bank PI/EMI population, which had previously operated under lighter-touch oversight relative to bank-affiliated payment processors.

Outlook

The compliance calendar is front-loaded through the first three quarters of the 2025-26 to 2026-27 window: the offline-PA authorisation deadline of 31 December 2025 has already passed, an extended merchant-CDD compliance deadline runs to 15 September 2026 for merchants onboarded before 31 December 2025, and the PA-CB net-worth threshold falls due 31 March 2026. Supervisory attention through this period is likely to concentrate on authorisation-status verification for offline PAs and net-worth compliance for cross-border aggregators. Watch for RBI guidance clarifying the merchant-CDD extended-deadline population and for any enforcement action against aggregators that miss the passed 31 December 2025 offline-PA authorisation deadline.

Sources and findings (23)
  1. T1RBI (Regulation of Payment Aggregators) Directions 2025 (15 Sep 2025) (rbi.org.in)
  2. T1RBI PA Directions 2025 — ₹15cr/₹25cr net worth (rbi.org.in)
  3. T3https://www.mondaq.com/india/corporate-and-company-law/877826/part-i-rbi-proposes-regulation-licensing-of-payment-aggregator-and-gateways [CAVEAT: Tier 3 secondary source — Assessed; verify vs primary pre-publication]
  4. T3https://www.businesstoday.in/latest/corporate/story/rbi-grants-payment-aggregator-licence-to-32-entities-heres-the-full-list-370397-2023-02-15 [CAVEAT: Tier 3 secondary source — Assessed; verify vs primary pre-publication]
  5. T1Payment and Settlement Systems Act, 2007, s.4(1) — Payment and Settlement Systems Act, 2007, s.4(1) — No person other than the Reserve Bank may commence or operate a payment system except under and in accordance with an RBI authorisation.retrieved
  6. T3Spice Money Limited — Spice Money Limited — In-principle RBI authorisation as a Physical Payment Aggregator (PA-P)retrieved
  7. T2RBI Payment Aggregator Master Directions, 2025 — RBI Payment Aggregator Master Directions, 2025 — Offline PAs (point-of-sale, same-location instrument/acceptance) regulated for the first time; existing offline PAs required to apply for RBI authorisation by 31 December 2025 or wind down by 28 February 2026.retrieved
  8. T1Reserve Bank of India — Reserve Bank of India — RBI/DPSS/2025-26/141, notified 15 September 2025, comprehensively rewrites the Payment Aggregator framework, introducing an Offline PA category for the first time.retrieved
  9. T22025 Payment Aggregator Directions — 2025 Payment Aggregator Directions — Explicitly repeals the prior 2020 intermediary-transactions circular except for pending authorisation decisions.retrieved
  10. T2Non-bank Payment Aggregators (including PA-P offline category) — Non-bank Payment Aggregators (including PA-P offline category) — Non-bank PAs, including the new PA-P (offline) category, are confirmed as PMLA reporting entities and must register with FIU-IND.retrieved
  11. T3Offline Payment Aggregators (India) — Offline Payment Aggregators (India) — Existing offline PAs were required to apply for RBI authorisation by 31 December 2025; this leeway is not available for merchants onboarded after 1 January 2026.retrieved
  12. T3Cross-Border Payment Aggregators (PA-CB) — Cross-Border Payment Aggregators (PA-CB) — PA-CBs gain liberalised scope, now permitted to process any permissible current-account FEMA transaction rather than only trade transactions, subject to an INR 25 crore net-worth requirement by 31 March 2026.retrieved
  13. T3Reserve Bank of India — Draft Master Direction on Prepaid Payment Instruments, 2026 — Reserve Bank of India — Draft Master Direction on Prepaid Payment Instruments, 2026 — Mandates fit-and-proper promoter/director criteria and brings PPI customer onboarding directly within RBI KYC frameworkretrieved
  14. T3RBI Payment Aggregator authorisation regime — RBI Payment Aggregator authorisation regime — Over 60 entities hold in-principle or final RBI Payment Aggregator authorisation as of 2026; net-worth threshold ₹15-25 croreretrieved
  15. T1Reserve Bank of India — Reserve Bank of India — RBI (Regulation of Payment Aggregators) Directions, 2025 (effective 15 Sept 2025) rationalise and repeal prior 2020/2021 PA-PG Guidelines and the 2023 cross-border PA framework, creating PA-Online, PA-Cross-Border and PA-Physical categories.retrieved
  16. T1PA-P entities (India) — PA-P entities (India) — PA-P entities without an RBI authorisation application by 31 Dec 2025 must wind up PA-P operations by 28 Feb 2026.retrieved
  17. T2India payment aggregators — India payment aggregators — Extended CDD-compliance timeline to 15 September 2026 for merchants onboarded before 31 December 2025.retrieved
  18. T3Non-bank Payment Aggregators (India) — Non-bank Payment Aggregators (India) — Non-bank PAs, including the new PA-P offline category, are confirmed reporting entities and must register with FIU-IND and comply with PMLA/KYC Directions.retrieved
  19. T3Payment Aggregator merchant CDD compliance timeline — Payment Aggregator merchant CDD compliance timeline — Extended timeline (to 15 September 2026) granted for merchant CDD compliance on merchants onboarded up to 31 December 2025; no leeway for merchants onboarded from 1 January 2026.retrieved
  20. T3PA-CB (cross-border Payment Aggregator) regime — PA-CB (cross-border Payment Aggregator) regime — PA-CB liberalised to permit processing of permissible current-account transactions under FEMA, not merely trade transactions as before.retrieved
  21. T3Payment Aggregators (India) — Payment Aggregators (India) — One-year deadline (15 September 2026) for merchant re-KYC under RBI's Sept 2025 Master Direction on Payment Aggregators has passed; aggregators report completing only ~80% of the verification backlog and have sought additional time from RBIretrieved
  22. T1Master Direction on Regulation of Payment Aggregators, 2025 — Master Direction on Regulation of Payment Aggregators, 2025 — Non-bank Payment Aggregators must hold minimum net worth of Rs 15 crore at application, rising to Rs 25 crore by end of third financial year.retrieved
  23. T2Draft Master Direction on Prepaid Payment Instruments, 2026 — Draft Master Direction on Prepaid Payment Instruments, 2026 — RBI released a draft Master Direction on PPIs on 22 April 2026 to replace the 2021 PPI framework; public comments closed 22 May 2026; not yet finalised.retrieved

#

Customer-fund safeguarding for both PAs and non-bank PPI issuers rests on a mandatory escrow account held with a single scheduled commercial bank, with no co-mingling, day-end balance floors, and quarterly statutory-auditor certification. For escrow purposes the non-bank PPI issuer/PA is deemed a 'designated payment system' under the PSS Act. Conduct is supervised by RBI's DPSS; the draft PPI MD 2026 adds codified fit-and-proper criteria, multilingual disclosure and grievance-redress obligations. [CAVEAT: draft PPI Master Direction released 22 Apr 2026, comments to 22 May 2026; not yet finalised as of late Jun 2026.]

Horizon · 2026-H2 (± six months)Final RBI Master Direction on Prepaid Payment Instruments 2026Consultation · Tier 2 source
Horizon · 2026-05-01 (± a quarter)Bank/PSP penal liability for online money-gaming facilitationIn force · Tier 1 source
Standing sub-brief · as of 27 June 2026 212 words · last cycle 2026-10-11

Conduct, Safeguarding & Promotions

India's safeguarding model for non-bank PPI issuers and payment aggregators rests on a mandatory single-bank INR escrow account held with a scheduled commercial bank, with no co-mingling, a day-end balance floor not below outstanding PPIs plus acquirer dues, and quarterly statutory-auditor certification. The non-bank PPI issuer or PA is deemed a designated payment system under Section 23A(3) of the PSS Act, and the PPI issuer holds a perpetual, conditional Certificate of Authorisation. This escrow-based approach contrasts with the EU/UK segregation-plus-insurance models, carrying the bank versus non-bank distinction explicitly through the safeguarding mechanism.

Periodic update · new data 2026-10-11

Conduct, Safeguarding & Financial Promotions

The compliance deadline for cross-border card-not-present two-factor authentication arrived on 1 October 2026 under the Reserve Bank of India's Authentication Mechanisms for Digital Payment Transactions Directions, 2025. This deadline follows the earlier commencement of the domestic card-not-present 2FA requirement in April 2026, meaning that by October 2026 the additional-authentication mandate under these Directions extends across both domestic and cross-border card-not-present transaction flows involving Indian-issued cards. The finding rests on a single trade-press source and is assessed as probable rather than confirmed, since no independently corroborating primary notification was retrieved this cycle.

The structural significance of the cross-border extension is that it closes what had been a gap in authentication coverage: international e-commerce and card-not-present transactions, which are frequently a higher-risk category for fraud given the absence of physical card presentation and the greater difficulty of applying domestic authentication infrastructure across borders, now fall within the same additional-authentication requirement that already governed domestic transactions. For payment service providers and card issuers operating in India, this means authentication-related conduct obligations now apply uniformly across the card-not-present transaction population regardless of transaction origin, removing what had been a bifurcated compliance timeline between domestic and cross-border flows.

This development should be read as the completion of a phased rollout rather than as a new standalone rule: the underlying Directions were already in force from April 2026 for domestic transactions, and the cross-border deadline represents the scheduled second phase of the same instrument reaching its commencement date rather than the introduction of a materially new obligation.

Outlook

With both the domestic and cross-border phases of the Authentication Mechanisms Directions now in effect, no further phased milestones under this specific instrument are indicated in current reporting. Attention in this module going forward is likely to shift toward how consistently payment service providers and card networks implement the cross-border authentication requirement in practice, particularly given the greater technical complexity of applying strong authentication across international payment rails compared to the domestic card-not-present environment addressed from April 2026.

2 earlier distinct update(s)
Periodic update · new data 2026-09-14

Conduct, Safeguarding & Financial Promotions

This cycle's most consequential conduct-side development for the Indian payments industry is direct and confirmed at the highest source tier: banks and financial institutions that promote or facilitate financial transactions for online money gaming will be guilty of an offence, effective from 1 May 2026. This statement, made explicitly by the government, converts what had previously been an indirect exposure for the payments industry into a direct criminal-liability standard tied to a specific prohibited activity.

The Online Gaming Rules, 2026 operationalise this penal-liability announcement into a concrete transaction-blocking mechanism: a designated authority is empowered to instruct banks and payment service providers to halt transactions linked to specified games, with penalties attaching to delayed compliance. This is a confirmed, though Tier 2-sourced, development that gives the conduct obligation an enforceable operational form rather than leaving it as a general prohibition. Both banks and non-bank payment service providers fall within scope of this obligation, a rare instance where the conduct standard is deliberately drawn across the bank/non-bank line rather than differentiated by institution type.

A further, less-corroborated development concerns merchant-category-code tagging: reporting sourced only at a low evidentiary tier indicates a designated authority mandated a unique gaming merchant-category code for UPI-based gaming transactions specifically to enable real-time monitoring and deposit-limit enforcement. This remains an uncertain finding pending stronger-tier corroboration, and should be read as a plausible but unconfirmed elaboration of the broader transaction-blocking framework rather than a settled fact.

Outlook

The practical enforcement pattern under the new penal-liability regime, and specifically whether and how often the designated authority exercises its transaction-blocking power against banks or PSPs, is the central indicator to watch through the remainder of 2026. Independent corroboration of the gaming merchant-category-code mandate would also be a significant confirming development if it emerges.

Periodic update · new data 2026-09-08

Conduct, Safeguarding & Financial Promotions

The 2025 Payment Aggregator Directions impose a confirmed, high-impact conduct and safeguarding obligation on all payment aggregators operating in India: a board-approved dispute-resolution policy with clear refund timelines is now mandatory, alongside maintenance of PCI-DSS/PA-DSS data-security standards. This combines a customer-facing conduct requirement -- ensuring merchants and consumers have a defined, governed path to dispute resolution and refunds -- with a technical data-security baseline that aggregators must demonstrably maintain rather than merely aspire to.

The safeguarding mechanism specified is procedural rather than a discrete asset-segregation rule: the requirement centres on the board-approved policy itself and the underlying PCI-DSS/PA-DSS compliance posture, rather than, for example, a specific customer-funds-segregation mechanism of the kind seen in some other jurisdictions' payment-institution safeguarding regimes. Security-incident reporting is bound to this same conduct framework: aggregators must report security incidents to RBI within stipulated timeframes, including a monthly cyber-incident reporting cadence, meaning conduct obligations and operational-security obligations are woven together in the same directive rather than sitting in separate regulatory tracks.

This conduct and safeguarding tightening applies across the newly authorised online, offline and cross-border aggregator categories established by the same directions, meaning the non-bank PI/EMI population bears the primary weight of these new board-governance and data-security obligations, consistent with the directions' overall focus on non-bank aggregator oversight rather than bank-affiliated PSP conduct specifically.

Outlook

Watch for RBI supervisory guidance detailing the specific stipulated timeframes for security-incident reporting beyond the monthly cyber-incident cadence already specified, and for any published enforcement action addressing aggregators found not to have implemented a board-approved dispute-resolution policy. As the broader PA Directions rewrite beds in through 2026, conduct-related supervisory findings are likely to surface alongside the authorisation and net-worth compliance actions tracked under the licensing module.

Sources and findings (12)
  1. T1RBI Master Directions — PPI & PA conduct/safeguarding (rbi.org.in)
  2. T2https://community.nasscom.in/communities/public-policy/key-highlights-rbi-draft-master-direction-prepaid-payment-instrumentsretrieved
  3. T3https://www.lexology.com/library/detail.aspx?g=741da40c-2952-4c9b-8f94-886e57b874ec [CAVEAT: Tier 3 secondary source — Assessed; verify vs primary pre-publication]
  4. T3https://www.argus-p.com/updates/updates/rbi-issues-master-directions-on-prepaid-payment-instruments/ [CAVEAT: Tier 3 secondary source — Assessed; verify vs primary pre-publication]
  5. T1Government of India (MeitY) — Government of India (MeitY) — Banks and financial institutions promoting or facilitating financial transactions for online money gaming will be guilty of an offence, effective 1 May 2026retrieved
  6. T1Payment Aggregators (India) — Payment Aggregators (India) — PAs must implement a board-approved dispute-resolution policy with clear refund timelines, maintain PCI-DSS/PA-DSS data-security standards, and report security incidents to RBI within stipulated timeframes including monthly cyber-incident reporting.retrieved
  7. T2Online Gaming Rules, 2026 designated authority — Online Gaming Rules, 2026 designated authority — Designated authority can instruct banks/PSPs to halt transactions linked to specified games, with penalties for delayed complianceretrieved
  8. T4DGRA/OGAI — DGRA/OGAI — Mandated a unique gaming merchant-category code for UPI-based gaming transactions to enable real-time monitoring and deposit-limit enforcementretrieved
  9. T3Card Issuers (India) — Card Issuers (India) — Compliance deadline for additional-factor-authentication (AFA) on non-recurring cross-border card-not-present transactions fell on 1 October 2026; issuers must support PIN, device token, biometric or passkey authentication rather than SMS OTP aloneretrieved
  10. T3Reserve Bank of India — Reserve Bank of India — Cross-border CNP 2FA compliance deadline (1 October 2026) under the Authentication Mechanisms for Digital Payment Transactions Directions, 2025 reachedretrieved
  11. T1non-bank Payment Aggregator escrow account — non-bank Payment Aggregator escrow account — Non-bank PAs must hold merchant funds in an escrow account at a scheduled commercial bank, separate from own operating funds, with Tp+0/Tp+1 sweep and monthly RBI reconciliation reportingretrieved
  12. T3designated payment system (PSS Act s.23A(3)) — designated payment system (PSS Act s.23A(3)) — Funds held in escrow/designated payment system accounts enjoy a first and paramount charge on an operator's insolvencyretrieved

#

India's digital-money posture is CBDC-led and stablecoin-sceptical. The RBI's Digital Rupee (e₹), a tokenised CBDC and legal tender backed by RBI, launched wholesale (Nov 2022) and retail (Dec 2022) pilots and by 2026 carries ~7-8 million retail users with programmable use-cases in welfare schemes. The RBI strongly advocates prioritising CBDCs over privately issued stablecoins; there is no in-force stablecoin framework, though the Ministry of Finance's Economic Survey 2025-26 signals possible regulation, diverging from the cautious RBI stance.

Open gap — wpm-int-2Draft Master Direction on PPIs (2026) not yet made; tracked as a horizon lead, not an instrument.APP-fraud reimbursement is a known under-indexed vector for non-Anglosphere markets; flagged for deeper research next cycle.
Horizon · 2026-27 (± a year)RBI bilateral/multilateral cross-border CBDC pilotsProposed · Tier 2 source
Horizon · 2026-Q4 (± six months)Draft Master Direction on Prepaid Payment Instruments, 2026Consultation · Tier 3 source
Standing sub-brief · as of 27 June 2026 190 words · last cycle 2026-06-27

Stablecoins & Digital Money

India's digital-money posture is CBDC-led and stablecoin-sceptical. The Digital Rupee (e-Rupee) comprises wholesale e-Rupee-W, launched 1 November 2022 for G-sec settlement, and retail e-Rupee-R, launched 1 December 2022; the instrument is legal tender, bears no interest, and provides cash-like settlement finality. The retail user base is estimated at around 6-10 million by mid-2026, a range reflecting source variance and an unanchored primary count.

no periodic updates on record for this sub-brief

Sources and findings (4)
  1. T1RBI Digital Rupee (e₹) pilot — CBDC framework (rbi.org.in)
  2. T2https://www.business-standard.com/finance/news/rbi-cross-border-cbdc-pilots-digital-currency-2026-27-126052900721_1.htmlretrieved
  3. T3https://coinmarketcap.com/academy/article/india-central-bank-pushes-for-prioritizing-cbdcs-over-stablecoins [CAVEAT: Tier 3 secondary source — Assessed; verify vs primary pre-publication]
  4. T3https://www.cryptotimes.io/2026/04/15/rbi-urges-indians-to-join-cbdc-pilot-calls-e-rupee-future-of-money/ [CAVEAT: Tier 3 secondary source — Assessed; verify vs primary pre-publication]

#

Operational resilience for payments rests on the RBI Master Directions on Cyber Resilience and Digital Payment Security Controls for non-bank PSOs (July 2024), the Master Direction on IT Governance, Risk, Controls and Assurance Practices (effective 1 April 2024) and the Master Direction on Outsourcing of IT Services (10 April 2023), supplemented by 2025 Outsourcing Directions for commercial banks and NBFCs. Core obligations: board-approved cyber/IT governance, business-continuity/DR, vendor (third-party/cloud) risk management and incident reporting to RBI within six hours of detection.

Horizon · 2026-04-01 (± a quarter)RBI Authentication Mechanisms Directions 2FA/AFA mandateIn force · Tier 3 source
Standing sub-brief · as of 27 June 2026 205 words · last cycle 2026-09-14

Operational Resilience & Critical Infrastructure

India's operational-resilience regime for payments rests on a layered set of Master Directions rather than a single statute. These comprise the Master Directions on Cyber Resilience & Digital Payment Security Controls for non-bank PSOs (July 2024), the Master Direction on IT Governance, Risk, Controls & Assurance Practices (effective 1 April 2024), the Master Direction on Outsourcing of IT Services (10 April 2023), and the RBI (Commercial Banks — Managing Risks in Outsourcing) Directions 2025. Core obligations include board-approved cyber and IT governance, BCP/DR, vendor and cloud risk management, and cyber-incident reporting to RBI within six hours of detection; existing outsourcing arrangements must comply by 10 April 2026. The framework applies to both banks and non-bank PSOs.

Periodic update · new data 2026-09-14

Operational Resilience & Critical Infrastructure

The Reserve Bank of India's Authentication Mechanisms for Digital Payment Transactions Directions, 2025 mandate two-factor authentication, with at least one dynamic security element, for every digital payment transaction, including transactions on the Unified Payments Interface, effective 1 April 2026. This is a probable, system-wide resilience and fraud-control uplift that touches essentially the entire retail digital-payments ecosystem in India rather than a narrow subset of instruments or providers.

The scale at stake is considerable: UPI alone processed over 14 billion transactions per month by March 2026, meaning the new authentication standard applies across an exceptionally high transaction volume, and any friction or failure in the authentication mechanism's rollout would have an outsized practical effect on the payments system's day-to-day functioning. This throughput figure is itself a probable finding, useful primarily as scale context for the authentication mandate rather than as an independent resilience development in its own right.

No further critical-infrastructure-specific findings, such as outage-reporting requirements, resilience-testing obligations, or third-party risk-management standards for critical payment infrastructure, were located for India this cycle beyond the authentication mandate itself.

Outlook

The question to watch is whether the 2FA/AFA mandate, now in force since 1 April 2026, produces measurable fraud-reduction outcomes at UPI's scale without introducing friction significant enough to prompt a regulatory adjustment or exemption carve-out. Given UPI's transaction volume, even a modest friction effect could generate material user-experience or throughput consequences worth monitoring in subsequent cycles.

1 earlier distinct update(s)
Periodic update · new data 2026-09-08

Operational Resilience & Critical Infrastructure

The 2025 Payment Aggregator Directions formalise a confirmed operational-resilience obligation requiring payment aggregators to present reports on risk assessment, security-compliance posture, security audits and incidents to their board, and to report the same to RBI. This sits alongside the confirmed PCI-DSS/PA-DSS data-security standard and the monthly cyber-incident reporting cadence carried within the same directions, together constituting a materially strengthened operational-resilience framework for the payment-aggregator sector relative to the prior 2020 regime.

The structural significance of formalising board-level presentation of security and risk-assessment reporting is that it embeds operational-resilience accountability at governance level rather than leaving it purely as a technical-compliance function reporting only to management. Combined with the monthly cyber-incident reporting obligation to RBI, this creates a dual accountability channel -- internal board oversight and external regulatory reporting -- operating on overlapping but distinct cadences.

This resilience obligation applies to the newly authorised online, offline and cross-border aggregator categories alike, meaning the non-bank PI/EMI population that dominates the payment-aggregator sector in India now faces board-governance and regulatory-reporting obligations for operational resilience that more closely approach, though do not necessarily match, the standards historically expected of bank-affiliated payment infrastructure.

Outlook

Watch for the first cycle of monthly cyber-incident reports to RBI under the new framework, and for any RBI commentary on aggregate incident volumes or patterns across the newly regulated offline-PA population, which entered the authorisation regime for the first time this cycle. Any high-profile security incident at a payment aggregator in the coming cycles would be the first real test of whether the board-reporting and RBI-notification cadence functions as intended under the new directions.

Sources and findings (9)
  1. T3https://www.getastra.com/blog/compliance/rbi-cybersecurity-compliance-checklist/ [CAVEAT: Tier 3 secondary source — Assessed; verify vs primary pre-publication]
  2. T2https://taxguru.in/rbi/rbi-commercial-banks-managing-risks-outsourcing-directions-2025.htmlretrieved
  3. T3https://thedigitalfifth.com/decoding-rbis-master-direction-on-it-governance/ [CAVEAT: Tier 3 secondary source — Assessed; verify vs primary pre-publication]
  4. T3https://aiplexorm.com/blog/rbi-master-direction-digital-payment-security-controls [CAVEAT: Tier 3 secondary source — Assessed; verify vs primary pre-publication]
  5. T2Payment Aggregators (India) — Payment Aggregators (India) — Reports on risk assessment, security-compliance posture, security audits and incidents must be presented to the PA's Board and reported to RBI.retrieved
  6. T3RBI — Authentication Mechanisms for Digital Payment Transactions Directions, 2025 — RBI — Authentication Mechanisms for Digital Payment Transactions Directions, 2025 — Two-factor authentication (2FA/AFA) with at least one dynamic security element mandatory for every digital payment, including UPI, effective 1 April 2026
  7. T3UPI (Unified Payments Interface) — UPI (Unified Payments Interface) — UPI processed over 14 billion transactions per month by March 2026retrieved
  8. T1RBI circular on Storage of Payment System Data — RBI circular on Storage of Payment System Data — All payment system providers must store the entire data relating to payment systems operated by them only in Indiaretrieved
  9. T1regulated entity outsourcing IT services — regulated entity outsourcing IT services — Cyber incidents at an IT service provider must be reported by the RE to RBI within 6 hours of detection by the third-party service providerretrieved

#

UPI's zero-MDR status for merchants is in transition: NPCI's 0.4% MDR on P2M UPI payments above Rs2,000, enabled by a 14 Sept 2026 Gazette amendment to s.10A PSS Act 2007, was deferred from its 15 Oct 2026 go-live date to 'immediately post-Diwali' with no new date announced, following public and political pushback.

Movement — NEWMandatory two-factor authentication for digital payments effective 1 April 2026.RBI Authentication Mechanisms for Digital Payment Transactions Directions, 2025 newly surfaced this cycle as a forward-dated SCA mandate.
Key judgment — Probable · impact HIGHIndia's payments regulatory trajectory is tightening on authentication (mandatory 2FA from April 2026) and non-bank payment-aggregator capital/authorisation requirements, while consumer protection for authorised-but-deceived (APP fraud) payments remains structurally underdeveloped relative to UK-style regimes.claims: none recorded
Horizon · 2027 (± a year)Possible reintroduction of MDR on large UPI merchantsProposed · Tier 3 source
Horizon · 2027 (± a year)Possible reintroduction of MDR on large UPI merchantsProposed · Tier 3 source
Horizon · 2026-Q4 (± a quarter)UPI merchant MDR go-live, rescheduledAdopted · Tier 2 source
Horizon · 2026-04-01 (± a quarter)RBI Authentication Mechanisms for Digital Payment Transactions Directions effectiveAdopted, not yet in force · Tier 1 source
Horizon · 2026-10-15 (± a quarter)UPI MDR of 0.4% on P2M payments above Rs 2,000 takes effectAdopted, not yet in force · Tier 3 source
Standing sub-brief · as of 27 June 2026 211 words · last cycle 2026-11-04

Scheme & Network Compliance

Scheme economics in India are dominated by the zero-MDR regime. RBI caps debit-card MDR at up to 0.90% and NPCI caps UPI P2M MDR at up to 0.30%, but since January 2020 MDR is statutorily zero for RuPay debit cards and BHIM-UPI via Section 10A of the PSS Act and Section 269SU of the Income-tax Act, funded by a government incentive scheme paid to acquiring banks. Credit cards carry no regulatory MDR cap, and a roughly 1.1% interchange applies to PPI-routed UPI merchant transactions over INR2,000. The regime applies across both bank and non-bank acquirers.

Periodic update · new data 2026-11-04

Scheme & Network Compliance

The Reserve Bank of India has consolidated its rules governing recurring payments into a single instrument, the Digital Payments E-mandate Framework, 2026. The new framework repeals eight prior circulars in their entirety and replaces them with one unified code covering standing instructions executed through cards, prepaid instruments and other designated mechanisms, for both domestic and cross-border recurring transactions. Because the repealed circulars had accumulated piecemeal since the original e-mandate regime, scheme participants and payment service providers had been operating against a patchwork of overlapping notifications; the new framework is intended to resolve that fragmentation by setting out a single rulebook that applies across card networks, wallet issuers and other recurring-payment mechanisms, regardless of whether the underlying payment instrument is bank-issued or non-bank-issued.

The consolidation reaches both ends of the recurring-payment chain: issuers validating the mandate and merchants or payment aggregators initiating it. This is a structural tidying exercise rather than a new restriction, but the breadth of the repeal means every entity that previously relied on the specific wording of one of the eight superseded circulars needs to re-map its compliance position against the new, single text. The framework extends to cross-border recurring transactions as well as domestic ones, which is notable given how much recent RBI attention has gone into cross-border payment aggregation and card-not-present authentication; the e-mandate consolidation sits alongside that wider push to standardise how international recurring charges are authenticated and settled.

The immediate effect for payment system operators and card networks is procedural: the rulebook governing dispute handling, mandate registration, and notification to the payer ahead of a recurring debit sits now under one consolidated reference rather than eight. For network participants whose compliance processes were built around the specific numbering of the earlier circulars, the exercise of mapping obligations across to the new framework is itself a compliance task, even though the underlying policy intent is harmonisation rather than tightening.

1 earlier distinct update(s)
Periodic update · new data 2026-10-18

Scheme & Network Compliance

The National Payments Corporation of India introduced a merchant discount rate on person-to-merchant Unified Payments Interface transactions, departing from the long-standing zero-MDR position on UPI. The rule sets a 0.4 percent charge on transactions above Rs2,000, capped at Rs300 for transactions of Rs75,000 or more, with a flat Rs5 fee for railways, telecom, insurance and fuel payments, a reduced 0.02 percent rate for capital-market payments, and no charge for peer-to-peer transfers or for small merchants processing Rs1 lakh or less per month. Consumers remain entirely unaffected: the scheme rule applies only to the merchant side of person-to-merchant transactions.

The scheme-rule change was enabled by statute rather than scheme discretion alone: a Gazette notification of 14 September 2026 amended section 10A of the Payment and Settlement Systems Act, 2007, establishing the enabling legal framework for digital-payment processing charges on a rail that had previously operated on a mandated zero-MDR basis. This statutory-basis finding carries more caution than the scheme-rule finding itself, since it rests on a secondary explainer source rather than a directly retrieved Gazette text.

The rule was originally due to take effect on 15 October 2026. On 13 October 2026, two days before that date, the scheme deferred implementation to a point after the Diwali festival period, with no replacement date announced, following public and political pushback against the prospect of new merchant-side costs on India's dominant free payment rail. The Finance Ministry has denied that the deferral reflects pressure from the United States, a denial offered in response to speculation linking the deferral to external trade considerations. The underlying scheme rule and its enabling statutory amendment remain formally in place: this is a deferral of implementation timing, not a reversal of the rule itself.

Outlook

The operative question for scheme participants and merchants is when a revised go-live date will be announced and whether the rate structure will change in response to the pushback that triggered the deferral. A future cycle should watch specifically for a post-Diwali NPCI circular; the political sensitivity already displayed around this rule suggests any relaunch is likely to be managed carefully to avoid a second reversal.

Sources and findings (10)
  1. T1https://www.pib.gov.in/PressReleasePage.aspx?PRID=2114335&reg=3&lang=2retrieved
  2. T3https://www.medianama.com/2026/03/223-parliamentary-committee-calls-return-mdr-upi-implications-users-small-merchants/retrieved
  3. T3https://razorpay.com/learn/upi-transaction-charges/retrieved
  4. T2https://www.npci.org.in/what-we-do/rupay/circularsretrieved
  5. T2National Payments Corporation of India (NPCI) — National Payments Corporation of India (NPCI) — 0.4% MDR introduced on P2M UPI payments above Rs2,000 (capped Rs300 at Rs75,000+); flat Rs5 for railways/telecom/insurance/fuel; 0.02% for capital-market payments; nil for P2P and small merchants (<=Rs1 lakh/month)retrieved
  6. T4Ministry of Finance (India) — Ministry of Finance (India) — Gazette notification (14 Sept 2026) amended s.10A of the Payment and Settlement Systems Act, 2007, creating the enabling statutory framework for UPI processing chargesretrieved
  7. T2UPI and Services Steering Committee (NPCI) — UPI and Services Steering Committee (NPCI) — MDR implementation deferred from 15 Oct 2026 'until after Diwali', no new date set, following public and political pushback; Finance Ministry denies US pressureretrieved
  8. T1Authentication Mechanisms for Digital Payment Transactions Directions, 2025 — Authentication Mechanisms for Digital Payment Transactions Directions, 2025 — All digital payment transactions must be authenticated using at least two distinct independent factors, effective 1 April 2026, for all Payment System Providers and Participants.retrieved
  9. T3UPI person-to-merchant payments — UPI person-to-merchant payments — 0.4% MDR capped at Rs 300 applies to UPI P2M payments above Rs 2,000 to organised retailers from 15 October 2026; payments up to Rs 2,000 and RuPay debit remain charge-freeretrieved
  10. T1debit card transactions — debit card transactions — RBI caps debit card MDR up to 0.90% across card networks for physical PoS and QR-code acceptanceretrieved

#

NPCI/RBI's UPI Merchant Discount Rate reform introduces a 0.4% MDR on eligible UPI merchant transactions above ₹2,000, effective 15 October 2026.

Horizon · 2026-10-15 (± a quarter)UPI MDR reintroduction on eligible merchant transactionsAdopted · Tier 3 source
Horizon · 2026-04-01 (± a quarter)Cross-border CNP authentication-factor validation effectiveAdopted, not yet in force · Tier 2 source
Standing sub-brief · as of 27 June 2026 189 words · last cycle 2026-11-04

Payment Corridor Dynamics

India's corridor strategy is UPI-led and run through NPCI International (NIPL) in concert with RBI. The UPI-PayNow linkage with the Monetary Authority of Singapore, launched February 2025, is the world's first cloud-based real-time cross-border remittance corridor — a bilateral India-Singapore arrangement now expanded to 19 participating Indian banks. Daily caps run at SGD1,000 / INR60,000, governed by FEMA under the LRS USD250,000/year limit.

Periodic update · new data 2026-11-04

Payment Corridor Dynamics

The planned introduction of a merchant discount rate on high-value Unified Payments Interface transactions has been deferred following a legal challenge. The National Payments Corporation of India had set 15 October 2026 as the effective date for a 0.4% merchant discount rate, capped at ₹300, on person-to-merchant UPI payments above ₹2,000 routed to organised retailers. That rollout has now been pushed back to an unannounced date after the Diwali 2026 period.

The deferral followed a hearing before the Supreme Court of India on 29 September 2026, at which the court declined to stay the fee framework outright but directed the Centre, the Reserve Bank of India and the National Payments Corporation of India to justify its legal basis within four weeks. The court's refusal to stay the measure, combined with its demand for a justification of the statutory footing on which a merchant fee is being imposed on a payment rail that has operated on a zero-MDR basis since the government's 2020 amendment to the Payment and Settlement Systems Act, leaves the framework in an unresolved position: live in principle, deferred in practice, and now under direct judicial scrutiny as to whether NPCI has the authority to impose such a charge without clearer statutory backing.

The practical effect for the payments industry is that organised retailers and the acquiring banks and payment aggregators that serve them continue to operate under the existing zero-cost UPI model for now, with no confirmed date for when — or whether — the fee will take effect. Any forward planning around merchant pricing, acquirer economics or the splitting of interchange-equivalent revenue on large-ticket UPI transactions is necessarily provisional until the court receives and rules on the government's and regulators' justification, and until a revised implementation date is announced. The episode is also a reminder that UPI's zero-MDR status, long treated as a fixed feature of the rail since the 2020 statutory amendment, is being tested for the first time at the point where transaction value and merchant category create a plausible case for a fee, and that any change to that status needs more than a notice from the network operator to survive legal challenge.

1 earlier distinct update(s)
Periodic update · new data 2026-09-22

Payment Corridor Dynamics

NPCI and the RBI are reintroducing a Merchant Discount Rate on the Unified Payments Interface rail. A 0.4% MDR will apply to eligible UPI merchant transactions above ₹2,000, effective 15 October 2026. This is probably the most structurally significant single development in India's domestic payment-corridor economics this cycle: UPI has operated as a zero-MDR rail for small transactions since 2020, as part of a deliberate government policy of promoting digital-payments adoption by keeping merchant acceptance costs at zero. The reintroduction of even a modest 0.4% rate marks the first material departure from that decade-long zero-MDR posture.

The practical effect falls on merchant acquirers and the broader UPI merchant-acceptance ecosystem, which must now build MDR collection and reconciliation into transaction processing for eligible transactions above the ₹2,000 threshold, where previously no such mechanism was required for the affected transaction band. The structural significance is less about the rate itself, which is modest by card-scheme standards, than about what it signals for the commercial economics of India's flagship instant-payment rail going forward: a shift away from an absolute zero-cost-to-merchant model toward one in which at least some transaction volume now carries an explicit cost.

Outlook

The 15 October 2026 effective date is the concrete marker to track. Whether this modest reintroduction is a one-off adjustment or the beginning of a broader recalibration of UPI's commercial-economics model is the open question that will likely become clearer only after the new MDR has been in effect for a full reporting cycle.

Sources and findings (9)
  1. T2https://ibsintelligence.com/ibsi-news/npci-adds-13-banks-to-upi-paynow-for-faster-cross-border-payments/retrieved
  2. T3https://corporate.cyrilamarchandblogs.com/2026/05/upi-goes-global-the-regulatory-reckoning-ahead/retrieved
  3. T3https://thepaymentsassociation.org/article/cross-border-payments-and-upi-revolution-in-india/retrieved
  4. T3https://www.policycircle.org/industry/upi-global-expansion-cross-border/retrieved
  5. T3NPCI / RBI — NPCI / RBI — 0.4% Merchant Discount Rate on eligible UPI merchant transactions above ₹2,000, effective 15 October 2026.retrieved
  6. T1UPI — UPI live for acceptance/remittance in 11 foreign countries including Bhutan, Nepal, Singapore, UAE, France, Sri Lanka, Mauritius, Qatar, Cambodia, Greece, Maldivesretrieved
  7. T3Liberalised Remittance Scheme — Liberalised Remittance Scheme — Resident individuals may remit up to USD 250,000 per financial year abroad without case-by-case RBI approvalretrieved
  8. T3Payment Aggregator - Cross Border (PA-CB) — Payment Aggregator - Cross Border (PA-CB) — PA-CBs are capped at INR 25,00,000 (~USD 28,000) per inward/outward e-commerce transaction, with mandatory CDD on directly onboarded merchants and separate Import/Export Collection Accountsretrieved
  9. T2card issuer — Card issuers must validate the additional factor of authentication on non-recurring cross-border CNP transactions when requested by the overseas merchant or acquirerretrieved

#

The retail-payments market is UPI-dominated (~86% of digital transaction volume, 23bn+ payments/month worth ~₹30 lakh crore) and structurally concentrated in a PhonePe/Google Pay duopoly, whose combined share fell below 80% for the first time in May 2026 (PhonePe 46.2%, Google Pay 32.7%). NPCI's proposed 30% per-app volume cap (deadline December 2026) remains far from achievable; challengers Navi, Flipkart's super.money, BHIM and WhatsApp Pay are gaining share, and Amazon/Meta are lobbying NPCI over dominance.

Horizon · 2026-12-31 (± a quarter)NPCI 30% per-app UPI volume capProposed · Tier 3 source
Horizon · 2026-10-15 (± a quarter)UPI P2M MDR reportedly introducedProposed · Tier 4 source
Standing sub-brief · as of 27 June 2026 187 words · last cycle 2026-06-27

Industry Structure & Commercial Dynamics

The Indian payments market is structurally concentrated but eroding at the top. UPI handles around 86% of India's digital transaction volume — over 23 billion payments per month, around INR30 lakh crore. PhonePe (46.2%) and Google Pay (32.7%) combined fell to around 79% in May 2026, the first time below 80%. Challengers are gaining: Navi (from 0.21% to 3.6%), Flipkart's super.money (1.8%), BHIM and WhatsApp Pay. NPCI's proposed 30% per-app volume cap has been deferred to 31 December 2026, and Amazon and Meta have joined lobbying over duopoly dominance. UPI-enabled banks grew to 685 by December 2025. This module sits on the non-bank PI/EMI side of the market structure, with per-app share data derived from Tier-3 NPCI-sourced journalism, held at Assessed confidence.

no periodic updates on record for this sub-brief

Sources and findings (5)
  1. T3https://www.outlookbusiness.com/economy-and-policy/phonepe-google-pay-combined-upi-market-share-drops-below-80-for-first-timeretrieved
  2. T3https://www.niftytrader.in/markets/phonepe-google-pay-share-falls/retrieved
  3. T3https://techcrunch.com/2026/04/29/amazon-meta-join-fight-to-end-google-pay-phonepe-dominance-in-india/retrieved
  4. T3https://www.oxigenwallet.com/upi/apps-market-share/retrieved
  5. T4UPI/RuPay MDR notification (Sept 2026) — UPI/RuPay MDR notification (Sept 2026) — A 0.4% MDR on UPI P2M payments above Rs 2,000 was introduced from 15 October 2026, following removal of the automatic s.269SU exemption from MDR.

Payments enforcement is active. The RBI imposed monetary penalties on 353 entities totalling ₹54.78cr in FY 2024-25 for compliance failures, with PSO-specific actions under Sections 30/31 PSS Act for KYC/PPI lapses (e.g. Appnit Technologies, May 2026). A landmark RBI Ombudsman order in 2026 shifted liability onto banks whose receiving-side KYC/AML systems failed, departing from the prior 'contributory negligence' defence. The PayPal/OPGSP case established broad construction of 'payment system' under PMLA.

Standing sub-brief · as of 27 June 2026 169 words · last cycle 2026-06-27

Legal & Litigation

RBI runs an active payments-enforcement posture. It imposed monetary penalties on 353 entities totalling INR54.78cr in FY2024-25, and on 15 May 2026 penalised Appnit Technologies INR5.8 lakh for KYC/PPI non-compliance under Sections 30/31 of the PSS Act. The pivotal legal development is a 2026 RBI Ombudsman order that shifted liability onto banks whose receiving-side KYC, AML, transaction-monitoring and STR systems failed, departing from the prior contributory-negligence OTP-disclosure defence. Separately, a court held that 'payment system' under PMLA must be broadly construed to include OPGSPs, in the PayPal/Abhijit Mishra case. The enforcement reach spans both bank and non-bank entities.

no periodic updates on record for this sub-brief

Sources and findings (6)
  1. T3https://www.bhavyasharmaandassociates.com/rbi-ppi-kyc-penalty-fintech-founder-checklist-2026/retrieved
  2. T3https://www.multibagg.ai/market-pulse/articles/rbi-digital-fraud-compensation-rules-cmnbhiarudsmcpa0jlgnczxa7retrieved
  3. T3https://clatgurukul.com/rbi-ombudsman-digital-arrest-malhotra-22-crore-kyc-clat-2027/retrieved
  4. T3https://www.taxtmi.com/article/detailed?id=13006retrieved
  5. T4Payment and Settlement Systems Act, 2007 s.26(1) — Payment and Settlement Systems Act, 2007 s.26(1) — Operating a payment system without authorisation, or breaching authorisation conditions, is punishable by 1 month to 10 years imprisonment and/or a fine up to Rs 1 crore, plus Rs 1 lakh per day of continuing contraventionretrieved
  6. T2Mastercard Asia Pacific — Mastercard Asia Pacific — RBI barred Mastercard from onboarding new domestic card customers for non-compliance with the data-storage circularretrieved

#

Acquiring is governed by the PA Directions (escrow settlement, merchant KYC/onboarding by the PA) and card-scheme rulebooks (Visa/Mastercard/RuPay) for the chargeback/dispute cycle. RBI mandates an Online Dispute Resolution (ODR) system for digital payments (DPSS circular 2020-21/21) and card-on-file tokenisation/eMandate rules for recurring transactions. Card chargebacks follow a 45-120 day network-driven cycle with issuer temporary credit; UPI disputes use a separate NPCI 3-day mechanism, with escalation to the RBI Integrated Ombudsman.

Standing sub-brief · as of 27 June 2026 174 words · last cycle 2026-06-27

Merchant Acquiring & Risk

Merchant acquiring in India is governed by the PA Directions — escrow settlement, merchant KYC and onboarding — together with the card-scheme rulebooks of Visa, Mastercard and RuPay for the chargeback cycle. RBI mandates an Online Dispute Resolution (ODR) system under DPSS.CO.PD No.116/02.12.004/2020-21, plus card-on-file tokenisation and eMandate rules for recurring transactions. The dispute architecture diverges by rail: card chargebacks follow a 45-120 day network cycle with issuer temporary credit, while UPI disputes use a separate NPCI 3-day mechanism, escalating to the RBI Integrated Ombudsman Scheme 2021. Both bank and non-bank acquirers are in scope.

no periodic updates on record for this sub-brief

Sources and findings (5)
  1. T1https://www.rbi.org.in/commonperson/English/Scripts/Notification.aspx?Id=3194retrieved
  2. T3https://in.nttdatapay.com/en/company/corporate-governance/grievance-redressal-policyretrieved
  3. T3https://merchantriskcouncil.org/advocacy/reserve-bank-of-india-rbiretrieved
  4. T4https://righttoinformation.wiki/credit-card-chargeback-guide-india [CAVEAT: Tier 4 source — Assessed; illustrative only, verify pre-publication]
  5. T1regulated entity (payment system participant) — regulated entity (payment system participant) — CDD required at account-based relationship commencement or for an occasional transaction (single or connected) of Rs 50,000 or more, or any international money transferretrieved

#

India is a global front-runner in rail and product innovation: UPI (real-time rails), UPI 123Pay/UPI Lite (feature-phone and offline low-value), the e₹ CBDC pilots with programmability and offline NFC, and an active RBI regulatory sandbox plus the CBDC and Asset Tokenisation Sandbox. Open-banking-style account aggregation and agentic/AI-powered conversational payments (Razorpay-NPCI-OpenAI) are emerging build-outs; RuPay-credit-card-on-UPI is a key product driving challenger growth.

Horizon · 2026-Q4 (± six months)RBI cross-border CBDC pilots expectedProposed · Tier 3 source
Horizon · 2026-10-15 (± a quarter)UPI P2M MDR framework in forceAdopted, not yet in force · Tier 3 source
Horizon · 2026-10-15 (± a quarter)UPI 0.4% MDR on merchant payments above ₹2,000In force · Tier 3 source
Standing sub-brief · as of 27 June 2026 170 words · last cycle 2026-10-11

Product Innovation & Market Development

India's product-innovation frontier layers new commerce and access patterns on top of UPI rails. The thematic build-out spans UPI 123Pay and UPI Lite, offline NFC CBDC, the CBDC & Asset Tokenisation Sandbox, and the Unified Markets Interface (UMI). The emerging product frontier includes agentic and conversational payments: a Razorpay-NPCI-OpenAI tie-up enabling ChatGPT users in India to find products and instantly purchase them with UPI illustrates AI-driven product build-out around real-time rails. This thematic product-access view is distinct from discrete commercial events; the specific Razorpay-NPCI-OpenAI launch is rendered as a W13 commercial event, while the structural UPI product-rail innovation theme sits here in the W9 standing position. The module reflects non-bank PI/EMI product activity built on state rails.

Periodic update · new data 2026-10-11

Product Innovation & Market Development

A merchant discount rate of 0.4 percent has reportedly been introduced on select UPI merchant payments above two thousand rupees, effective from 15 October 2026. This is reported as the first merchant discount rate applied to UPI merchant transactions since the scheme's zero-MDR mandate was established, a policy that has underpinned UPI's merchant-acceptance growth strategy since its inception. The finding rests on a single trade source and is assessed as uncertain, reflecting both the limited sourcing and the significance of a departure from a long-standing zero-MDR commercial model.

If accurate, the introduction of even a selective, threshold-based MDR represents a notable shift in the commercial economics underlying India's dominant instant-payment scheme. UPI's acceptance growth has historically been attributed in part to the absence of merchant-side transaction fees, which lowered the cost of acceptance relative to card-based payment methods and supported rapid merchant onboarding across small and micro-merchant segments. A reported 0.4 percent rate applying only above a two-thousand-rupee threshold would be a targeted rather than blanket change, potentially aimed at larger-ticket transactions where the cost-benefit calculation for scheme participants differs from the high-volume, low-value transaction profile that has characterised UPI's merchant base to date.

The uncertain confidence rating attached to this finding reflects the absence of independent corroboration; a change of this commercial significance to India's flagship instant-payment scheme would ordinarily be expected to generate broader reporting, and the gap between the reported change and available corroborating sourcing warrants caution before treating the development as established fact.

Outlook

Should the reported UPI merchant discount rate be corroborated by additional sourcing or confirmed through scheme documentation, it would mark a material inflection point in UPI's commercial model and would warrant close tracking of any downstream effects on merchant acceptance behaviour, particularly among merchants processing transactions near or above the reported two-thousand-rupee threshold. Absent further corroboration, this development should continue to be treated with caution in subsequent reporting periods.

2 earlier distinct update(s)
Periodic update · new data 2026-09-28

Product Innovation & Market Development

The Reserve Bank of India's FY2025-26 Annual Report signals a deliberate expansion of its central bank digital currency programme. The Report states RBI will explore bilateral and multilateral cross-border CBDC pilots during FY2026-27, extending the e-Rupee programme beyond its current domestic pilot footprint into cross-border settlement use cases. Domestically, the Report also signals a widening of existing CBDC pilots into direct-benefit-transfer and business-application use cases, broadening the programme's functional scope beyond its initial retail and wholesale pilot design.

Separately, and on thinner sourcing, RBI is reported to have launched a deposit-tokenisation pilot around October 2025 using its Unified Markets Interface, applying blockchain-based settlement to tokenised Certificates of Deposit. This pilot, if confirmed by further reporting, would represent a distinct product-innovation track from the e-Rupee CBDC programme, applying distributed-ledger settlement mechanics to an existing wholesale-market instrument rather than to a sovereign digital currency. Both developments sit within the bank/PSP side of India's payments infrastructure, reflecting RBI's own central-bank-led experimentation rather than non-bank product innovation.

Outlook

Watch for RBI's FY2026-27 activity on cross-border CBDC pilots as the most concrete near-term marker of this programme's direction, and for any further confirmation or expansion of the deposit-tokenisation pilot beyond its October 2025 launch, which currently rests on a single lower-tier source.

Periodic update · new data 2026-09-22

Product Innovation & Market Development

The Reserve Bank of India's 2025-26 Annual Report commits to a substantial expansion of e-rupee central-bank-digital-currency experimentation during 2026-27. The programme spans cross-border bilateral and multilateral CBDC pilots, asset tokenisation experimentation via the Unified Multi-Ledger Infrastructure, programmable-money direct-benefit-transfer pilots running in Gujarat, Puducherry and Chandigarh, and a digital-assets cooperation pact with the Monetary Authority of Singapore. This is a confirmed institutional commitment rather than a speculative proposal, reflecting the RBI's stated annual-report-level prioritisation of CBDC development.

The breadth of this programme — spanning cross-border settlement, asset tokenisation, and domestic social-transfer programmability — signals that the RBI regards the e-rupee as its primary vehicle for digital-money innovation, in preference to accommodating private stablecoin issuance. The digital-assets pact with Singapore's Monetary Authority is notable as an early instance of India pursuing bilateral digital-currency cooperation with another major Asian financial centre, extending the CBDC programme's ambition beyond purely domestic use cases.

Outlook

The pace and results of the Gujarat, Puducherry and Chandigarh programmable-money pilots, and the concrete shape the MAS cooperation pact takes in practice, are the two most consequential near-term markers for assessing whether this expanded CBDC programme translates into deployed product rather than continued pilot-stage experimentation.

Sources and findings (12)
  1. T2https://www.business-standard.com/finance/news/rbi-cross-border-cbdc-pilots-digital-currency-2026-27-126052900721_1.htmlretrieved
  2. T3https://en.wikipedia.org/wiki/Digital_rupeeretrieved
  3. T3https://www.pymnts.com/news/ipo/2026/indian-payment-fintech-razorplay-planning-600-million-ipo/retrieved
  4. T3https://razorpay.com/learn/upi-transaction-charges/retrieved
  5. T3NPCI / Ministry of Finance — NPCI / Ministry of Finance — 0.4% Merchant Discount Rate (capped at Rs300) on Person-to-Merchant UPI payments above Rs2,000, effective 15 October 2026; flat Rs5 MDR for thin-margin sectors (railways, telecom, insurance, fuel, agri-inputs); no-surcharge rule bars pass-through to consumersretrieved
  6. T3Reserve Bank of India — Reserve Bank of India — RBI's 2025-26 Annual Report commits to expanding e-rupee CBDC experimentation in 2026-27: cross-border bilateral/multilateral pilots, UMI asset tokenisation, DBT programmable-money pilots (Gujarat, Puducherry, Chandigarh), and a digital-assets pact with MAS.retrieved
  7. T3RBI e-Rupee (CBDC) programme — RBI e-Rupee (CBDC) programme — RBI's FY2025-26 Annual Report states it will explore bilateral and multilateral cross-border CBDC pilots in 2026-27 and widen domestic CBDC pilots into DBT and business-application use-cases.retrieved
  8. T4RBI Unified Markets Interface deposit-tokenisation pilot — RBI Unified Markets Interface deposit-tokenisation pilot — RBI launched a deposit-tokenisation pilot (blockchain-based settlement, tokenised Certificates of Deposit via UMI) around October 2025.retrieved
  9. T3UPI — 0.4% MDR applies to select UPI merchant payments above ₹2,000, effective 15 October 2026retrieved
  10. T3NBFC-Account Aggregator — NBFC-Account Aggregator — An NBFC-AA may not store financial information it accesses, nor access or store customer authentication credentials; sharing occurs only upon valid consent artefactretrieved
  11. T3RBI Regulatory Sandbox — RBI Regulatory Sandbox — Initial coin offerings and cryptocurrencies are expressly excluded from RBI sandbox cohort themesretrieved
  12. T1Digital Rupee (e-Rupee) — Digital Rupee (e-Rupee) — Wholesale e-Rupee pilot launched 1 November 2022 and retail pilot launched 1 December 2022; no nationwide rollout date set as of 1 October 2026retrieved

#

RBI's digital fraud-compensation framework (2026) requires zero-liability compensation for unauthorised digital transactions, provisional-credit issuance within prescribed timelines, and quarterly aggregate fraud-compensation reporting to RBI's Department of Payment and Settlement Systems.

Open gap — wpm-int-1No dedicated APP-fraud reimbursement scheme for payments found for India; coverage thin on payment-specific financial promotions and private civil-litigation rules.Resilience analysis under-indexes on third-party/cloud concentration risk absent a CTP designation lens.
Horizon · 2026-07-01 (± a quarter)RBI Draft Third Amendment Directions 2026 — APP-fraud compensation schemeConsultation · Tier 3 source
Horizon · 2027-Q1 (± six months)Draft RBI KYC Amendment Directions - mule account holdConsultation · Tier 3 source
Horizon · 2026-07-01 (± a quarter)Integrated Ombudsman Scheme 2026 replaces 2021 schemeAdopted, not yet in force · Tier 3 source
Standing sub-brief · as of 27 June 2026 209 words · last cycle 2026-10-11

Consumer Protection & APP Fraud

India's APP-fraud compensation framework is moving toward an imminent effective date. Draft Third Amendment Directions 2026 (Responsible Business Conduct), proposed 6 March 2026 and effective 1 July 2026, provide that a customer suffering genuine fraud loss up to INR50,000 may receive 85% of net loss or up to INR25,000, whichever is lower, once per lifetime, for transactions on or after 1 July 2026 at commercial banks — excluding small finance banks, payments banks, RRBs and local area banks — reported within five days. RBI bears around 65% of cost, with the remainder split between sending and receiving banks. The scheme applies on the bank-PSP side.

Periodic update · new data 2026-10-11

Consumer Protection & APP Fraud

The Reserve Bank of India has published draft Know Your Customer Amendment Directions, 2026, proposing a mule-account debit-hold mechanism as a consumer-protection and fraud-control measure. Under the draft, banks would be permitted to place a temporary debit hold of up to sixty days on transactions of one thousand rupees or more that are flagged by AI-based transaction monitoring systems as linked to suspected mule-account or cyber-fraud activity. The hold would be amount-limited, restricting only the disputed sum rather than the account as a whole, except in exceptional circumstances not further specified in the draft as currently reported. The proposal was published 8 October 2026 and remains at consultation stage, with an expected effective date in the first quarter of 2027; this finding is assessed as probable, resting on a single trade-press source.

From a consumer-protection and authorised-push-payment-fraud perspective, the proposed mechanism addresses a recognised gap: current bank-level practice for handling suspected mule-account funds reportedly varies significantly across institutions, creating inconsistency in how quickly and how comprehensively fraud-linked transactions are intercepted. A standardised, amount-limited hold mechanism tied to a quantified monetary threshold and a capped maximum duration would give consumers a more predictable and nationally consistent experience when their transactions are flagged, while the amount-limited design is intended to avoid the disproportionate consumer impact of a full account freeze in response to a single flagged transaction.

The design balances fraud-prevention objectives against consumer-protection concerns: a full account freeze in response to an automated flag risks denying a legitimate account holder access to unrelated funds, whereas restricting the hold to the disputed amount limits collateral impact while still preserving the funds at issue pending investigation. The draft's reliance on AI-based flagging as the triggering mechanism also raises an implicit question, not resolved in current reporting, about the error-rate tolerance built into the system and what recourse is available to account holders whose transactions are flagged in error.

Outlook

As a consultation-stage instrument, the draft KYC Amendment Directions remain subject to revision, and the first-quarter-2027 expected effective date should be treated as scheduled rather than settled. Key open questions for the consumer-protection reading of this development include the specificity of the appeals or reversal process available to account holders whose transactions are held in error, and whether the sixty-day maximum hold period will be retained in the finalised rule. Continued tracking through the consultation period will be needed to assess whether the mechanism, once finalised, achieves its stated fraud-prevention purpose without generating disproportionate consumer friction.

3 earlier distinct update(s)
Periodic update · new data 2026-09-28

Consumer Protection & APP Fraud

India's digital-fraud compensation framework now places the burden of proving customer negligence on banks and payment service providers rather than on the customer. Under this framework, customers who report unauthorised digital transactions promptly and are not shown to have been negligent are entitled to zero-liability compensation, reversing what would otherwise be a burden-of-proof default falling on the consumer to demonstrate they were not at fault. Banks and PSPs are additionally required to submit quarterly aggregate reporting to RBI on these compensation outcomes, creating a supervisory data trail on how frequently unauthorised-transaction claims arise and how they are resolved.

This burden-shift is a significant consumer-protection development for a market where digital-payment fraud volumes are substantial, and it applies specifically to the bank/PSP side of the payments ecosystem rather than to non-bank payment institutions, reinforcing the bank-versus-non-bank distinction that runs through this cycle's other India developments.

Outlook

Watch for the first quarterly aggregate reporting cycles under this framework, which should begin to reveal the practical scale of zero-liability compensation claims and the extent to which banks are successfully or unsuccessfully proving customer negligence under the new burden-of-proof standard.

Periodic update · new data 2026-09-22

Consumer Protection & APP Fraud

The Reserve Bank of India has issued draft amendment directions reviewing the 2017 customer-liability-limitation framework that governs how losses from unauthorised electronic-banking transactions are allocated between customers and institutions. The review is a direct response to a shift in the dominant fraud typology: where the 2017 framework was designed primarily around system-level vulnerabilities and unauthorised access, the current fraud environment is increasingly driven by social-engineering techniques that induce customers to authorise payments themselves — authorised-push-payment fraud, in the terminology used elsewhere in this monitor's coverage.

This is a probable rather than confirmed development in terms of its eventual final shape, since the directions remain in draft form, but the direction of travel — toward a liability framework better calibrated to social-engineering-driven fraud rather than purely system-vulnerability-driven fraud — is a clear signal about where Indian consumer-protection policy in payments is heading.

Outlook

Whether the draft amendment directions are finalised, and in what form the revised customer-liability allocation ultimately lands, is the key marker to track. The shift in underlying fraud typology that is driving this review is itself a durable structural trend rather than a one-off anomaly, suggesting further consumer-protection policy attention in this area is likely regardless of the specific final shape these directions take.

Periodic update · new data 2026-09-08

Consumer Protection & APP Fraud

The Reserve Bank of India's digital-fraud compensation framework, assessed at probable confidence from a lower-tier source this cycle, requires zero-liability compensation for unauthorised digital transactions where the customer reports promptly and was not negligent. Critically, the burden of proving negligence rests with the bank rather than the customer, a material consumer-protection tightening that shifts the evidentiary burden away from the party with less visibility into the transaction's authentication chain.

The operational mechanics attached to this framework require banks to issue provisional credit to affected customers within prescribed timelines, ensuring consumers are not left without access to disputed funds while a fraud investigation proceeds, and to report aggregate fraud-compensation data to RBI on a quarterly basis. This quarterly reporting obligation gives RBI a standing data feed on the scale of digital-fraud compensation across the banking sector, which could in later cycles support more granular supervisory or policy responses to APP-fraud trends.

This framework applies specifically to the bank/PSP population handling digital transactions, distinct from the non-bank PI/EMI-focused obligations formalised in the same cycle's payment aggregator directions, reflecting the different points in the payment chain at which liability and compensation obligations naturally attach. The lower source-tier basis for this framework's specifics -- relative to the payment aggregator directions material sourced more directly to RBI's own circular index -- means the precise operational parameters merit confirmation against RBI's own published framework text in a future cycle.

Outlook

Watch for the first quarterly aggregate fraud-compensation reports banks submit to RBI under this framework, which would provide the first empirical measure of the scheme's practical scale and effectiveness. Given the probable-confidence, lower-tier sourcing basis for this cycle's finding, a direct RBI primary-source retrieval in a subsequent cycle would materially strengthen confidence in the framework's exact operational parameters.

Sources and findings (10)
  1. T3https://www.angelone.in/news/economy/rbi-proposes-new-rules-effective-july-1-2026-safeguards-against-digital-banking-fraudretrieved
  2. T3https://theprint.in/opinion/rbi-compensate-app-fraud-victims/2904306/retrieved
  3. T3https://chahalacademy.com/indian-express-editorial-analysis/16-feb-2026/2553retrieved
  4. T3https://abclive.in/2026/03/10/rbi-digital-fraud-liability-rules/retrieved
  5. T3Reserve Bank of India — Reserve Bank of India — Draft KYC Amendment Directions 2026 propose a 60-day debit hold on transactions ≥₹1,000 flagged as suspected mule-account activity, restricting only the disputed amountretrieved
  6. T4Reserve Bank of India — Reserve Bank of India — RBI's digital-fraud compensation framework requires zero-liability compensation for unauthorised digital transactions where the customer reports promptly and was not negligent, with the bank bearing the burden of proving negligence.retrieved
  7. T4Banks (India) — Banks (India) — Banks must issue provisional credit within prescribed timelines and report aggregate fraud-compensation data to RBI quarterly.retrieved
  8. T3RBI digital-fraud compensation framework — RBI digital-fraud compensation framework — Banks/PSPs must compensate customers on a zero-liability basis for unauthorised digital transactions where the customer reported promptly and was not negligent, with the burden of proving negligence placed on the bank; quarterly aggregate reporting to RBI required.retrieved
  9. T1RBI zero-liability circular, RBI/2017-18/15 — RBI zero-liability circular, RBI/2017-18/15 — A customer has zero liability for an unauthorised electronic banking transaction arising from bank fault or third-party breach, provided notification within 3 working days.retrieved
  10. T3Authorised push-payment fraud reimbursement regime — Authorised push-payment fraud reimbursement regime — India has no dedicated mandatory reimbursement scheme for APP fraud comparable to the UK PSR regime; the 2017 zero-liability circular addresses only unauthorised transactions, not deceived-customer authorised payments.retrieved

#

[Sentinel.gi position] India's payments AML/CFT posture is anchored on the PMLA 2002 and UAPA, supervised by RBI/FIU-IND. The FATF 2024 Mutual Evaluation placed India in 'regular follow-up' (the highest category, alongside few G20 peers), rating it compliant/largely compliant on 37 of 40 Recommendations, but flagged only 'moderate' effectiveness in AML/CFT supervision (IO.3) and that monetary penalties on FIs are generally not proportionate or dissuasive. Cross-border UPI corridors create FEMA/FATF-list interaction risk.

Standing sub-brief · as of 27 June 2026 177 words · last cycle 2026-06-27

AML/CFT & Financial Crime

This module is carried from the Sentinel.gi feed; no original illicit-finance analysis is performed here. Per the FATF September 2024 Mutual Evaluation Report, India rated compliant or largely compliant on 37 of 40 Recommendations — partial on R.8 (NPOs), R.12 (PEPs) and R.28 (DNFBP supervision) — with 'substantial' effectiveness in six areas but only 'moderate' on AML/CFT supervision (IO.3). FATF found monetary penalties on financial institutions generally not proportionate or dissuasive. India was placed in 'regular follow-up', the highest category, alongside the UK, France and Italy among G20 members. FIU-IND fined a VDA service provider USD2.16m (INR18.2cr) in June 2024 for STR-monitoring failures, and a payments bank was fined and wound down for AML/CFT violations. The intelligence is attributed to the Sentinel feed; see Sentinel.gi for the underlying analysis.

no periodic updates on record for this sub-brief

Sources and findings (11)
  1. T3https://risk.lexisnexis.com/insights-resources/article/fatf-new-findings-aml-cft-compliance-indiaretrieved
  2. T?FIM (sentinel.gi) per-JID baseline profile — India — India's AML/CFT regime rests on the Prevention of Money Laundering Act 2002 (PMLA) and the Unlawful Activities (Prevention) Act 1967, supervised by FIU-IND, RBI, SEBI and the Enforcement Directorate. FATF's 2024 MER found strong technical compliance and good results on risk understanding, asset deprivation and international cooperation, but flagged prosecution delays, thin DNFBP supervision and an early-stage VASP regime.
  3. T?FIM (sentinel.gi) gaps_register_cumulative (issue FIM-BASE-GAP-005) — Gap: sourcing-thinness
  4. T2FIM (sentinel.gi) enforcement_action_register (issue FIM-BASE-ENF-002) — Enforcement: US DOJ / SEC / OFAC — Gautam Adani, Sagar Adani, Adani Green Energy CEO Vneet Jaain, Adani Group
  5. T1FIM (sentinel.gi) sanctions_change_register (issue FIM-BASE-SANC-004) — Sanctions: EU listing
  6. T2FIM (sentinel.gi) sanctions_change_register (issue FIM-BASE-SANC-003) — Sanctions: national wind-down
  7. T2FIM (sentinel.gi) enforcement_action_register (issue FIM-BASE-ENF-001) — Enforcement: Indian Coast Guard — Three tankers suspected of dark-fleet oil smuggling off Mumbai
  8. T?FIM (sentinel.gi) gaps_register_cumulative (issue FIM-BASE-GAP-004) — Gap: regulatory-failure
  9. T?FIM (sentinel.gi) gaps_register_cumulative (issue FIM-BASE-GAP-002) — Gap: enforcement-absence
  10. T3FIM (sentinel.gi) enforcement_action_register — Enforcement action
  11. T1Prevention of Money Laundering Act, 2002 — Prevention of Money Laundering Act, 2002 — PMLA, in force since 1 July 2005, applies to all Reporting Entities including payment system participants, with CDD/record-keeping/STR obligations.retrieved

#

Central settlement runs on RBI-owned Centralised Payment Systems — RTGS (large-value, real-time, 24x7x365 since Dec 2020) and NEFT (batch, 24x7 since Dec 2019), both on the e-Kuber core banking system. Since July 2021 the RBI has opened CPS direct membership to authorised non-bank PSPs (PPI issuers, card networks, white-label ATM operators) requiring ₹25cr net worth, Indian incorporation, data-localisation and an RBI current account/IFSC; non-banks are excluded from intra-day liquidity and cannot sponsor sub-members.

Standing sub-brief · as of 27 June 2026 188 words · last cycle 2026-06-27

Correspondent Banking, Settlement & Access

The analytical spine of this module is the bank versus non-bank settlement-access asymmetry. Central settlement runs on RBI-owned Centralised Payment Systems — RTGS (large-value, real-time, 24x7x365 since December 2020) and NEFT (batch, 24x7 since December 2019), both on the e-Kuber core banking system. Since July 2021 RBI has opened direct CPS membership to authorised non-bank PSPs — PPI issuers, card networks and white-label ATM operators — under Section 10(2) read with Section 18 of the PSS Act, requiring INR25cr net worth, Indian incorporation, data-localisation, a separate IFSC, an RBI current account and INFINET/SFMS membership.

no periodic updates on record for this sub-brief

Sources and findings (5)
  1. T2https://www.thenewsminute.com/money/rbi-allows-paytm-phonepe-and-other-non-banks-access-neft-rtgs-payment-systems-153159retrieved
  2. T3https://www.drishtiias.com/daily-updates/daily-news-analysis/non-bank-psps-to-join-centralised-payment-systemretrieved
  3. T3https://affairscloud.com/rbi-allowed-non-banks-to-participate-in-cps-rtgs-neft/retrieved
  4. T3https://www.dnaindia.com/personal-finance/report-rtgs-neft-payment-systems-opened-up-for-non-banks-in-phases-rbi-2903037retrieved
  5. T2RBI non-bank CPS membership policy — RBI non-bank CPS membership policy — RBI allows regulated non-bank payment system operators (PPI issuers, card networks, White Label ATM operators, TReDS platforms) to take direct membership of RTGS and NEFT, without eligibility for RBI liquidity facilities.retrieved

#

Trailing-12-month commercial intelligence is dominated by a fintech IPO pipeline amid more selective funding. Razorpay confidentially filed a ~$600m IPO (June 2026) and obtained shareholder approval for a ₹2,700cr fresh issue; PhonePe filed in late 2025 and received listing approval in January 2026 at a $9-10.5bn target valuation; Pine Labs progressed toward its IPO. India fintech funding was $513m in Q1 2026 with a sharply falling deal count, signalling consolidation toward stronger players.

Horizon · 2026-02-28 (± a quarter)PA-P physical operator wind-up deadlineIn force · Tier 2 source
Standing sub-brief · as of 27 June 2026 260 words · last cycle 2026-10-25

Commercial Intelligence (M&A, Investment & Product)

Three discrete commercial events define this cycle's W13 entries. First, Razorpay confidentially filed for a roughly USD600m IPO in June 2026, targeting a year-end debut (last valued at around USD7.5bn in its 2021 round); it separately obtained shareholder approval in May 2026 to raise INR2,700cr (~USD283m) via the fresh-issue component plus an undisclosed offer-for-sale, with a pre-IPO placement planned before filing its RHP with SEBI. This anchors India's fintech listing pipeline and signals public-market appetite for licensed payments platforms with merchant networks.

Periodic update · new data 2026-10-25

Commercial Intelligence & Fintech

Saber Money, the entity behind the Indian cryptocurrency exchange Mudrex and a holder of licences or registrations in Canada, the European Union, India and Australia, announced a strategic investment from Tether and CMCC Global's Titan Fund between 14 and 19 October 2026. No transaction amount was disclosed in any source located, and the event is reported as an announced, not yet closed or further-detailed, investment. Tether's chief executive Paolo Ardoino's public framing of the rationale centred on emerging markets as the locus of the next phase of global payments development, with stablecoins positioned as the underlying infrastructure enabling that shift.

The investment is squarely a commercial event rather than a regulatory one: no announcement, approval or statement from an Indian regulator accompanied the transaction, and the only confirmed facts are the identity of the parties, the announced date window, and the undisclosed-amount status of the deal itself. Saber Money's multi-jurisdictional licensing footprint, spanning Canada, the EU, India and Australia, situates this transaction within a broader pattern of international stablecoin-linked capital seeking exposure to operators that already hold licensed or registered standing across several markets, India among them, rather than targeting a single-jurisdiction play.

The absence of a disclosed transaction value is itself a notable gap in the public record for this event: multiple press releases and wire syndications confirmed the fact and parties of the investment, but none carried a figure, leaving the commercial scale of the development unquantified as reported.

Outlook

Whether further detail on the transaction's size, structure, or strategic terms emerges in subsequent periods would materially sharpen the read on this development; as it stands, the event is confirmed as to occurrence and parties but unquantified as to scale. More broadly, continued strategic investment activity from stablecoin issuers into exchange operators with an India footprint would be a signal worth tracking against any future regulatory commentary from Indian authorities on stablecoin-adjacent commercial activity, though no such commentary accompanied this transaction.

1 earlier distinct update(s)
Periodic update · new data 2026-10-18

Commercial Intelligence & Fintech

India's fintech sector produced two notable discrete commercial events this cycle, set against a backdrop of overall sector funding growth alongside declining deal volume. Tracxn's nine-month 2026 report shows Indian fintech companies raised approximately 2.2 billion dollars across the January-to-September period, up 14 percent on the 1.9 billion dollars raised over the same period in 2025, even as the number of completed rounds fell sharply year on year.

The largest single funding event of the period was CRED's 540 million dollar round, one of five mega-rounds that together accounted for roughly 48 percent of all capital raised across the nine-month window. On the acquisition side, Indiabulls Group completed the purchase of Fintech Cloud for 110 million dollars, reported as the largest fintech acquisition of the nine-month period. Both figures are disclosed amounts drawn from vendor analytics reported through quality press rather than from primary deal filings independently verified this cycle.

The pattern these two events illustrate, a small number of large transactions accounting for a disproportionate share of total sector activity, is a discrete commercial-intelligence signal distinct from any structural market-concentration thesis: it describes what happened in specific, named transactions during the period rather than asserting a durable shift in India's fintech industry structure.

Outlook

Future cycles should watch for confirmation of deal terms and strategic rationale behind the Indiabulls Group acquisition of Fintech Cloud, and for whether the funding concentration pattern, a small number of mega-rounds dominating total capital raised, persists or reverses as further 2026 data becomes available.

Sources and findings (7)
  1. T3https://www.pymnts.com/news/ipo/2026/indian-payment-fintech-razorplay-planning-600-million-ipo/retrieved
  2. T3https://www.medianama.com/2026/05/223-exclusive-razorpay-shareholder-approval-rs-2700-crore-ipo/retrieved
  3. T3https://www.newskart.com/razorpay-files-confidential-ipo-papers-can-indian-fintech-still-command-big-valuations/retrieved
  4. T4https://tiimagazine.com/top-30-fintech-companies-in-india-to-watch-in-2026/ [CAVEAT: Tier 4 source — Assessed; illustrative only, verify pre-publication]
  5. T3Saber Money — Saber Money — Strategic investment from Tether and CMCC Global's Titan Fund (amount undisclosed)retrieved
  6. T3Indiabulls Group — Indiabulls Group — Acquired Fintech Cloud for $110m, the largest fintech M&A deal of 9M-2026 per Tracxnretrieved
  7. T3CRED — CRED — $540m funding round, the single largest of five mega-rounds making up 48% of 9M-2026 India fintech fundingretrieved
No modules match.

Filters combine as OR inside a group and AND across groups.

Provenance and declared absence

Disclosure model: module cards load OPEN; standing positions render in full; sub-briefs and jurisdiction briefs load as a clamped teaser with an explicit “read full” control carrying the true word count; earlier updates stay collapsed behind a counted summary. No text is hidden without disclosing how much of it there is.

Sentinel-fed modules receive no special rendering treatment. sentinel_feed is an attribution chip only: it does not suppress content, does not generate an absence reason code, and does not exclude the module from any count, filter, search index or export on this page.

Family taxonomy is renderer-level presentation config, not a JID field. Colour is always duplicated in text and is never the sole carrier of meaning.

Suppressed by doctrine: derived risk score; per-module RAG traffic light. Not shown on this page.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-11-04. A year-precision row is never promoted into a tighter band.

Orphan deltas: 1 cycle_delta row(s) target non-module objects and are listed in the rail rather than attached to a card.

Envelope: baseline resolved at jurisdiction_json.baseline; 14 module(s), 128 finding(s), 160 source(s) in the cumulative register.

Think something on this page is wrong? Report an error.