Reaching Bachatt's fund folios, SIP mandates and loan records through consented data flows

A Bachatt account is, underneath, a set of mutual-fund folios stitched to a UPI autopay engine. Insta Fund is a SEBI-regulated liquid scheme with instant UPI-style withdrawal; the curated baskets are regular plans from AMCs the app names — SBI, ICICI Prudential, Axis, HDFC and others — funded by daily, weekly or monthly SIPs from as little as ₹20–₹51 a day, as the listing describes it. On top of that sits a personal-loan account routed through an RBI-registered NBFC. Three different data shapes, three different homes.

The route that survives is the investor's own consent. In September 2025 AMFI directed MF Central to stop handing investor data straight to third-party apps (reported by Business Standard), which closed the OTP tap several guided-investment apps had leaned on. What stays open is the RBI Account Aggregator network, where the CAMS and KFin RTAs are live as Financial Information Providers. We build to that consent artefact and read the app-side surfaces under the same authorization. Below is what each surface holds and how we'd wire it.

The data Bachatt actually keeps

How we get in

Account Aggregator consent (the spine of this one)

The investor approves a consent through a licensed AA; CAMS and KFin, as FIPs, return folio holdings and transactions as signed ReBIT data. Reachable: the full MF picture across AMCs in one normalized shape. Effort is moderate and front-loaded into the consent design; durability is high because it rests on regulated, revocable authorization rather than a private endpoint. We arrange the AA linkage and the FIU-side handling with you during onboarding.

Authorized protocol analysis of the app

For surfaces the MF schema doesn't carry — SIP scheduling, autopay mandate state, the loan EMI table — we analyse the app's own traffic under your authorization and document the auth chain and request/response fields. This is the route for the daily-savings mechanics that make Bachatt distinct from a plain folio.

User-consented session access

Where a one-off backfill is needed, a consenting account holder can authorize a session capture so we map exact payloads once and codify them. Used to confirm field meanings, not as a standing feed.

For a wealth or lending integrator, the consented AA pull carries the regulated investment data and should anchor the build; the protocol-analysis work fills the daily-savings and loan gaps the AA schema was never meant to express. We'd recommend starting there and treating the app-side capture as the companion that completes the picture.

A consented fetch, sketched

Illustrative only — exact field names are confirmed against the live ReBIT response during the build. The flow requests a mutual-fund summary against an active consent handle, then folds in the app-side SIP record.

POST /AA/FI/fetch
Authorization: Bearer <fiu-session-token>
Content-Type: application/json

{
  "consentId": "c-9f21...",          // revocable, investor-granted
  "fiTypes": ["MUTUAL_FUNDS"],
  "dataRange": {"from": "2026-04-01", "to": "2026-06-24"}
}

# Normalized response (illustrative)
{
  "folios": [
    {
      "amc": "ICICI Prudential",
      "scheme": "Liquid Fund - Insta",     // SEBI Instant Access Facility
      "units": 412.553,
      "navDate": "2026-06-24",             // same-day if placed before 13:30 IST
      "nav": 100.41,
      "value": 41423.0,
      "instantRedeemHeadroom": 50000        // AMC per-day cap, modelled separately
    }
  ],
  "sips": [                                 // from app-side surface, labelled non-FIP
    {"scheme": "Insta", "amount": 51, "freq": "DAILY", "nextDebit": "2026-06-25"}
  ]
}

# Handle a stale or revoked consent before trusting any of it
if resp.status == 403 and resp.error == "CONSENT_EXPIRED":
    trigger_reconsent(consentId)

What lands in your repo

Each engagement ships runnable code and the documents to operate it, scoped to Bachatt's real surfaces:

• An OpenAPI/Swagger spec covering the normalized holdings, SIP, transaction and loan objects.
• A protocol and auth-flow report: the AA consent handshake plus the token and session chain for the app-side surfaces.
• Runnable source for the key calls in Python and Node.js — folio fetch, transaction pull, SIP read, loan-schedule parse.
• Automated tests, including a fixture for the expired-consent and re-consent path.
• Interface documentation and data-retention guidance keyed to AA consent scope and the SEBI distributor context.

Consent and the rules that bind it

This is RBI Account Aggregator territory, regulated by the Reserve Bank, with SEBI standing behind the mutual-fund data itself. Under the AA framework no FI data moves without the investor's explicit, granular, revocable consent — a signed artefact, not a blanket OTP grab, which is precisely the practice AMFI moved against in 2025. Consent carries a purpose, a data range and an expiry; we design the sync so it honours that window and re-prompts rather than silently failing when it lapses. Bachatt itself operates as an AMFI-registered distributor (ARN-321640 per its listing) and is not an adviser, so the integration stays on the data-portability side and never implies advice. We work authorized and logged, minimize what we pull, and sign an NDA where the engagement needs one.

Things we handle on this build

• We stamp every unit balance with its effective NAV date around the 1:30 PM cut-off, so a snapshot taken at 2 PM isn't mislabelled with a NAV that won't apply until the next session.
• We model Insta Fund's liquid-scheme redemption — instant, capped per day under SEBI's Instant Access Facility — separately from the regular-plan baskets, because treating a long-term basket as same-day liquid is the kind of error that breaks a cash view.
• The Salora Capital loan record sits outside the AA mutual-fund schema; we reconcile EMI, tenure and processing-fee fields from the consented app surface and keep them clearly partitioned from regulated FIP data.
• When the app front end shifts, the app-side captures need a re-check; we fold that into maintenance so the SIP and loan readers don't drift after a release.

Pricing

Source delivery for Bachatt starts at $300, billed only after we hand over the working folio-and-SIP integration and you've run it and signed off. If you'd rather not host anything, the alternative is our pay-per-call hosted API: you call our endpoints for the holdings, transaction and loan objects and pay only for the calls, with no upfront fee. Either way the cycle is one to two weeks. Tell us the app and what you need from its data, and access plus compliance get arranged with you as part of the work — start a project.

Where teams use this

• A lending platform reading consented folio value to size a loan-against-mutual-funds offer without screen-scraping.
• A personal-finance app folding a user's daily Insta Fund balance into a single net-worth view alongside bank data.
• An advisory desk importing SIP cadence and XIRR to flag where a regular-plan basket is dragging versus its direct equivalent.
• An accounting tool pulling redemption history for capital-gains statements at year end.

App screens

From the public store listing — useful for reading how the dashboard groups savings, holdings and loans before we map the surfaces.

How this was checked

Mapped against the app's public Google Play and Apple App Store listings for the product surfaces and the ARN-321640 distributor detail, the RBI/government Account Aggregator documentation for the consent model and FIP roles, industry reporting on CAMS/KFin RTA availability over the AA network, and Business Standard's September 2025 report on the MF Central data-sharing directive. Sources opened:

• Business Standard — AMFI asks MF Central to stop sharing investor data with third-party apps
• Dept. of Financial Services — Account Aggregator framework
• CDSL — Financial Information Provider (FIP) under AA
• Bachatt — Google Play listing

Mapped by the OpenBanking Studio integration desk, June 2026.

Apps in the same neighbourhood

Same daily-savings and micro-investing category in India; an integrator weighing a unified data layer usually looks across several at once.

• Jar — rounds up spends into digital gold; holds a per-user gold ledger and recurring-saving mandates.
• Fello — game-led saving across a flexible pot and digital gold, with reward-state alongside holdings.
• NiyoX — a banking-plus-savings account with daily balances and card transactions.
• Gullak — automated micro-savings into gold and fund products with goal tracking.
• Deciml — round-up and daily SIP into mutual funds; holds folio and contribution data much like Bachatt.
• Pyllar Money — daily SIP from a low minimum, AMFI-registered, with per-user fund holdings.
• Fi Money — a neobank app holding accounts, deposits and mutual-fund investments in one view.
• Jupiter — spending account plus investment pots, with transaction and holdings data per user.

Questions integrators ask

Which Bachatt data moves through the Account Aggregator network, and which does not?

Mutual-fund folios — units, scheme, current value, transaction history — flow as ReBIT-structured FI data from the CAMS and KFintech RTAs acting as Financial Information Providers. The in-app SIP configuration, the UPI autopay mandate state and the Salora Capital loan schedule are not part of the regulated MF schema; we read those from the consented in-app surface and label them separately so an integrator never confuses an FIP record with an app-side one.

After AMFI restricted MF Central data sharing in September 2025, what is the durable way into Bachatt's fund data?

The OTP-based MF Central route that several guided-investment apps relied on was directed to stop, per Business Standard's September 2025 report. The standing path is the investor's own consent through the RBI Account Aggregator network, where CAMS and KFin RTAs are live as FIPs. We build against that consent artefact, so the integration rides the investor's revocable authorization rather than a third-party data tap that can be switched off.

Can you separate the liquid Insta Fund balance from the long-term SIP baskets?

Yes, at scheme level. Insta Fund maps to a liquid scheme under SEBI's Instant Access Facility with a per-day instant-redemption cap; the curated baskets are regular-plan equity and hybrid schemes with normal T+1 to T+3 redemption. We model the two with distinct redemption semantics so a downstream cash-management view does not treat a locked-in basket as same-day liquid.

How current is the holdings snapshot you would hand back?

Purchases placed before the 1:30 PM cut-off get same-day NAV per AMC rules, so we stamp each unit balance with its effective NAV date rather than the wall-clock fetch time. AA pulls can be scheduled or consent-triggered; for a daily-SIP app a once-a-day post-allotment pull usually matches how the underlying RTA data actually settles.