Account Aggregator API Integration
Consent-driven financial data sharing across banks via the RBI Account Aggregator framework. FIU-grade integration.
What Account Aggregator API integration does
The RBI Account Aggregator framework is the most consequential change to Indian credit underwriting in a decade. It replaces customer-supplied PDF bank statements — slow to collect, tedious to parse, trivially forged — with structured financial information delivered straight from the bank under a consent the customer grants and can revoke.
Our integration implements the full ReBIT-specified flow: consent artefact creation, consent handle tracking, FI request and FI data fetch, under FIU-grade access. The consent artefact is the heart of it. It records purpose, data scope, frequency and expiry, and every subsequent fetch is bound to it. That is what makes the framework defensible to a regulator and, equally, what makes a sloppy implementation a compliance exposure rather than merely a bug.
What you receive is structured: account summaries, balances and transaction data you can score directly, with no parsing layer and no question about whether the document was edited before it reached you.
What teams build with it
Statement-free underwriting
Raise a consent request, fetch structured transaction data and score the applicant without a single uploaded document.
Cash-flow lending
Underwrite thin-file and self-employed borrowers on observed cash flow rather than on a formal income proof they cannot produce.
Ongoing portfolio monitoring
Use a recurring consent to refresh financial data across the loan life and catch deterioration before a missed payment.
Personal finance and advisory
Aggregate a customer's accounts with consent to power budgeting, advisory or wealth products.
Endpoints included
POST/aa/v2/consentCreates a consent request for a customer to share specified FI types.POST/aa/v2/fi/fetchRetrieves financial information once consent is approved.
Try it in the sandbox
https://sandbox.aeologic.io/aa/v2/consent{
"customer_vua": "9928174455@finvu",
"fi_types": [
"DEPOSIT",
"TERM_DEPOSIT"
],
"purpose": "Loan eligibility assessment",
"duration_days": 90
}What you need before we start
- Your regulated position and FIU scope, confirmed during onboarding
- A defined data purpose, scope and retention period for the consent artefact
- A consent journey that presents purpose and scope clearly to the customer
- Handling for consent revocation and expiry
How we deliver it
- Scoping of your FIU position and the consent template for your use case
- Sandbox integration covering consent, FI request and FI fetch
- Revocation and expiry handling wired into your data lifecycle
- Production rollout with consent-artefact audit logging
Related Financial Data integrations
Industries using Account Aggregator
Solution bundles that use it
Account Aggregator API integration — FAQs
Do we need to be a registered FIU?
Access runs under Aeologic's FIU-grade integration, which lets regulated customers begin consented fetches without standing up their own AA connectivity. Your own registration position depends on your regulator and is scoped during onboarding.
What data actually comes back?
Structured financial information — account summaries, balances and transaction records — as defined by the consent scope, rather than a document you have to parse.
Can the customer revoke consent?
Yes, at any time, and revocation takes effect immediately. Our connector surfaces revocation events so your system stops fetching rather than failing silently.
How is this better than statement upload?
It is faster, structured rather than parsed, tamper-evident because it comes from the bank, and consent-governed end to end. The drop-off difference against asking a customer to find and upload six months of statements is substantial.
Ship Account Aggregator in days
Tell us your stack and we'll wire up Account Aggregator API integration for your team.
Talk to Aeologic