On this page
RBI-backed DPIP launches Smart Registry with eight banks, targets broader fraud-data network
Our read
India's shared fraud-data infrastructure will shift from a bank onboarding tool toward a cross-ecosystem risk utility, raising fraudster switching costs but making data quality and false-positive governance the key adoption constraint.
For operators
Smart Registry’s eight-bank launch signals a growing shared-defense layer for onboarding and account checks, making fraud-data connectivity an increasingly important operational requirement for payment and retail finance teams.
Watch
Whether the platform reaches 25 additional bank integrations within the stated two-month target window.
Ask next
The report,
RBI-backed DPIP’s Smart Registry has gone live with eight banks, enabling shared fraud intelligence for onboarding and account checks. It plans to add 25 banks and 15 payment aggregators, while Phase 2 will provide real-time risk scores for digital transactions.
- Banks live on Smart Registry from September 1
- 8 banks
- Additional banks expected within 2 months
- 25 additional banks
- Top payment aggregators targeted by end-January
- 15 top payment aggregators
- Payment-volume coverage targeted
- approximately 80%
Channel facts
From the report. Source details below
| 8 banks live from September | 1 |
|---|---|
| 12 months of transaction data used for Phase | 2 models |
Also in the report
- approximately 80% payment-volume coverage targeted
Other figures
- 4 initial use cases
What it means for online and offline
Banks, payment aggregators and fraud-tech providers should assess partnership or integration opportunities early, as DPIP could become a strategically important consortium-led fraud-data rail in India.
Signals to track
- Production launch timing, latency and measured precision of real-time transaction scoring after UAT.
- Evidence of reductions in mule-account creation, account-opening fraud, beneficiary fraud or fraud losses among the first eight banks.
- Adoption by systemically important banks, large private banks and high-volume payment aggregators rather than only smaller participants.
- RBI or DPIP guidance on data-sharing permissions, customer consent, privacy safeguards, auditability and liability for false-positive decisions.
- False-positive rates, customer complaint volumes and any increase in legitimate onboarding or payment declines.
Show 1 more
- Competitor responses from credit bureaus, fraud-tech vendors, NPCI-linked systems and bank-led consortiums.
Likely next moves
Our read of what comes next — analysis, not reported by the source.
- Prioritize integrations by fraud-loss exposure and transaction volume, using the initial eight banks to demonstrate measurable fraud-loss and mule-account reductions.
- Standardize minimum data fields, match-confidence thresholds, retention rules and dispute-resolution processes before rapid member expansion creates inconsistent decisioning.
- Move real-time transaction scoring from UAT to phased production pilots with human-review fallback for high-value declines and low-confidence matches.
- Create tiered registry products for onboarding, beneficiary/account checks, mule-network detection and transaction scoring rather than relying on a single binary fraud flag.
- Payment aggregators should assess API readiness and redesign merchant onboarding workflows to consume shared-risk signals without materially increasing approval friction.
Show 1 more
- Banks outside the network should evaluate joining versus building bilateral data-sharing arrangements, as exclusion could create an intelligence disadvantage in fraud controls.
The counter-case
The case against this reading — not reported by the source.
The launch is more a network-building milestone than proof of fraud reduction. With only eight banks live and real-time transaction scoring still in UAT, the registry may initially cover too small a share of mule accounts and cross-platform fraud patterns to materially improve outcomes. Its value depends on consistent, timely, high-quality data contribution; participating institutions may limit fields, update frequencies, or use cases because of privacy, liability, and competitive concerns. Ambitious onboarding targets do not guarantee active utilization, and aggressive screening can create false positives, customer friction, and higher manual-review costs.
The source
First seen