Finvu

What is Finvu?

If you have ever applied for a personal loan, a credit card, or a wealth-management onboarding in India, you know the friction. The user has to download six months of PDF bank statements from their HDFC/SBI/Axis net-banking portal, manually upload them, and wait for a third-party OCR engine to parse the text. The process is slow, prone to OCR error, vulnerable to PDF forgery, and creates a regulatory headache for the receiving fintech. Finvu eliminates this entire workflow.

Finvu operates under the RBI's Account Aggregator (AA) framework, a 2016 regulatory innovation (operationalised from 2021) that defines three roles: FIP (Financial Information Provider) — the bank or mutual-fund registrar that holds the data; FIU (Financial Information User) — your lending or wealth app that wants the data; and the AA itself — a regulated NBFC that routes consent and encrypted data between FIP and FIU and is legally prohibited from reading or storing the data in plaintext. When your end user grants consent on Finvu's RBI-mandated consent screen, Finvu fetches their cryptographically signed FI block from the FIP and delivers it encrypted to your backend, where only your private key can decrypt it.

The Sahamati ecosystem. Finvu is part of the Sahamati collective — the industry body that runs the AA ecosystem standards. As of 2026 there are 13+ RBI-licensed NBFC-AAs, of which Finvu, Setu (Pine Labs), CAMS Finserv, OneMoney, Anumati (Perfios), Saafe (NeSL), and a handful of others are the operationally significant players. The category is consolidating around the top 5–6 names by FIU+FIP-volume; Finvu is consistently in that top tier.

The 2025 rebrand. A subtle but important detail: the parent legal entity was renamed in 2025 from Cookiejar Technologies Private Limited to Finfactor Technologies Private Limited. Several public funding-announcement headlines actually credit "Finfactor" rather than "Finvu" — same company, new legal name. The consumer brand stays "Finvu." For procurement, expect your master services agreement to be with Finfactor Technologies Pvt Ltd.

Why Account Aggregator matters in 2026. Three regulatory currents converge: (1) the DPDPA 2023 data-protection framework codifies consent-first data handling — AA is the legally-blessed implementation; (2) RBI digital lending guidelines increasingly disfavour PDF-based income verification on regulated lenders; (3) the Unified Lending Interface (ULI) rollout from RBI in 2024–2026 leans heavily on AA rails. For any Indian lending or wealth-tech build in 2026, an AA integration is no longer optional; the question is which AA.

Capabilities

Pricing (2026, Best-Available)

Finvu uses negotiated enterprise pricing — no public rate card. Figures below are typical market-rate ranges per multiple Sahamati-ecosystem advisory reports and FIU procurement sources. Excludes 18% GST and any pass-through charges levied by the FIP banks themselves (banks now charge FIPs per fetch on certain data types; some FIPs in turn pass-through to AAs).

When Finvu Is the Right Call

1. Indian lending platforms (NBFC / digital lender / co-lending stack) needing forgery-proof income verification. Forge-proof bank-statement data via AA is now the table-stakes input for underwriting; HDFC + Axis + Canara are on Finvu, which means most retail credit applicants are reachable.
2. Wealth and PFM apps needing aggregated net-worth views. Mutual fund holdings (CAMS + KFin), equity portfolios via depositories, insurance policies — Finvu offers the multi-FI-type FI fetches needed for one-screen net-worth views.
3. Insurance distributors and InsureTech platforms. AA-linked insurance policy data via NeSL flow gives a single-consent view of a customer's policy holdings — useful for cross-sell, claims pre-fill, and policy renewals.
4. Co-lending and partnership BFSI plays with banks. Anchor customers HDFC + Axis + Canara on the FIP side make Finvu a natural choice if your lending product runs as a co-lender with one of these names.
5. DPDPA-compliant data architectures. AA is the legally-blessed implementation of DPDPA's consent-first principle for financial data. Building on Finvu is materially easier to defend to your CISO/DPO than scraping or PDF-uploading.
6. FIU programmes wanting analytics, not just routing. Finvu's Series A use-of-funds is explicit about scaling the analytics suite; if you want a vendor moving toward analytics + insights on top of raw FI data, Finvu is the right bet.

When Finvu Is the Wrong Call

Pre-FIU-registration startups. Accessing the AA framework requires your company to be registered as an FIU with the relevant regulator (RBI for banks, SEBI for wealth, IRDAI for insurance). If you're pre-seed and not yet registered, no AA can onboard you. Need to move money, not just read data. Use Decentro, RazorpayX, or Cashfree for virtual accounts, UPI payouts, and BaaS — Finvu is strictly data, not money movement. Need a single API for both AA data and BaaS payments. Setu (now Pine Labs) is the natural pick because it bundles AA with payments in one developer relationship. Legacy NBFC needing PDF-parsing fallback for older customer cohorts. Perfios (Anumati) is the historical PDF-parsing leader; their AA story is also strong but they offer the rare combination of PDF + AA under one roof. Bank-side integration as a FIP first, FIU second. If your primary use case is acting as a FIP exposing your bank's data, the AA market has different commercial dynamics — talk to multiple AAs. International data residency where data should not touch Indian rails. The entire AA framework is RBI-jurisdictional and India-only. Need free, public-rate-card pricing for fast procurement. No AA in 2026 ships a public rate card — all are enterprise-negotiated.

First 5 Setup Steps for FIU Engineering Teams

1. Regulatory registration. Confirm your entity has the right regulatory standing — FIU registration with RBI (for banks/NBFC use cases), SEBI (for wealth), or IRDAI (for insurance). The AA ecosystem won't onboard without this.
2. Sahamati membership and Finvu sandbox. Register on the Sahamati participant list and request Finvu UAT (User Acceptance Testing) sandbox access. Sandbox simulates mock FIP responses for major banks and asset classes.
3. JWS (JSON Web Signatures) implementation. All API requests to Finvu must be cryptographically signed using JWS for non-repudiation. Your backend must securely manage private keys (use AWS KMS or Azure Key Vault on ap-south-1 Mumbai for DPDPA-clean key management).
4. Consent flow design. Implement the API calls that trigger the Finvu consent redirect (web + Android + iOS deep links). Handle the webhooks that notify your system when a user approves, rejects, or revokes a consent.
5. Decrypt-and-parse the FI block. Once consent is granted and data is fetched, implement decryption with your private key on your server, parse the FI block (typically JSON), and feed it into your underwriting / scoring / analytics pipeline.

Pros and Cons

Alternatives to Consider

Bottom line for Indian buyers

If you are building an Indian lending, wealth-tech, PFM, or insurance-distribution platform in 2026, an Account Aggregator integration is no longer optional — RBI digital-lending guidelines, the DPDPA, and the Unified Lending Interface have all converged on consent-based AA rails as the legally-clean way to get bank-statement, MF-holding, and policy data. Finvu is one of the top 5–6 NBFC-AAs by volume, has just raised a $15M Series A from WestBridge with HDFC/Axis/Motilal Oswal/Canara/CRED as anchor references, and is investing heavily in an analytics suite that goes beyond pure routing. The watchpoints are: pricing is opaque and the category is commoditising — always benchmark against Setu and Perfios before signing. The 2025 Cookiejar→Finfactor rebrand confuses contract paperwork; insist on clarity. The Indian AA category is where Indian fintech regulatory infrastructure meets engineering excellence, and Finvu is one of the strongest local-built operators on it.