Reaching the loan ledger and policy records inside ติดใจ by เงินติดล้อ

Open ติดใจ and a borrower sees a vehicle-title loan balance that moves in real time, a dated repayment history, the next due date, and the motor-insurance policies tied to the same login. That is the data a third party wants to query or sync — a servicer dashboard, a debt-advisory tool, a fleet-insurance tracker — and reaching it is what this brief is about. ติดใจ is the rebuilt app from Ngern Tid Lor (เงินติดล้อ), the listed lender behind the TIDLOR ticker, and it bundles lending, insurance brokerage and a few lifestyle services under one account.

The app stitches together more than one backend — the title-loan core, the insurance brokerage, a gold-savings wallet, an affiliate ledger — which makes it more interesting to integrate than a single-product app and a little more work to map cleanly. Below is what is reachable, the authorized way in, and what lands in your hands at the end.

Data inside the app

Each row reflects a surface ติดใจ actually shows a logged-in user, not a generic finance checklist.

Authorized routes to that data

Three ways in genuinely apply to ติดใจ. They differ in reach, in how much survives an app update, and in what we stand up to operate them — and the setup work sits with us, arranged with you, not as a checklist you clear first.

Authorized interface integration (protocol analysis)

We analyse the app's own traffic under your authorization and rebuild the calls behind the loan ledger, the policy list and the payment screens as a clean API. Reach is broad: anything the app renders, the integration can return. Effort is moderate and durability tracks the app's release cadence — when a screen changes, the affected call is re-mapped. We run this against a consenting account or a sponsor sandbox, set up with you during onboarding.

User-consented credential access

For an aggregation product, the end user consents and we operate the session on their behalf, returning their own balances, history and policies. Reach matches what that user sees; the consent record and revocation path are part of the build.

The BOT "Your Data" scheme (forward-looking)

The Bank of Thailand enacted its consumer data-sharing regulation in late 2025, starting with deposit data and expanding to loan and payment categories across 2027–2028. Once a loan-data phase carries Tidlor's records, a regulated consented-sharing route becomes available; we design the integration so that path can be added without a rebuild.

For ติดใจ today, authorized interface integration against a consenting account is the route we would actually run. It is the only one that returns the live title-loan balance and the current policy list the moment the app does, and the BOT scheme is still phasing deposit data first. Where the app exposes an in-app statement or export view, we treat that as a corroboration source, not the primary feed.

What you get back

The deliverable is a working integration for the surfaces above, not a report. For ติดใจ that means:

• An OpenAPI/Swagger spec covering loan balance, repayment history, quote, payments and policy endpoints.
• A protocol & auth-flow report: the login, token issue and refresh chain as it actually behaves across the lending and insurance subsystems.
• Runnable source for the key endpoints in Python or Node.js, with the fee model so totals reconcile against the 24% all-in cap.
• Automated tests, including the policy-expiry and พรบ paths that move most often.
• Interface documentation, plus PDPA-aligned guidance on consent records and data retention.

Worked example: loan balance after token refresh

Illustrative shape only — field names and the exact auth chain are confirmed during the build against a consenting account, not asserted here as the app's internal contract.

# Authorized interface integration — title-loan balance read
POST /auth/token            # device + session credential, consented
  -> { access_token, refresh_token, expires_in }

GET  /loans/{contract_id}/balance
  Authorization: Bearer <access_token>
  -> {
       "contract_id": "NTL-…",
       "principal_outstanding": 0.00,
       "next_due_date": "YYYY-MM-DD",
       "all_in_rate_pct": 24.0,      # interest + fees, capped per BOT
       "transfer_fee_thb": 3
     }

# Adapter notes carried in the delivered client:
#  - on 401, replay /auth/token with refresh_token, then retry once
#  - reconcile interest + 3 THB transfer fee into the contract's
#    all-in figure before surfacing a total
#  - policy + พรบ calls live behind a separate adapter (see notes)

Where this gets used

• A debt-advisory service that needs a live title-loan balance and repayment history to model an early payoff against the 12–24% rate band.
• An SME fleet operator tracking พรบ and voluntary motor-insurance expiry across many vehicles from one feed instead of opening the app per car.
• A partner reconciling affiliate payouts against its own referral records.

Consent and the regime around it

Thailand's Personal Data Protection Act (PDPA, B.E. 2562, in force since June 2022) is the governing privacy law here: collection, use and disclosure need an explicit, granular, logged consent that the data subject can withdraw, and the cross-border transfer rules that took effect in March 2024 shape where any processing can sit. Every integration we run carries a consent scope tied to the loan and policy data requested, an expiry and revocation path, and data minimization so only the requested domains are touched. The BOT "Your Data" framework is the forward-looking layer — it will add a regulated sharing route as its loan-data phases land, but it does not yet carry Tidlor's records, so the dependable basis today is the account holder's own authorization. Access is logged, and we work under NDA where the engagement needs it.

Engineering judgment specific to ติดใจ

A few things about this app shape how we build, all handled on our side:

• The app fronts several backends behind one login. We map the title-loan core, the insurance brokerage, the gold-savings wallet and the affiliate ledger as separate subsystems and normalize them into one schema, so a client can take only the slice it needs.
• Charges are presented per-contract under a single 24% annual cap, with the 3-baht transfer fee folded in. We model the fee schedule explicitly so reconstructed repayment totals match what the app displays, rather than splitting interest and fees into figures that do not reconcile.
• The motor-insurance renewal and พรบ flows change more often than the loan screens. We isolate them behind their own adapter and add a verification pass to maintenance, so a front-end change to renewal is caught and patched before the expiry feed goes stale.

Interface evidence

Store screenshots of the surfaces referenced above. Select to enlarge.

How this was mapped

We checked the Google Play listing for com.ntl.cxm_mobile and the Tidlor app guide for the feature set and the 12–24% rate band (stated on the listing as of April 2025), the Bank of Thailand's data-sharing announcements for the "Your Data" timeline, and PDPA references for the consent regime — all in June 2026. Primary sources:

• Google Play — ติดใจ โดย เงินติดล้อ
• Tidlor — app features (balance, bill pay, transfer)
• Bank of Thailand — data-sharing regulation (Nov 2025)
• Bank of Thailand — Open Data

Mapped by the OpenBanking Studio integration desk · 26 June 2026.

Adjacent apps in the same data landscape

Same category, named for ecosystem context only — a unified title-loan or motor-insurance integration usually touches several of these.

• Srisawad (SAWAD) — title-loan balances and repayment schedules; one of the three largest in the segment.
• Muangthai Capital (MTC) — vehicle and land-title loan accounts with per-contract repayment data.
• SCB EASY (My Car My Cash) — bank car-cash loans alongside deposit and card data.
• Krungsri (Car4Cash) — auto-backed lending inside Bank of Ayudhya's mobile app.
• TTB Touch — Thanachart-lineage car-title loans and account data.
• Kasikorn K PLUS — broad retail banking holding loan and payment records.
• Heng Leasing — title and hire-purchase loan accounts in a similar microfinance bracket.

Questions integrators ask about ติดใจ

Can the lending data be pulled apart from the insurance and gold-savings sections of ติดใจ?

Yes. The app fronts several distinct backends — the title-loan core, the insurance brokerage, the gold-savings wallet and the affiliate ledger — behind one login. We map each subsystem's calls separately and normalize them into one schema, so an integration can subscribe to only the loan ledger, only policies, or all of it.

Does the 24% all-in fee cap change how repayment figures come back from the app?

It shapes them. The app folds interest, the 3-baht-per-transfer fee and other charges into a single cap of 24% per year, as its Play listing describes. We model that fee schedule explicitly so reconstructed totals reconcile against the per-contract figures the app shows, rather than treating interest and fees as separate lines.

Will the Bank of Thailand 'Your Data' scheme make this integration unnecessary?

Not in the near term. The BOT enacted its data-sharing regulation in late 2025 with deposit data first and a phased expansion of loan and payment data across 2027–2028. Until a loan-data phase actually carries Tidlor's records, consented interface integration is what reaches the live ledger; we design so a future scheme route can slot in alongside it.

How do you keep a sync working when the motor-insurance renewal flow changes?

The renewal and พรบ (compulsory motor) paths move more often than the loan screens. We isolate those calls behind their own adapter and wire a verification pass into maintenance, so when the renewal front end shifts the policy-expiry feed is re-checked and patched rather than silently going stale.

Source-code delivery for the ติดใจ loan and policy endpoints — runnable client, OpenAPI spec, tests and documentation — starts at $300, and you pay only after delivery once you have what you asked for. If you would rather not host anything, call our endpoints on a pay-per-call basis with no upfront fee instead. The build cycle is one to two weeks either way, and you start by telling us the app name and what you want from its data; access and PDPA-aligned consent are arranged with you as part of the work. Tell us what you need from ติดใจ and we will scope it.