Getting a structured feed of a Bibit user's mutual fund, SBN and equity positions

One Bibit login sits over three settled ledgers — curated mutual funds, government securities (ORI, SBR, ST, SR and FR bonds), and an equities book cleared through Stockbit Sekuritas — held server-side under the APERD permit OJK records for PT Bibit Tumbuh Bersama. None of that lives on the phone. A unified read has to reach the registered owner's position and movement records and put three differently-regulated books into one shape. That join is the work, and it is work this desk does end to end: you name the app and what you need out of it, and a runnable integration comes back.

The four ledgers behind one Bibit login

Bibit labels its surfaces the way an Indonesian retail investor sees them. The table maps each to where it originates and what an integrator does with it.

Authorized ways into a Bibit user's holdings

Three routes genuinely apply here. They differ in coverage and in how durable the feed stays.

1. KSEI AKSes consolidated read (user-consented)

PT Kustodian Sentral Efek Indonesia runs an investor-facing facility at akses.ksei.co.id that lets the registered owner see securities ownership and mutations held in C-BEST against their Single Investor Identification, refreshed for roughly the last 30 days per KSEI's own description. Because a Bibit user already has a Sub Securities Account, this is a documented, owner-consented view that spans mutual fund units, SBN and equities at once. We set up the consent and access with the account holder during onboarding and build the read against it.

2. Authorized interface integration of the Bibit app

Protocol analysis of the app's own traffic under the customer's authorization reaches what AKSes does not: robo-advisor target weights, goal pockets, the equity Playlist, RDN cash state and in-app order status. This is reverse engineering for interoperability — the login and token chain, then the portfolio and history surfaces. Most exposed of the three to front-end change, which we plan for.

3. User-consented credential access plus native statements

With a consenting account holder, the same surfaces can be driven from a live session, and KSEI / custodian periodic statements give a reconciliation baseline. Useful as a fallback and a cross-check rather than a primary feed.

For most buyers the workable shape is route 1 as the consolidated, regulator-backed backbone, with route 2 layered on for the Bibit-only fields AKSes never carries. We say which mix fits once we see what you need out of the data.

A portfolio read, sketched

Illustrative only and confirmed against live shapes during a build — field names are normalized, not lifted from any contract. The pattern is: establish a session, pull the Bibit-side portfolio, then reconcile against an AKSes consolidated snapshot.

POST /auth/session            # phone + PIN, then OTP challenge
  -> { access_token, refresh_token, sid }

GET  /portfolio/summary       # Bearer access_token
  -> { reksadana: { nav_total, funds:[{ fund_id, units,
                     nav, cost_basis, manager, custodian }] },
       sbn:        [{ series, type:"ORI|SBR|ST|SR|FR",
                     nominal, coupon_rate, maturity, syariah }],
       saham:      { equity_value, positions:[{ ticker,
                     lots, avg_price, mkt_value }] },
       rdn:        { bank:"Bank Jago", balance, value_date } }

# reconciliation: KSEI AKSes consolidated ownership by SID
GET  akses.ksei.co.id/holdings?sid={sid}   # owner-consented
  -> { instruments:[...], mutations_last_30d:[...] }

on 401  -> refresh_token rotation, single retry
on 429  -> respect Retry-After, backoff
join    -> key Bibit funds/SBN/equities + AKSes rows on SID

Errors matter as much as the happy path: token rotation, rate-limit backoff, and a settled-vs-pending distinction so an RDN top-up that has not value-dated does not look like a holdings discrepancy.

What lands at the end of the build

Each deliverable is tied to the surfaces above, not a generic checklist:

• An OpenAPI specification covering the portfolio, SBN, equity, RDN and transaction-history reads, plus the AKSes reconciliation call.
• A protocol and auth-flow report: the phone/PIN/OTP login, token rotation, and the session model used for the consented reads.
• Runnable source for the key endpoints in Python and Node.js, including the SID join that merges the three books.
• Automated tests covering NAV roll-up, SBN cashflow fields, value-dated RDN balance and the 401/429 paths.
• Interface documentation and a data-retention note aligned to UU PDP, with consent records and access logging.

Where it gets used

Three end-to-end shapes come up most:

• A wealth dashboard that folds a client's Bibit funds, SBN and Stockbit equities into one net-worth view refreshed daily.
• An advisory tool that ingests the risk profile and goal pockets to flag drift from target allocation.
• A tax and accounting workflow that pulls realized redemptions and SBN coupon income for annual filing.
• A lending check that verifies investable assets from a single owner-consented AKSes snapshot.

Consent and the rulebook this sits under

Bibit's products are supervised by OJK, with PT Bibit Tumbuh Bersama carrying an APERD permit (code BTB69 on OJK's public reksadana register). Securities ownership is recorded centrally by KSEI; retail SBN runs through the Ministry of Finance distribution-partner framework. Personal data is governed by Indonesia's Personal Data Protection Law, UU No. 27/2022, whose sanctions became enforceable from October 2024 per legal commentary; personal financial data is treated as a specific category requiring explicit consent. The funding rail touches Bank Indonesia's SNAP payment-API standard, released in 2021, where the RDN top-up moves through Bank Jago. Every route we run is owner-consented or customer-authorized, with consent scope recorded, revocation honored, access logged, data minimized to what the integration needs, and an NDA in place where the work requires it.

Engineering realities we plan around

Two judgments shape every Bibit build:

• Three licensed entities, one investor. Mutual funds (APERD), retail SBN (Ministry of Finance distribution partner) and equities (Stockbit Sekuritas) are separate books. We map all three onto the investor's SID so the unified feed reconciles instead of triple-counting or dropping a sleeve.
• The AKSes window rolls. KSEI exposes mutations for roughly the last 30 days. We design the sync cadence around that window so movement history is captured before it ages out, and reconstruct deeper history from the consented app session.
• RDN value-dating. Per Bank Jago's RDN documentation, top-ups after the evening cut-off land the next morning. We model the RDN as its own value-dated ledger so cash and settled holdings never read as inconsistent.

Access, the consenting account and any sandbox are arranged with you as part of onboarding — that setup is our step in the project, not something you clear before we begin.

How often this actually moves

Mutual fund valuations update once per day off published NAV. SBN series carry mostly static terms with periodic coupon events. Equities move intraday during IDX trading hours. AKSes reflects ownership and the trailing 30-day mutation set. RDN balances shift on top-up and withdrawal with value-dating. We set each sleeve's refresh cadence to its real change rate rather than polling everything on one clock.

Engagement and cost

A Bibit integration ships as runnable source for the portfolio, SBN, equity, RDN and AKSes-reconciliation surfaces within a one to two week cycle. Source-code delivery starts at $300: you receive the API specification, the runnable endpoints, tests and interface documentation, and you pay only after delivery once the integration satisfies you. The alternative is a hosted API you call on a pay-per-call basis with no upfront fee. Same surfaces either way; the choice is whether you run the code or we host it. Tell us the app and what you want out of its data on the contact page and we will scope the route.

Screens from the app

Store screenshots, shown as a reference for the surfaces described above.

How this brief was built

Compiled from the app's own store description and from primary sources opened during research in May 2026: OJK's public reksadana register for the APERD permit, KSEI's AKSes facility documentation for the consolidated-ownership read, the Ministry of Finance DJPPR retail-SBN page for the distribution-partner framework, and Bank Indonesia's SNAP standard for the payment rail. Where a detail was not publicly disclosed it is not asserted here.

• OJK reksadana register — APERD permit (BTB69)
• KSEI — AKSes facility
• DJPPR Kemenkeu — retail SBN
• Bank Indonesia — SNAP open API standard

OpenBanking Studio integration desk · mapping reviewed May 2026.

Other Indonesian investing apps in the same picture

A unified feed rarely stops at one app; clients usually consolidate across several. Named here for context, not ranked:

• Bareksa — mutual fund and SBN marketplace; holds per-user fund positions and government-bond orders.
• Ajaib — mutual funds and equities in one account; holds portfolio and order history.
• Pluang — multi-asset (US stocks, crypto, gold, mutual funds); per-user balances across classes.
• Stockbit — equities and community research, affiliated with Bibit; holds the brokerage book and watchlists.
• IPOT (Indo Premier Sekuritas) — long-running broker app; holds equity, fund and bond positions.
• Tanamduit — mutual funds, SBN and insurance; per-user fund and bond holdings.
• Bions (BNI Sekuritas) — bank-linked brokerage; holds equity positions and RDN data.
• MOST (Mandiri Sekuritas) — brokerage app with SBN distribution; holds equity and bond positions.

Questions integrators ask about Bibit

Does KSEI AKSes show the same holdings a user sees inside Bibit?

AKSes consolidates securities ownership held in KSEI's C-BEST system against the investor's Single Investor Identification, covering mutual fund units, SBN and equities with mutations for roughly the last 30 days. Bibit-specific layers such as robo-advisor target allocations, goal pockets and the stock Playlist are not in AKSes, so we read those from the consenting app session and reconcile both into one feed.

Bibit splits funds, SBN and stocks across different licensed entities. Does that complicate a unified feed?

Mutual funds sit under PT Bibit Tumbuh Bersama's APERD permit, retail SBN under the Ministry of Finance distribution-partner framework, and equities clear through Stockbit Sekuritas. We normalize the three into one schema keyed on the investor's SID so a downstream system sees a single portfolio rather than three disconnected books.

Is the RDN cash balance reachable, and which bank holds it?

The Rekening Dana Nasabah is a separate bank account; Bibit operates it with Bank Jago, including a Shariah RDN variant. Its balance and top-up or withdrawal movements are a distinct surface from securities holdings, with value-dating rules, so we map it as its own ledger instead of folding it into position data.

If Bibit ships an app update, does the integration break?

Portfolio and order surfaces can shift between releases. We ship a re-validation suite keyed to Bibit's response shapes and re-test against new versions as they ship, with the consolidated AKSes path kept as a stable fallback. A build turnaround is one to two weeks.