Technology Service Providers: The Invisible Layer Making Account Aggregation Work

India's Account Aggregator framework is one of the most ambitious consent-driven data-sharing systems anywhere in the world. It gives customers a simple, standardized way to authorize the movement of their financial data from one institution to another — a Financial Information Provider (FIP) to a Financial Information User (FIU) — through a licensed Account Aggregator.

The framework works because of what most people never see: the Technology Service Provider (TSP) layer. TSPs are the connective tissue that turns the AA specification into a functioning production system for the banks, NBFCs, insurers, and fintechs who plug into it.

What a TSP Actually Does

A TSP is a technology partner that sits between a regulated financial entity and the Account Aggregator network. On the FIP side, the TSP takes the entity's underlying data — often held in decades-old core banking systems, insurance policy stores, or lending management platforms — and exposes it through the standardized AA APIs. On the FIU side, the TSP takes raw JSON responses from FIPs and turns them into usable, normalized data for credit decisions, underwriting, or account monitoring.

In both directions, the TSP handles the messy, non-differentiating work: schema mapping, session orchestration, retry logic, encryption and key management, error handling, and the observability needed to run the integration at production scale.

The FIP Side: Making Legacy Data API-Ready

Most FIPs — banks, NBFCs, insurers, mutual fund houses — did not build their core systems with real-time API exposure in mind. Their data lives in mainframes, relational stores, and batch-updated warehouses, spread across silos that reflect decades of product launches, mergers, and platform migrations.

A TSP resolves this by acting as a translation and orchestration layer. It queries the underlying systems in whatever way they need to be queried, normalizes the output into the AA schema, and serves it back to the requesting Account Aggregator inside the tight latency budgets the framework requires.

The FIU Side: Turning Raw Data into Decisions

For an FIU — typically a lender, an insurer, or a wealth manager — the raw data returned by an AA request is a starting point, not an answer. Twelve months of transactions across three accounts is a lot of JSON. Turning it into a credit decision, a fraud signal, or a cash flow forecast requires a second layer of work: categorization, income detection, obligation identification, anomaly flagging, and confidence-scored feature extraction.

This is where the TSP earns its second keep. A good FIU-side TSP delivers analytics-ready data, not raw dumps — and pairs it with the observability an FIU needs to trust what's being handed to their credit or risk engines.

Why 'Just Build It Yourself' Rarely Works

Every FIP and FIU that has tried to build AA integration in-house has learned the same lesson: the specification is only the beginning. Real-world integration involves handling dozens of FIP-side quirks, managing encryption at multiple layers, running certificate rotations, handling partial failures gracefully, and staying current with the framework's evolving technical standards.

Doing all of that reliably, at scale, and with the audit posture that regulators expect, is a substantial engineering commitment. For most institutions, that commitment competes for engineering attention with actual product work. A specialist TSP takes the plumbing off the plate and lets the institution focus on the decisions the data enables.

Choosing a TSP

The right TSP for a given institution depends on which side of the network they sit on, which data domains they need to cover, and what regulatory and audit posture they need to maintain. Ask about FIP coverage, historical uptime, encryption architecture, data-retention policies after consent expiry, and how quickly the TSP has historically responded to updates in the AA technical specifications.

The most important question, though, is philosophical: does the TSP treat the framework as a compliance checkbox or as infrastructure worth investing in? The answer tends to show up in the details — in how they handle edge cases, in how they log, and in how quickly they respond when something breaks at 2 a.m.