Getting investor records out of the Mirae Asset Mutual Fund app

A Mirae Asset folio changes shape the moment a SIP debit clears, a redemption settles, or a switch goes through. Most teams that want to integrate this app do not want to re-download a statement every morning to notice that — they want those moves to land as events. The app itself, marketed as a paperless way to invest using PAN, email and mobile number (as its store listing describes onboarding), keeps the records that make those events worth catching: per-folio holdings, live SIP mandates, a transaction history, and goals tagged to investments. This page maps what is in there and the authorized ways to read it for an Indian mutual-fund data set.

Investor records the app keeps

Each row below is a surface the app actually exposes to a logged-in investor, mapped to where it originates and what an integrator typically builds on it.

Authorized ways in

Three routes carry real weight for this app; which one leads depends on whether you only need to read holdings or also need to act on them.

Account Aggregator consent (SEBI-side FIPs)

India's Account Aggregator framework, run under the RBI's NBFC-AA Master Direction, moves financial data between regulated entities only on the customer's explicit consent. SEBI's August 2022 circular brought its registered entities in as financial information providers, and the registrar-and-transfer agents that service mutual funds — CAMS and KFintech — sit on the supply side. Reachable: consented holdings, valuation and transactions. Effort is medium; durability is high because the ReBIT API contract and Sahamati interoperability are standardized. We handle the FIU-side onboarding and the consent artefact with you during the project.

Authorized interface integration of transact@ease

The transact@ease portal and the app share the same backend, with OTP issued against the registered mobile and email for redemptions and switches. Under the customer's authorization, we capture and map that traffic against a consenting account to reach everything the user sees, including per-folio SIP controls and the CART flow. Effort is medium to high because the session is OTP-gated and the surface evolves; durability is medium and maintained by re-validation. This is the route that supports write actions.

Consolidated statement / RTA export

The CAMS-and-KFintech consolidated account statement gives a cross-fund-house view of holdings and transactions and works well as a backfill source. Note the live constraint here: in September 2025, Business Standard reported AMFI asked MF Central to stop sharing investor data with third-party apps over OTP-based access. So we treat the consolidated statement as a parse-and-reconcile input under the investor's own authorization, not as an informal third-party pull. For most builds we recommend the AA route as the durable read spine and bolt interface integration onto it where you need richer state or to place transactions.

What you get back

The headline deliverable is code that runs against this app's surfaces, not a document describing it.

• Runnable connector source in Python and Node.js for the folio, holdings and transaction reads, including the OTP session handling for the interface route.
• A webhook layer that emits normalized push events — sip.debit.settled, redemption.settled, switch.completed, holding.revalued — so your stack reacts to folio changes instead of polling.
• An automated test suite with recorded fixtures and contract tests run against a consenting account or an AA sandbox, so a changed field is caught at build time.
• A normalized schema mapping Mirae Asset folios, schemes, units and NAV into a cross-AMC model you can extend to other fund houses.
• Secondary, and included: an OpenAPI description of the connector surface, an auth-flow write-up of the OTP and consent chain, data-retention guidance, and interface documentation your own engineers can maintain.

A connector sketch

Illustrative, and confirmed in shape during a build — the watcher reads the consented feed, diffs against last-seen state, and posts a normalized event. Field names and masking are finalized against the live payload.

# watcher: turn a consented Mirae Asset read into push events
state = load_last_seen(folio_set)                  # per folio+scheme cursor
snap  = aa_pull(consent_ref) or portal_read(session)  # AA first, interface fallback

for folio in snap.folios:
    for scheme in folio.schemes:
        prev = state.get((folio.id, scheme.code))
        if prev is None or scheme.units != prev.units:
            emit({
              "event": classify(prev, scheme),       # sip.debit.settled / redemption.settled / switch.completed
              "folio": mask(folio.id),               # never log the raw folio
              "scheme": scheme.name,                  # e.g. "Mirae Asset Large Cap Fund - Direct - Growth"
              "amount_inr": scheme.value_inr,
              "nav": scheme.nav,                      # last AMFI-published NAV
              "units": scheme.units,
              "value_date": scheme.value_date,
              "source": snap.source,                  # "aa_pull" or "portal"
              "consent_ref": consent_ref
            })
        state[(folio.id, scheme.code)] = scheme

# events post to your endpoint, keyed on (folio, scheme, value_date) for safe replays

Where teams plug this in

• A neobank showing a member's full net worth pulls consented Mirae Asset holdings, revalues them on the daily NAV, and takes a webhook on every transaction so the balance is never stale.
• An advisory product watches SIP mandate health through the interface route and raises a flag the moment a debit bounces or an investor pauses a plan.
• A tax tool ingests the transaction and switch history to compute realized short- and long-term gains across an investor's folios at filing time.

Consent and the SEBI rails

Mutual funds in India are regulated by SEBI; the data-sharing rail is the RBI's Account Aggregator framework, with ReBIT-defined APIs and Sahamati as the ecosystem alliance. Consent under AA is explicit, scoped to named data and a stated purpose, time-bound, and revocable by the investor at any point — nothing moves without it. On the personal-data side, India's DPDP Act, 2023 frames how identity fields such as a PAN-linked record are handled. Our posture is plain: authorized or user-consented access only, consent and access logged, payloads minimized to what the use case needs, folio identifiers masked in transit and logs, and an NDA where the engagement calls for one.

What we account for in the build

Two details about this app shape the connector, and we design around them rather than hand them to you as hurdles.

• NAV is once a day. Units revalue against the AMFI-published end-of-day NAV, so a "current value" is the last published NAV plus any pending order state. We model both, so a dashboard built on this never implies intraday pricing it cannot truthfully show.
• Consent has a validity window. An AA consent is granted for a fixed period; the connector tracks that window and queues a renewal request before it lapses, so a long-running sync is never left holding a dead consent.
• Same scheme, many folios. An investor can hold one scheme across several folios; we de-duplicate at the folio-plus-scheme grain so totals are not double-counted.
• OTP-gated sessions. transact@ease issues an OTP for redemptions and switches; we handle that session lifecycle with a consenting account while building, and document it so your team can run it.

Cost and how it runs

Source delivery starts at $300, and you pay it after the code is in your hands and working — runnable connector, webhook layer, tests and the interface docs for this app, on a one-to-two-week cycle. If you would rather not run anything yourself, the same integration is available as a hosted endpoint you call and pay per call, with no upfront fee. You bring the app name and what you want from its data; access, consent and any compliance paperwork are arranged together as part of the work. Tell us which Mirae Asset surfaces you need and we will scope it — start a conversation here.

How this brief was put together

Checked on 14 June 2026 against the app's own description and store listing, Mirae Asset's transact@ease platform notes, SEBI's circular on financial information providers in the Account Aggregator framework, the CAMS consolidated-account-statement documentation, and recent reporting on the MF Central data-sharing question. Sources opened:

• SEBI — Participation as Financial Information Providers in the Account Aggregator framework (Aug 2022)
• Business Standard — AMFI asks MF Central to stop sharing investor data with third-party apps (Sept 2025)
• CAMS — Consolidated Account Statement
• Mirae Asset Mutual Fund — investor app overview

OpenFinance Lab — interface mapping · 2026-06-14

Apps in the same data orbit

These Indian platforms hold comparable mutual-fund records and tend to show up when a single integration has to read across more than one source.

• Groww — direct mutual funds plus stocks and gold; holds per-user folios, SIPs and order history.
• Zerodha Coin — direct mutual funds tied to a demat account, so positions sync against broking records.
• Kuvera — zero-commission direct plans with goal-based tracking across folios.
• ET Money — mutual funds alongside NPS and insurance, with consolidated portfolio views.
• Paytm Money — low-cost investing with SIP tracking and order records.
• Scripbox — curated portfolios and goal plans built on the investor's holdings.
• myCAMS — the CAMS investor app, with CAS-style holdings across CAMS-serviced funds.
• KFinKart — KFintech's investor app for portfolios and statements across its serviced funds.
• MF Central — the RTA-run common platform for cross-fund-house transactions and statements.

Screens we worked from

Store screenshots of the app surfaces referenced above. Tap to enlarge.

Questions integrators ask

Does the SIP and folio data arrive as live events or as a once-a-day file?

Both, and they serve different needs. Mutual fund units revalue once daily against the AMFI-published NAV, so the valuation side is end-of-day by nature; we reconcile that off the consolidated statement. The order side has a real lifecycle, so we wrap the consented feed in a watcher that pushes a webhook when a SIP debit settles, a redemption pays out, or a switch completes. You get the daily truth and the intraday state changes without polling the app yourself.

What route do you use when an Account Aggregator consent only returns read-only holdings?

The AA route through the SEBI-side financial information providers gives you consented holdings and transactions, which covers most dashboard and reconciliation use cases. When you need richer per-folio state or write actions such as placing or modifying a SIP, we add authorized interface integration against the transact@ease session with a consenting account. The two routes feed one normalized schema, so downstream code does not care which path a given field came from.

How does the September 2025 AMFI restriction on MF Central data sharing affect this build?

Business Standard reported in September 2025 that AMFI asked MF Central to stop sharing investor data with third-party apps over OTP-based access. We read that as a signal to keep the design on the regulated Account Aggregator consent rail and on directly authorized interface access rather than on any informal third-party pull from MF Central, so the integration sits on routes regulators are reinforcing, not curtailing.

Can Mirae Asset folios be normalized alongside holdings from other fund houses?

Yes. We map Mirae Asset folios, schemes, units and NAV-valued amounts into a cross-AMC model keyed at the folio-plus-scheme grain, de-duplicating the same scheme held across multiple folios. That lets a single investor view stitch Mirae Asset positions together with holdings reached the same way from other Indian fund houses.