DEV Community

Cover image for Integrating India's Account Aggregator API as an FIU: A Developer's Field Guide (2026)
ZANISS SOFTWARES
ZANISS SOFTWARES

Posted on Originally published at zanisssoftwares.com

Integrating India's Account Aggregator API as an FIU: A Developer's Field Guide (2026)

If you're the engineer who just got handed the ticket "add Account Aggregator support for underwriting," here's what the API-level reality looks like in 2026, past the marketing decks.

AA integration is fundamentally a consent-artifact handshake across three parties — your FIU backend, a licensed Account Aggregator (AA), and the Financial Information Provider (FIP) holding the data. You never talk to the FIP directly. Your flow looks like this:

  1. POST a consent request to your chosen AA, specifying fiTypes (DEPOSIT, EQUITIES, GSTR1, etc.), the date range, purpose code and consent life (ONETIME vs PERIODIC).
  2. The AA hands the customer a consent handle; they approve it in the AA's own app via mobile+OTP account linking — you don't build this UI, the AA does.
  3. On approval, you receive a signed consent artifact — cache its reference ID, you'll need it for every subsequent data pull.
  4. Request data against that consent handle. The AA orchestrates the pull from each FIP; the FIP encrypts the payload with your public key before it ever leaves their system — the AA is a blind router, not a data holder.
  5. You decrypt and parse the response against Sahamati's standardized FI schemas (structured JSON per data type — bank transaction statements, GST filings, equity holdings, etc.).
  6. Build your deletion job now, not later — your "consent life" window is a hard compliance deadline, and DPDP Act obligations stack on top of the AA consent rules.

As of March 2026 there are 17 live AAs to choose from (Anumati, CAMS AA, OneMoney, Finvu, Setu, NADL and others), each with different live FIP coverage — Anumati and CAMS AA currently lead with 70-80+ live FIP connections, but coverage of specific banks/insurers varies enough that most production FIUs integrate against 2-3 AAs for redundancy rather than one.

Budget-wise: a single-endpoint pilot (one AA, one-time consent, one data type) is realistically a 2-4 month build for a small team; a production multi-AA, multi-data-type integration with a consent-lifecycle dashboard is closer to 4-8 months. Treat those timelines as planning ranges rather than estimates for your project: they shift with team size, how many FI types you parse, and how quickly your chosen AA onboards you. We wrote up the full cost breakdown with tiered pricing tables, timeline estimates and a decision framework in our complete guide: Account Aggregator (AA) Framework Integration Cost for Indian Fintechs & Lenders in 2026.

One thing worth flagging to your PM early: don't confuse this with ULI or UPI integration — different APIs, different licensing, different teams usually end up owning each one.

Top comments (0)