RBI-Regulated Framework

Account Aggregator API

India’s consent-based financial data sharing framework — what it is, who the licensed players are, what data you receive and how Roopya’s ready-to-use AA API works .

15 min read • Published 23-Aug-2026
6+
RBI-licensed Account Aggregators in India
1,100+
Banks and FIPs connected to the AA network
2 Days
Go-live time with Roopya’s unified AA API

What is an Account Aggregator?

The RBI’s framework for secure, consent-based financial data sharing in India.

An Account Aggregator (AA) is a category of entity licensed and regulated by the Reserve Bank of India under the Financial Data Sharing and Monitoring Framework. The AA acts as a secure intermediary that retrieves a customer’s financial data from one or more Financial Information Providers (FIPs) — such as banks, NBFCs, mutual fund houses, and insurance companies — and delivers it to a Financial Information User (FIU), such as a lender, strictly based on the customer’s explicit, time-bound, purpose-specific consent.

The customer is always in control. They decide what data is shared, with whom, for what purpose, and for how long. No data flows without an active, digitally signed consent artefact that the customer has approved. The customer can revoke consent at any time.

Key Principles of the AA Framework

  • Consent-driven: Data moves only when the customer grants explicit, digitally signed consent — never automatically.
  • Purpose-limited: Each consent request specifies the exact purpose, data types, and duration for which the FIU can access data.
  • Time-bound: Consents expire automatically. A typical consent for loan underwriting is valid for a few hours to a few days.
  • Revocable: The customer can revoke consent at any time, immediately cutting off the FIU’s access.
  • Non-storage by default: The AA does not store the financial data it transmits — it is a pipe, not a store.
  • Standardized: Data is exchanged in the ReBIT-standardized format, ensuring interoperability across all AAs, FIPs, and FIUs.

Why the AA Framework Matters for Lenders

Before the AA framework, lenders had to rely on physical bank statements or bureau data alone. The AA framework gives lenders real-time, machine-readable, verified bank transaction data directly from the source — enabling faster, more accurate credit decisions, especially for thin-file borrowers and small businesses.

The Four Roles in the AA Ecosystem

Every participant has a specific, RBI-defined role in the data flow.

Data Owner

CU — Customer

The individual or business whose financial data is being shared. Initiates and approves all consent requests, and can revoke access at any time.

Intermediary

AA — Account Aggregator

The RBI-licensed entity that manages consents and routes data requests between FIPs and FIUs. Never stores financial data — a secure conduit only.

Data Source

FIP — Financial Information Provider

The bank, NBFC, mutual fund, or insurance company that holds the data and releases it upon a valid consent-linked request.

Data Consumer

FIU — Financial Information User

The lender or fintech that requests data for a specific purpose and receives it in a standardized format for processing.

Licensed Account Aggregators in India

As of 2026, all are interoperable through the Sahamati alliance — a consent created on one AA can fetch data from FIPs connected to any other AA in the network.

RBI-Licensed AA

Anumati

  • Operated by Perfios subsidiary
  • Strong FIP coverage across major banks
  • Integrated with 100+ FIUs
RBI-Licensed AA

CAMS FRS

  • Operated by Computer Age Management Services
  • Deep mutual fund and insurance FIP connectivity
  • Widely used by NBFCs and banks
RBI-Licensed AA

Finvu AA

  • Operated by Cookiejar Technologies
  • Open API with developer-friendly docs
  • Coverage across 500+ bank FIPs
RBI-Licensed AA

OneMoney

  • Operated by ProductNext Solutions
  • One of the earliest AAs to go live
  • Broad bank and NBFC FIP coverage
RBI-Licensed AA

NESL

  • National E-Governance Services Limited
  • Backed by public sector institutions
  • Focus on government and PSU bank FIPs
RBI-Licensed AA

Sespi

  • Operated by Account Aggregator Sespi
  • Newer entrant with growing FIP network
  • Competitive pricing for FIUs

Sahamati — The Industry Alliance

Sahamati is not an AA itself. It’s the non-profit industry alliance that sets interoperability standards, manages the shared registry of AAs/FIPs/FIUs, and ensures consents and data flow seamlessly across all licensed AAs.

Roopya’s Role: A Ready-to-Use AA API

One unified API that handles multi-AA routing, consent management, data fetching, and normalization.

Integrating directly with multiple Account Aggregators is complex — each has its own API spec, authentication flow, consent lifecycle, and response format. A lender reaching all bank FIPs typically needs to integrate with 3–6 AAs separately, taking 4–8 weeks of engineering effort.

Roopya solves this with a single, unified REST API. You call one set of endpoints, and Roopya handles routing, consent approval, data fetching, and normalization — so you go live in 1–2 days instead of weeks.

What Roopya’s AA API Handles for You

  • Multi-AA routing: Roopya automatically selects the best AA for each customer’s bank.
  • Consent lifecycle management: Create, track, and revoke consents through a single API.
  • Customer consent UI: A hosted, mobile-friendly consent approval page.
  • Data fetch and normalization: Raw ReBIT data normalized into clean, consistent JSON.
  • Webhook notifications: Real-time callbacks — no polling required.
  • Bank statement parsing: Structured fields plus cashflow analysis, EMI detection, income estimation.

How to Use the Account Aggregator API

The end-to-end flow from consent creation to receiving structured financial data.

1

Create a Consent Request

Your app calls Roopya’s API specifying the customer’s identifiers, data types, purpose, and consent validity duration.

2

Customer Approves Consent

The customer gets a notification with a link to the AA’s consent approval page, authenticates via OTP, and approves or rejects.

3

Consent Status Notification

Roopya sends a webhook once the customer approves. The consent is now active.

4

Request Data Fetch

Your app calls the data fetch endpoint with the active consent ID; Roopya triggers the AA to request data from the FIP.

5

Receive Normalized Data

Roopya normalizes the raw ReBIT response into clean JSON, delivered via API response or webhook.

6

Process or Revoke

Your app processes the data; the customer can revoke consent anytime, and Roopya notifies you of expiry or revocation.

API Example: Creating a Consent Request

POST /v1/aa/consentPOST https://api.roopya.money/v1/aa/consent Authorization: Bearer <YOUR_API_KEY> Content-Type: application/json { “customer_mobile”: “+919876543210”, “purpose”: “loan_underwriting”, “data_types”: [“transactions”, “profile”], “fip_ids”: [“HDFC”, “ICICI”], “fetch_type”: “periodic”, “from_date”: “2026-02-23T00:00:00Z”, “to_date”: “2026-08-23T00:00:00Z”, “consent_expiry”: “2026-08-24T00:00:00Z”, “webhook_url”: “https://yourapp.com/webhooks/aa” } // Response { “consent_id”: “cnst_7f3a9b2e1d”, “status”: “pending_customer_approval”, “consent_approval_url”: “https://aa.roopya.money/approve/cnst_7f3a9b2e1d”, “aa_provider”: “finvu”, “created_at”: “2026-08-23T10:15:30Z” }

API Example: Fetching Financial Data

POST /v1/aa/data/fetchPOST https://api.roopya.money/v1/aa/data/fetch Authorization: Bearer <YOUR_API_KEY> Content-Type: application/json { “consent_id”: “cnst_7f3a9b2e1d” } // Response (normalized by Roopya) { “consent_id”: “cnst_7f3a9b2e1d”, “status”: “success”, “accounts”: [ { “account_reference”: “HDFC-XXXX1234”, “fip_id”: “HDFC”, “account_type”: “SAVINGS”, “profile”: { “holder_name”: “RAHUL SHARMA”, “account_number_masked”: “XXXXXX1234”, “ifsc”: “HDFC0001234” }, “transactions”: [ { “date”: “2026-08-15”, “amount”: 45000.00, “type”: “CREDIT”, “narration”: “SALARY ACME CORP”, “balance_after”: 82340.50 } ] } ] }

What Data Is Received and in What Format

The AA framework the ReBIT standard — a structured XML/JSON schema. Roopya normalizes it into clean, consistent JSON regardless of source AA or FIP.

Bank Transactions

Transaction DateISO 8601
Amountdecimal
TypeCREDIT/DEBIT
ModeUPI/NEFT/IMPS

Account Profile

Account TypeSAVINGS/CURRENT
Holder Namestring
IFSC Codestring
Current Balancedecimal

Fixed & Recurring Deposits

Deposit TypeFD/RD
Principaldecimal
Maturity DateISO 8601
StatusACTIVE/CLOSED

Mutual Fund Holdings

Scheme Namestring
Units Helddecimal
Current NAVdecimal
Scheme TypeEQUITY/DEBT

Insurance Policies

Policy TypeTERM/ULIP
Sum Assureddecimal
Premiumdecimal
StatusACTIVE/LAPSED

SIP & Recurring Investments

SIP Amountdecimal
FrequencyMONTHLY
Total Investeddecimal
Current Valuedecimal

Cost Comparison: Direct AA Integration vs. Roopya

A transparent breakdown of what it costs to access AA data directly versus through Roopya’s unified API.

Cost ComponentDirect AA IntegrationRoopya Unified AA API
One-time Setup FeeRs. 50,000 – Rs. 2,00,000 per AAZero
Integration Time4–8 weeks per AA1–2 days
Per Consent RequestRs. 10 – Rs. 25Included
Per Data FetchRs. 2 – Rs. 5Rs. 15 per successful fetch
Multi-AA RoutingSeparate integration per AABuilt-in, automatic
Data NormalizationBuild your own parserIncluded
Consent UIBuild your ownHosted, included
Engineering Team Required2–4 developers, 4–8 weeksNone — API-first

Direct AA Integration

Rs. 2L+
setup + ongoing dev costs
  • Rs. 50K–2L setup per AA
  • 4–8 weeks to go live
  • Ongoing maintenance burden

Who Benefits from the AA Framework

FIU

NBFCs & Lenders

Pull verified bank transaction data into your underwriting engine — assess cashflow, detect EMIs, estimate income.

Customer

Small Businesses

Share bank statement data securely in minutes — no printing statements or emailing PDFs.

FIU

Wealth Managers

A consolidated view of a client’s accounts, funds, deposits, and insurance with a single consent.

FIU

Personal Finance Apps

Offer a unified view of user finances across all linked accounts, powered by verified data.

Frequently Asked Questions

An RBI-regulated entity that securely shares your financial data from your bank to a lender or app — only with your explicit, time-bound consent. Think of it as UPI for financial data.

Yes. The AA never stores your data — it’s a conduit that passes data only when a valid, signed consent is active. You control what’s shared, with whom, and for how long, and can revoke access anytime.

Direct integration means separate onboarding with 3–6 AAs, each with its own spec — 4–8 weeks of work. Roopya gives you one unified API: we route requests, manage consent, fetch data, and normalize it. Live in 1–2 days.

Bank account profiles, transaction histories, fixed/recurring deposits, mutual fund holdings, insurance policy summaries, and SIP details — coverage depends on which FIPs the customer’s institutions connect to.

Typically 30 seconds to 2 minutes if their bank is already linked to the AA. New users need 1–2 minutes per bank to link first.

Rs. 15 per successful data fetch, zero setup fee, no minimum commitment. No charge for consent creation, status checks, or failed fetches.

Yes, at any time through the AA’s app or website. Roopya sends a webhook when consent is revoked or expires so you can handle data deletion.

Over 1,100 institutions as of 2026, including all major public and private banks, NBFCs, cooperative banks, mutual fund houses, and insurers. Coverage keeps expanding.

Ready to Add AA-Based Bank Data to Your Lending Flow?

Go live with Roopya’s unified Account Aggregator API in 1–2 days.