Halfway through a loan application, a name the customer doesn’t recognise appears on screen. It’s an account aggregator, asking permission to share their financial information.
The customer came to the bank, and the bank initiated the data-sharing request. While the aggregator manages consent, the bank needs to explain why it wants the information. Otherwise, the customer is left to make sense of a process the bank set in motion.
The framework already operates at scale. By March 2026, more than 2.88 billion financial accounts were enabled for financial data sharing under the account aggregator framework, and customers had linked 284.6 million accounts.
The RBI’s 7 October 2026 announcement of account aggregator interoperability will give customers more choice over which aggregator they use. Banks need to prepare their connections, and the customer journeys that depend on them.
What account aggregator interoperability changes, and when
Today, a customer using an account aggregator in India can share data only from institutions connected to their chosen aggregator. Interoperability will extend that access to participating institutions across the network through one aggregator.
The RBI initially expected account aggregator interoperability to be implemented by 31 December 2026. ReBIT has since published technical specifications and revised the adoption deadline for account aggregators, Financial Information Providers and Financial Information Users to 1 December 2026. This is the adoption deadline for interoperability, not confirmation that every institution is already live.
Banks have responsibilities on both sides
A bank can provide financial information or request it. As a Financial Information Provider (FIP), it holds customer financial information and shares it against valid consent. As a Financial Information User (FIU), it requests information from other institutions for a specific purpose.
For example, a lender may request six months of transactions from a salary account held at another bank to assess a loan application.
Banks need to prepare for both roles. Sahamati’s summary of the RBI executive director’s SamvAAd keynote emphasises that institutions using financial information must also fulfil their responsibilities as providers.
Review your existing integrations
ReBIT’s technical specifications for account aggregator interoperability cover the APIs and communication flows used by Account Aggregators, Financial Information Providers and Financial Information Users.
Banks should review the specifications against their role in the framework. Identify which APIs apply, compare them with existing integrations and determine what needs to change.
Work with aggregator partners and technology providers to agree on the required changes, implementation responsibilities and testing plan. The aim is to ensure the bank can exchange financial information through the new interoperability connections, not just its existing direct connections.
Explain the request before asking for consent
Before directing a loan applicant to an aggregator’s consent screen, the bank should explain what information it needs and why. The aggregator then presents the request, including the data type, purpose, recipient and consent expiry, for the customer to review and approve or decline.
“Share financial data to continue” gives the applicant little basis for that decision. “We need six months of transactions from your salary account to assess your loan application” explains the purpose.
That explanation must match the actual request, including whether access is one-time or recurring. A correctly completed consent process does not, by itself, mean the customer understood what they approved.
What happens when they decline
Banks should distinguish between a customer declining consent and a technical failure during data sharing. If a connection fails, explain the issue and allow the customer to retry without treating it as a refusal. If the customer declines, clearly explain how that decision affects the application and what options are available next.
An optional question about why they declined can help the bank understand whether the concern relates to the information requested, the purpose or the way the request was explained.
What to prepare before implementation
Once the technical changes are identified, banks need to agree on how the new process will be managed.
Assign responsibility for investigating failed requests and resolving issues that involve the bank and its aggregator partners. Prepare support teams to answer questions about unfamiliar aggregator names and bank deposits appearing in consolidated account statements.
Then test the complete data-sharing journey. Include successful requests, declined consent and failed connections. Check whether customers understand the request, know what happens after their decision and can proceed when a connection fails.
At Clayfin, we believe digital banking should make each step clear and easy to follow. As banks prepare for account aggregator interoperability, a useful starting point is to follow one loan application through the entire data-sharing journey, including a refusal or a failed connection.
Wherever the customer is left to work out what happens next, the bank has more work to do.