LaunchCode

Account Aggregator hits scale, but consent-flow drop-offs are now the bottleneck

Account Aggregator hits scale, but consent-flow drop-offs are now the bottleneck

The Account Aggregator framework, the RBI-supervised data-sharing architecture that allows financial institutions to access a customer's financial data with explicit, revocable consent, has crossed material milestones in both linked accounts and successful data fetches since its live deployment in 2021. Lenders, wealth-tech platforms and personal-finance management apps have integrated the framework into their user journeys, enabling faster loan origination, more accurate financial planning and portfolio-level visibility that was previously impossible without cumbersome manual document collection. The limiting factor that has emerged clearly from the operational data is not technology or institution participation - both of which have improved substantially - but user behaviour at the consent step. When a first-time AA user encounters the consent screen - which asks them to authorise a specific entity to access specific financial accounts for a specified period - a meaningful fraction abandon the process before completing it. The drop-off rate at the consent step, which varies by use case, interface quality and the financial literacy of the user, is the primary constraint on the framework achieving its potential reach. The design challenges at the consent step are partly technical and partly behavioural. The information presented on the consent screen needs to be accurate and complete under the AA framework's regulations, which means it includes legal language about data access scope and duration that is accurate but sometimes confusing for users who are unfamiliar with the framework. The visual design of consent screens across different AA entities and financial information users varies, creating inconsistency that reduces user confidence. The mobile-to-mobile app transition required to complete consent - switching from the initiating app to the user's bank app and back - introduces friction that is inherent to the decentralised architecture. The Sahamati consortium, which coordinates the AA ecosystem's development, has been working on standardised consent-screen design guidelines and simplified language that can reduce the drop-off rate without violating the disclosure requirements. Industry pilots have shown that consent completion rates can be improved by fifteen to twenty-five percentage points through specific UX interventions, which at the scale of millions of consent attempts annually translates into a significant number of additional successful data fetches and the financial products that depend on them. What to watch: whether SEBI's planned integration of the AA framework for securities-portfolio data sharing significantly expands the framework's utility beyond lending, how the consent completion rate metrics improve as ecosystem-wide UX guidelines are implemented, and whether the introduction of consent managers - intermediaries that manage consent on behalf of users across multiple data sources - simplifies the user experience at scale.

Original source: Inc42