Transaction & Payment Processing Services · Reserve Bank of India
Reserve Bank of India - Payment System Indicators (Monthly Volume and Value)
Datadory delivers reserve bank of india payment system indicators monthly volume and value data covering every Indian rail the central bank counts - RTGS, NEFT, UPI, IMPS, NACH, cards, prepaid instruments, ATMs, PoS terminals, Bharat QR and UPI QR - in five parts per edition with fiscal-year-to-date totals, month-end infrastructure stocks and a domestic fraud series, delivered daily, weekly, or hourly on your cadence.
API, files, or your warehouse. Daily, weekly, or hourly.
- Where it covers
- India, domestic financial transactions only - failed transactions, chargebacks and reversals excluded by construction; Part IV separately covers international use of India-issued cards and PPIs
- How far back
- Monthly editions archived back to 1990; the current five-part format with granular retail modes runs from November 2019; the domestic fraud series in Part V is shown from September 2022
- How fine
- Monthly totals per payment system or mode, fiscal-year-to-date aggregates beside same-month-last-year comparisons, and month-end infrastructure stock counts in Part III
What is the RBI Payment System Indicators dataset?
It is the Reserve Bank of India's own statistical readout on the payment system it supervises, published monthly as five typed tables and restructured here into records a database can join. Part I carries the headline volume (lakh) and value (Rs. crore) columns - fiscal year to date, same month last year, and the two most recent months - across three tiers: securities and FX markets cleared through CCIL-operated FMIs, RTGS at the wholesale-customer boundary, and the full retail stack underneath it.
That retail stack is where India's payments story lives: AePS fund transfers, APBS, IMPS, NACH credit and debit, NEFT, UPI including its USSD channel, BHIM Aadhaar Pay, NETC toll collections, card payments split between PoS and other acceptance, prepaid payment instruments, and CTS paper instruments as the legacy baseline. The June 2026 edition puts UPI alone at 2,27,160.66 lakh transactions worth Rs. 28,92,139 crore in the month, inside 2,61,705.81 lakh total digital payments worth Rs. 3,17,64,092 crore.
The remaining four parts make this more than a volume sheet. Part II re-cuts payments by mode and channel, Part III stocks the installed infrastructure at month end, Part IV follows India-issued cards and PPIs abroad, and Part V publishes the domestic fraud series with its ratio expressed in basis points.
What do sample rows look like?
One rail first, then the structure around it - exactly as a delivery lands:
# Part I - June 2026 edition - volume in lakh, value in Rs. crore
row=2.6 UPI vol_FY2025_26=2416168.86 vol_June2026=227160.66
val_FY2025_26=31423250 val_June2026=2892139
row=Total Digital Payments (1+2+3+4+5)
vol_FY2025_26=2817448.36 vol_June2026=261705.81
val_FY2025_26=325103565 val_June2026=31764092Volume and value ride on the same row, which is the whole analytical trick: divide them once and you have UPI's implied average ticket size, month over month, without stitching two tables together. The fiscal-year-to-date column sits beside the monthly one, so a year-to-date reconciliation is a subtraction, not a rebuild.
The stock side lands just as cleanly:
# Part III - June 2026 edition - stock counts in lakh, as on month end
row=7 UPI QR May2026=7797.65 June2026=7925.74
row=1 Number of Cards (Credit + Debit) June2026=11534.57
# Part V - domestic payment frauds, June 2026
frauds: volume_lakh=3.53 value_crore=489 ratio_bps=0.150A single month moves UPI QR acceptance by roughly 128 lakh codes while total cards sit above 11,500 lakh - acceptance infrastructure and instrument supply moving on separate clocks, in one schema.
What fields does the dataset include?
Six field roles cover all five parts. The payment-system label keys each row to a settlement system, retail mode, channel or infrastructure item - '2.6 UPI', 'Number of PoS Terminals' - preserving the part's own numbering so cross-edition joins stay stable. Volume (lakh) and value (Rs. crore) are the paired measures in Part I and Part II; the lakh-crore convention matters because average ticket analysis needs both unrounded.
Fiscal-year-to-date columns accumulate from April, and the monthly columns run same-month-last-year plus the two most recent months, giving every row its own YoY comparison out of the box. Stock-count columns ('As on March 2026'-style headers) drive Part III, where the unit is outstanding items in lakh rather than period activity.
Every definition was verified against parsed editions during research, backed by published sample rows. Two structural notes ship with any sample because they change what you can claim: the ECS-to-NACH merger effective January 31, 2020, and revised card/PPI definitions from November 2019 onward that make those series incomparable with earlier periods. Deeper columns confirmed during sample preparation fold out under additional fields on request.
How wide is the coverage?
Geography: India, scoped to domestic financial transactions - failed transactions, chargebacks, reversals and expired cards are excluded by definition, so the numbers measure completed commerce rather than attempted attempts. Part IV steps outside the border to track international transactions made using India-issued cards and PPIs.
Temporal: the archive reaches back to 1990, though the series is not uniform across that span. The current five-part format with granular retail-mode rows dates from November 2019, and the card and PPI series from that point onward are explicitly not comparable with earlier periods due to revised definitions. The domestic fraud series in Part V runs from September 2022. Figures in recent editions are marked provisional until finalized.
Granularity: monthly totals per payment system or mode, with fiscal-year-to-date aggregates alongside, and month-end stock counts for everything installed - terminals, QR codes, cards, ATMs, CRMs. Roughly 100 data rows per edition means the entire national payments picture fits in memory, not a cluster.
How is the data delivered?
API, files, or your warehouse. Daily, weekly, or hourly.
Pick the channel your team already works in: structured payloads for live lookups on a specific rail or indicator, flat files sized for overnight warehouse loads, or a direct pipe into Snowflake, BigQuery or Redshift. Cadence is yours to set - and to change when your models change.
Every delivery ships the full field dictionary, sample rows for validation, and a schema that holds steady between deliveries.
The source releases as formatted spreadsheet and document tables, roughly 490 KB per edition across about 100 rows in five parts. Turning that layout into the six-role schema above - typed measures, split periods, preserved part numbering, footnote caveats attached to the series they govern - is our pipeline's work, not yours.
Who uses this data, and for what?
- Investors and quant researchers treat the UPI-versus-card split as a public read on Indian digital-payments adoption, watching volume growth in lakh against value growth in crore to see ticket sizes fall as acceptance spreads.
- Payments strategists and market sizers build rail-by-rail India models from one internally consistent official table instead of reconciling press releases, presentations and third-party estimates that never quite agree.
- Fraud and risk analysts benchmark their own book against Part V's national figures - the 'one in every X transactions fraudulent' rate and the fraud-to-payment-value ratio in basis points - rather than against anecdotes.
- Competitive intelligence teams track acquiring-side infrastructure directly: PoS terminal installs, micro-ATM rollout, Bharat QR versus UPI QR counts as month-end stocks.
- Market researchers and consultants ground fintech market maps and India-entry theses in official rail-level volumes and channel splits.
More applications by team live on the investors quants use cases and market researchers use cases briefings.
Which personas get the most value?
Investors and quant researchers get the cleanest public panel on India's payment rails, refreshed on their cadence rather than the release calendar; see investors quants use cases. Payments strategists and market sizers get one consistent denominator across every rail they compare. Fraud and risk analysts get a national baseline with the ratio pre-computed in basis points. Competitive intelligence and product teams get the acceptance-infrastructure story - terminals, QR codes, micro-ATMs - as stock counts rather than marketing claims. Data scientists and ML engineers get a long, documented monthly panel whose definitional break points are stated up front instead of discovered mid-backtest; see data scientists use cases. Market researchers and consultants get the official anchor every India fintech deck should cite; see market researchers use cases.
What should I know before requesting a sample?
Three things, stated up front.
First, the archive is deep but not uniform. Monthly editions exist back to 1990, yet the granular five-part structure only starts in November 2019, card and PPI definitions changed at that point enough to break comparability with earlier years, and Part V's fraud series begins in September 2022. Tell us how far back you actually need and we will shape the sample to the comparable window.
Second, the units are Indian conventions, kept deliberately. Volume arrives in lakh and value in Rs. crore, exactly as published - converting to millions and billions is a one-line transform we would rather leave to you than round-trip on your behalf and risk silent scale errors.
Third, recent months are provisional. The current edition's figures are flagged provisional in the source footnotes, which matters if you are building a nowcasting model: the latest point can move. Name the rails, indicators and months you care about and the sample comes back shaped to them, caveats attached to the series they govern.
Field dictionary
Every field below is documented against real records. The full dictionary ships with the sample.
| field | type | definition | example |
|---|---|---|---|
Payment system / mode label | string | Row label identifying the settlement system, retail payment mode, channel or infrastructure stock item; preserves each part's own numbering so cross-edition joins stay stable. | 2.6 UPI @ |
Volume (lakh) | number | Transaction count in lakhs (one lakh = ten million) for the reported period; paired with value on the same row. | 2416168.86 |
Value (Rs. crore) | number | Transacted value in crores of Indian rupees for the reported period; dividing by volume gives implied average ticket size. | 31423250 |
FY <year>-<year> | number | Cumulative volume or value for the fiscal year to date, running from April. | FY 2025-26 |
<Month> <year> columns | number | Monthly volume or value for the same month one year prior and for each of the two most recent months. | May 2026 / June 2026 |
As on <month> | integer | Month-end stock-count column header used in Part III for infrastructure items outstanding - terminals, QR codes, cards, ATMs, CRMs. | As on March 2026 |
Questions buyers ask
What fields does reserve bank of india payment system indicators monthly volume and value data include?
Payment-system row labels keyed to each rail, transaction volume in lakh, transaction value in Rs. crore, fiscal-year-to-date aggregates, same-month-last-year and two recent monthly columns, and month-end stock-count headers for Part III infrastructure items. Six field roles cover all five parts of each edition, with extended columns confirmed during sample preparation.
Which payment systems does the dataset cover?
CCIL-operated FMIs for government securities outright, repo and tri-party repo, forex clearing and rupee derivatives; RTGS customer and interbank transfers; and the retail stack - AePS, APBS, IMPS, NACH credit and debit, NEFT, UPI including USSD, BHIM Aadhaar Pay, NETC, card payments split PoS versus others, prepaid payment instruments and CTS paper instruments.
Does the data include UPI volumes and values?
Yes, on both measures at once. The June 2026 edition shows UPI at 2,27,160.66 lakh transactions worth Rs. 28,92,139 crore in the month, with fiscal-year-to-date totals of 24,16,168.86 lakh transactions and Rs. 3,14,232.50 billion-equivalent crore alongside. Dividing value by volume yields the implied average ticket size for any month.
How far back does the archive go?
Monthly editions reach back to 1990, but the usable windows differ by series: the current five-part format with granular retail modes starts November 2019, card and PPI series from then onward are not comparable with earlier periods after revised definitions, and the domestic fraud series runs from September 2022. Samples are cut to the comparable window you specify.
Is there a fraud dataset included?
Part V of each edition publishes domestic payment frauds: monthly fraud volume in lakh and value in crore, a 'one in every X transactions fraudulent' rate, and a fraud-to-payment-value ratio in basis points, shown from September 2022. It is the national baseline many teams benchmark their own fraud rates against before tuning internal thresholds.
What granularity is the data reported at?
Monthly totals per payment system or mode, with fiscal-year-to-date aggregates beside them and same-month-last-year columns for built-in YoY comparison. Part III infrastructure items are month-end stock counts rather than period flows, and Part V fraud ratios are computed monthly. Roughly 100 rows per edition keep the full picture queryable without aggregation layers.
Who uses rbi payment system indicators data?
Quant investors read UPI-versus-card momentum as an adoption signal. Payments strategists size each rail from one consistent official table. Fraud teams benchmark against the national basis-point ratio. Competitive-intelligence teams watch PoS, micro-ATM and QR install bases, and consultants anchor India fintech theses in official rail-level figures.
Datasets that pair with this one
- UK Finance / Pay.UK - UK Payment Markets and Payments Statistics The UK counterpart rail-by-rail - pair the two for an India-versus-UK digital payments comparison off official tables.
- Kaggle - IEEE-CIS Fraud Detection - 590K+ Transaction and Identity Tables (Vesta) Transaction-level labeled fraud for modeling; this dataset supplies the macro fraud ratios to calibrate against.
- World Bank DataBank - Global Financial Inclusion (Global Findex Query Interface) Survey-side account ownership and usage - complements these rails-level flows with the demand-side view.
- Transaction & Payment Processing Services data hub The full pooled industry view, from labeled fraud benchmarks to national payment-market statistics.
See the rows before you pay anything.
Name this dataset and we send real records from it — scoped to the fields you asked for.