What Tiền24 holds, and the authorized way to reach it

A 2,000,000 VND loan over 120 days, by the worked example in Tiền24's own Play listing, carries roughly 1,000 VND of interest a day and settles at about 2,120,000 VND at maturity. Numbers like that are not static — they are a daily accrual the app recomputes and shows back to the borrower. That recomputation, the application that produced it, and the bank account the money moves through are the records a partner, a collections desk, or a borrower's own finance tool would want to read out of this app.

Tiền24 (the listing reads "Tiền24-duyệt dễ") is a referral front end: it takes a borrower's request and routes it to cooperating P2P lending institutions, sometimes by recommending an in-app product, sometimes by sending the user into a partner's own app. So the integration question is less "what is the balance" and more "which records does Tiền24 itself hold, and how do we read them under a consent the borrower has given." This page lays out the data, the route, and what we hand over.

The records that actually live in this app

Rows below reflect the surfaces the app describes in its own sign-up flow and product detail, not a generic loan-app checklist. Granularity is what an integrator can realistically expect to read per borrower.

Three ways in, and the one we'd run

Authorized protocol analysis under borrower consent

The app talks to its backend over HTTPS to register a phone, submit an application, list partner products, and render the ledger. With a consenting borrower's account we observe and document those calls, then reimplement the ones that carry the records above. This reaches everything Tiền24 itself stores and is the route we would lead with, because the app's value to an integrator is exactly the borrower-specific application and ledger that only appear after phone-OTP sign-in.

Regulated data-sharing via the Vietnam sandbox

Decree 94/2025/ND-CP names data sharing through Open API as one of three sandbox solutions, alongside P2P lending and credit scoring. Where a Tiền24 operator or a partner institution holds a sandbox certificate, a sanctioned data-sharing channel is the durable long-run path. It depends on the counterparty's participation, which we confirm during onboarding rather than assume.

User-consented credential access

For a borrower who wants their own data moved — into a budgeting tool or a debt-advisor's dashboard — we run the same flows under that single user's credentials and consent. Narrow scope, fast to stand up, and it carries only that person's records.

The practical recommendation here is the first route. The records that make Tiền24 worth integrating are the per-borrower application and the daily ledger, both of which sit behind the authenticated app rather than in any shared feed, so reading the app's own traffic under consent is what reliably delivers them; the sandbox channel is worth pursuing in parallel when a partner already holds a certificate.

Auth and query shape

Illustrative, in the shape we would confirm during the build — phone-OTP sign-in to obtain a session token, then a ledger read keyed to the borrower's active loan. Field names stand in for what protocol analysis would pin down.

POST /api/v1/auth/otp/verify
{ "phone": "+849xxxxxxxx", "otp": "412208", "device_id": "..." }
-> 200 { "session_token": "ey...", "expires_in": 1800, "user_ref": "u_8842" }

GET /api/v1/loans/active?user_ref=u_8842
Authorization: Bearer ey...
-> 200 {
     "loan_ref": "ln_30194",
     "principal_vnd": 2000000,
     "term_days": 120,
     "daily_rate_pct": 0.05,          // ~18%/yr cap per listing
     "accrued_interest_vnd": 36000,   // dated: as of query date
     "overdue_penalty_vnd": 0,
     "payoff_vnd_today": 2036000,
     "partner_ref": "p_creditone"
   }

# session_token expires in ~30 min; refresh on 401 before retry
# all amounts re-read per query date — never cached as a static balance

What lands in your repo

Each deliverable is tied to a surface above, not a generic menu.

• OpenAPI / Swagger spec covering the auth, application, ledger and referral-event calls as observed, with the daily-accrual fields typed and documented.
• Auth-flow report for the phone-OTP and session-token chain — token lifetime, refresh behaviour, error codes — so your team can run it without re-deriving it.
• Runnable source in Python or Node.js for the key endpoints: OTP sign-in, active-loan read, application status, referral-event capture.
• Automated tests that assert the ledger math reconciles at a given date and that token refresh recovers from a 401.
• Normalized schema so a Tiền24 loan maps cleanly onto records from other lenders you integrate.
• Interface documentation plus data-retention and consent-handling guidance for the Vietnamese regime.

Consent and the Vietnamese rules that apply

The State Bank of Vietnam oversees this space. Decree 94/2025/ND-CP opened a two-year regulatory sandbox from 1 July 2025 covering P2P lending, credit scoring and Open API data sharing, with safeguards such as routing transactions through bank accounts or licensed e-wallets and drawing on National Credit Information Centre (CIC) data — context that shapes how a partner channel would be structured, per the DFDL and VILAF briefings we read.

Personal data sits under Decree 13/2023/ND-CP, in force since 1 July 2023, now elevated by the Personal Data Protection Law (91/2025/QH15) effective 1 January 2026. Both make prior, explicit, revocable consent the working basis for processing, and require that multiple purposes be listed separately. So the dependable footing for any Tiền24 integration is the borrower's own consent: we record it, scope capture to it, log access, data-minimize to the fields a use case needs, and work under NDA where a partner requires it.

Engineering notes we account for

Two things about this app shape the build, and we handle both on our side.

• The referral boundary. Tiền24 routes some borrowers into third-party lender apps. We map which fields the Tiền24 front end owns versus which are fetched live from a partner, and design capture to stop at the handoff — recording that a redirect fired without reaching into a separate app's consent scope.
• Daily accrual, not a stored balance. Interest and overdue penalty both accrue per day at ~0.05%, so a number that looks static changes overnight. We model the ledger as a dated series and stamp every read with its query date, so a synced figure matches the in-app view rather than going stale.
• OTP session lifetime. Sign-in is phone-OTP and the session is short-lived. We build the sync around that window with refresh-on-401, so a long-running job does not silently fall out of session mid-pull.

Where teams put this to work

• A partner P2P institution mirroring referred applications and their status into its own underwriting CRM.
• A collections or servicing desk reconciling daily payoff figures against what borrowers see in-app.
• A personal-finance tool pulling one consenting borrower's active loan into a unified debt view alongside other Vietnamese lenders.

Working with us

You bring the app name — Tiền24 — and what you want out of its data; we work out the route, arrange access with you, and deliver. There are two ways the commercial side runs. The first is source-code delivery from $300: you receive the runnable API source, the spec, tests and documentation, and you pay only after delivery once the integration satisfies you. The second is a pay-per-call hosted API: we host the endpoints and you pay per call, with no upfront fee. A typical build runs one to two weeks. Tell us which fits and what you need at /contact.html.

Interface shots

Screenshots from the Play listing, for reference on the surfaces named above.

How this was checked

I read the Google Play listing for com.hours.money for the data surfaces, the loan terms and the worked example, then the DFDL and VILAF briefings on Decree 94/2025 for the sandbox scope, and a Decree 13/2023 overview for the consent basis. Dates and numbers above are quoted as those sources state them. Checked June 2026 by the OpenBanking Studio integration desk.

• Tiền24-duyệt dễ on Google Play
• DFDL — Decree 94/2025 banking sandbox
• VILAF — Decree 94 sandbox for P2P lending and Open API
• Overview — Decree 13/2023 personal data protection

Similar apps in the same lending niche

Other Vietnamese consumer-loan and referral apps an integrator often unifies alongside Tiền24. Names are listed for ecosystem context only.

• MoneyCat — short-term online loans; holds per-user applications and repayment schedules.
• Cashspace — quick CCCD-based loans; per-borrower application and disbursement records.
• Jeff — loan-marketplace front end matching users to lender offers.
• Tamo — installment loans with an account-held repayment ledger.
• Takomo — fast-disbursement lender with per-user loan state.
• Doctor Đồng — small short-term loans, account-based history.
• Dong247 — automated-approval loan app with per-application records.
• Home Credit — consumer-finance lender with statements and installment ledgers.
• Touch (Mirae Asset Finance Vietnam) — consumer-finance app holding loan and repayment data.
• TiềnTay 24 — online loan-referral app in the same category as Tiền24.

Questions an integrator tends to ask

Does the loan-decision data sit in Tiền24, or with its partners?

Both, split across a boundary. Tiền24 describes itself as a referral platform that introduces P2P partner products, so the front end holds the application a borrower submitted, the amount and term they chose, and the repayment ledger shown back to them; the underwriting decision and disbursement live with the partner institution. We map field by field which side owns what and follow the referral handoff, so an integration reads the Tiền24-held records and does not pretend to own data it cannot see.

The app accrues interest daily — does a synced balance drift every day?

Yes. Tiền24's listing quotes a cap of 18% per year, about 0.05% per day, with overdue penalty also accruing daily. We model the ledger as a dated accrual series rather than a single number, so any figure we hand back is anchored to the date it was queried and matches what the borrower sees in-app on that day.

Which Vietnamese rules govern pulling this data?

The State Bank of Vietnam oversees the space; Decree 94/2025/ND-CP opened a two-year fintech sandbox from 1 July 2025 covering P2P lending, credit scoring and data sharing via Open API. Personal data is governed by Decree 13/2023/ND-CP and the Personal Data Protection Law (91/2025/QH15) in force from 1 January 2026, which require explicit, revocable consent. We build against the consenting borrower's authorization and keep capture scoped to that consent.

Can you capture the third-party app handoffs Tiền24 routes users into?

We capture the handoff event — which partner product was offered and which redirect fired — because that is a Tiền24-held record and it drives the referral funnel. Data inside the third-party app is a separate consent boundary and a separate integration; we flag where the boundary sits rather than reaching across it.