OnGravy pulls every Indian bank transaction in via the RBI Account Aggregator framework. Setu, Perfios, and Finbox adapters are code-ready; the engineering is done — only the vendor agreement remains.
Each vendor below is a regulated AA-TSP (Technical Service Provider) under the RBI framework. We're onboarding all three so production never depends on a single provider.
Adapter code is ready. Vendor agreement is in legal review.
Full RBI Account Aggregator framework — all FIPs onboarded with Sahamati. Setu is part of Pine Labs and the most-onboarded AA-TSP in India.
setu.co ↗Adapter code is ready. Vendor agreement is in legal review.
Bank statement analytics + AA fetch. Strong for lender-grade analysis; coverage extends to NBFC + co-op bank FIPs.
perfios.com ↗Adapter code is ready. Vendor agreement is in legal review.
AA aggregator + alt-data scoring. Useful when the same connection feeds underwriting (working-capital lending downstream).
finbox.in ↗AA + aggregator route is industry standard; we won't ship bank-specific direct integrations.
Direct APIs each require their own onboarding + IP-whitelisting + corporate-treasury contract. The AA framework collapses all of them into one consent flow.
The AA framework is what makes one-consent-many-banks possible. A short primer.
AA is an RBI-regulated consent layer that lets you grant a regulated data consumer (OnGravy via our chosen AA-TSP) read-only access to your bank, credit-card, and term-deposit accounts across all participating Indian banks — without sharing your net-banking password. Consent is granular (date range + data types) and revocable.
Two reasons. First, AA is the only RBI-blessed path: direct API access for non-banks needs a corporate-treasury contract per bank, which doesn't scale across 80+ FIPs. Second, the aggregator handles the FIU / FIP messaging spec so we focus on accounting workflows rather than rebuilding signed-XML parsers for every bank.
OnGravy operates as a sub-FIU through our chosen AA-TSP (Setu / Perfios / Finbox), which is the standard model for fintech-adjacent products. The TSP holds the regulated FIU registration; we consume their API. This means your consent goes to the TSP, with OnGravy named as the downstream data consumer.
The day the vendor contract closes. Engineering is done — the adapter contract, the registry, and the reconciliation engine are already shipped (see lib/banking/bank-feed/). We flip a single env var (SETU_LIVE=true, etc.) and the registry swaps in the real adapter.
Out of scope for the AA framework, which is India-only. For US / UK / UAE clients we currently rely on CSV import (HDFC-style statement parser handles most banks) and on Plaid for US accounts via lib/banking/aa/vendors/plaid.ts. Plaid is wired but not yet productionised.
Drop your email and we'll ping you the day a vendor contract closes and bank feeds flip live. You'll be one of the first 100 to onboard — same week, not next quarter.