India doesn’t use the term “open banking” the way the UK or Australia does. There’s no single regulation mandating banks to share data through standardized APIs. Instead, India has built something arguably more ambitious: a layered digital infrastructure — collectively known as India Stack — that enables data sharing, identity verification, and payment integration through distinct but interconnected platforms.

At the heart of the open banking story in India is the Account Aggregator (AA) framework. Understanding where it stands in 2026 tells you most of what you need to know about India’s approach to financial data sharing.

Account Aggregator: The Current State

The AA framework went live in September 2021. The concept is straightforward: Account Aggregators are licensed entities that facilitate the transfer of financial data from Financial Information Providers (FIPs — banks, insurers, mutual funds) to Financial Information Users (FIUs — lenders, wealth managers) with the customer’s consent.

By early 2026, the AA ecosystem includes over 20 licensed AAs, with Sahamati (the industry alliance) reporting cumulative consent artifacts in the hundreds of crores. But those headline numbers mask significant operational challenges.

Data from Sahamati’s public dashboard shows that while consent creation has grown steadily, the percentage of consents that result in successful data fetches is lower than ideal. Connection failures between AAs and FIPs, data format inconsistencies, and timeout issues mean that the user experience still isn’t as smooth as it should be.

Who’s Using It and Why

Digital lenders are the largest consumers of AA data. When a borrower applies for a loan, the lender can request bank statement data through the AA framework instead of asking the borrower to upload PDFs. The data arrives in a structured, machine-readable format that can feed directly into credit assessment models.

This has genuine benefits: faster loan processing, more accurate income assessment, and reduced document fraud. A PDF bank statement can be fabricated relatively easily. Data pulled through the AA framework, digitally signed by the originating bank, is much harder to tamper with.

Wealth management platforms use AA data to build consolidated financial views for clients. Instead of manually adding accounts from different banks, insurance companies, and mutual fund houses, the AA framework can pull it all together automatically.

Insurance underwriting is an emerging use case. Access to bank transaction data gives insurers a more granular view of an applicant’s financial behaviour, potentially enabling better risk assessment and pricing.

The Integration Reality

While the framework exists and works in principle, the practical integration experience varies enormously across institutions.

Large private banks (HDFC Bank, ICICI Bank, Axis Bank) have invested in robust FIP interfaces. Their data responses are generally reliable, structured correctly, and available within acceptable timeframes.

Public sector banks present a mixed picture. SBI, as the largest bank, has made significant progress. Several mid-tier public banks have functional AA interfaces but with higher failure rates and slower response times. Some smaller banks have minimal AA capability.

Non-bank FIPs — mutual fund houses, insurance companies, pension funds — are at various stages of readiness. SEBI-regulated entities have been slower to implement AA integration than RBI-regulated banks, partly because the regulatory mandate came later and partly because the technical infrastructure is less mature.

The API standardization that makes AA work in theory still has gaps in practice. While the data schema is defined, interpretation varies. How one bank categorizes a transaction type may differ from another, creating challenges for FIUs trying to analyze consolidated data consistently.

API Banking Beyond AA

Outside the AA framework, Indian banks are opening up through direct API platforms. ICICI Bank’s API Banking portal, HDFC Bank’s SmartHub APIs, and Yes Bank’s developer platform all offer programmatic access to banking services.

These aren’t standardized in the way open banking APIs are in the UK (where the Open Banking Implementation Entity defines exact specifications). Each bank offers its own API set with its own documentation, authentication methods, and capabilities.

For businesses integrating with multiple banks, this means maintaining multiple integrations with different specifications. API aggregators like Finbox, Perfios, and Setu have emerged to abstract this complexity, offering unified APIs that connect to multiple banks behind the scenes.

Enterprise AI work in the banking sector has increasingly focused on making sense of data flowing through these various API channels — normalizing formats, enriching transaction data, and building predictive models on top of the standardized data feeds.

OCEN: The Lending Layer

The Open Credit Enablement Network (OCEN) adds another dimension. Designed to enable any platform with customer relationships to offer credit products, OCEN standardizes the loan origination workflow through APIs.

The idea is that a dairy cooperative’s app, a trucking logistics platform, or an agricultural marketplace could embed lending directly into their platforms using OCEN APIs, connecting their users to willing lenders without building lending infrastructure themselves.

OCEN has moved slowly. The initial pilot was limited, and scaling has been challenging. The core technical framework works, but the commercial incentives for all parties — loan service providers, lenders, technology providers — haven’t aligned perfectly.

The concept remains powerful. India has millions of small businesses that need credit but don’t interact with traditional banking channels. Embedding credit into platforms they already use could dramatically expand access. But execution complexity has tempered early enthusiasm.

The ONDC Factor

The Open Network for Digital Commerce isn’t technically open banking, but it intersects in important ways. ONDC’s vision of an open protocol for e-commerce means that financial services — payments, credit, insurance — can be integrated into any ONDC-enabled platform.

The convergence of ONDC, OCEN, and AA creates a theoretical end-to-end ecosystem where a buyer on any platform can access credit based on their financial data (via AA), receive the loan through standardized protocols (via OCEN), and transact on any commerce platform (via ONDC).

This convergence is years away from smooth reality, but the architectural vision is there.

Challenges and Gaps

Consent management remains imperfect. Customers granting data access through AA often don’t fully understand what they’re consenting to, how long the access lasts, or how to revoke it. The consent artefact is technically well-designed, but the user-facing explanation of what consent means is often inadequate.

Data quality from FIPs varies. Categorization inconsistencies, missing fields, and delayed data availability all affect the usefulness of AA data for downstream applications.

Dispute resolution when AA data is inaccurate or misused lacks a clear, fast mechanism. If a lender denies credit based on incorrect data received through AA, the borrower’s recourse path isn’t well-defined.

Security concerns scale with adoption. As more data flows through the AA ecosystem, it becomes a more attractive target for attacks. The consent-based architecture provides inherent protection, but the operational security of AAs themselves is a potential weak point.

Where Things Are Heading

The direction is clear: India’s financial data infrastructure will continue to expand. More FIPs will join the AA network. More use cases will emerge beyond lending. The APIs will stabilize and improve.

What’s less clear is the timeline. The optimistic view predicted mass adoption by 2025, which hasn’t happened. The infrastructure is built, but changing institutional behaviour and customer habits takes longer than building technology.

India’s approach — building public infrastructure that private players use — is fundamentally different from the regulatory mandate approach used in the UK and EU. Both have their strengths. India’s approach is more flexible and innovation-friendly but relies on voluntary participation, which can be slow.

For banks and fintechs operating in India, the message is clear: API integration capability isn’t optional. The institutions that invest in robust, reliable API infrastructure today will be better positioned as the open data ecosystem matures. Those treating API compliance as a checkbox exercise will find themselves at a competitive disadvantage when the ecosystem reaches critical mass.