Reaching a borrower's revolving credit line inside สินเชื่อด่วน

The available credit line inside สินเชื่อด่วน is a live server-side number. It drops when a borrower draws against the limit and climbs back the moment a repayment posts, all without a fresh application. That refill behaviour, not a static loan balance, is the part an integrator actually wants — and it only lives on the lender's backend, reachable once a borrower's session is in hand. The app describes an approved line of ฿5,000 to ฿90,000, terms of 91 to 365 days, and an APR up to 14.6% (all per its Play Store description). Fees accrue only on the amount drawn, for the days it is out.

The bottom line is short. There is real, structured, per-borrower data here, and the practical way to it is the app's own authenticated traffic rather than any data-sharing scheme, which does not yet cover loan records. We map the login, the credit-line query and the repayment endpoints against a consenting account and give you runnable code that reads them.

Reaching the data

Three routes apply to this app. They differ in how much they reach today and how long they hold up.

Authorized protocol analysis under borrower consent

The สินเชื่อด่วน client authenticates to a lending backend and then requests the borrower's line state. We observe that exchange against a consenting account, document the token/session chain, and pin the calls that return the approved limit, the list of drawdowns and the repayment schedule. Effort is moderate. Durability depends on the app's release cadence, so we note which calls are version-sensitive. Access is set up together during onboarding, against a consenting borrower's account — nothing you need to assemble in advance. This is the route we would run for สินเชื่อด่วน now, because it reaches the live line today and the regulated alternative does not yet cover loan data.

Consented session capture

For a one-off pull or a small book, a borrower logs in and we capture and normalize that single session into the same schema. Lighter to stand up, narrower in reach: it gives a point-in-time snapshot of one account rather than a standing feed. Useful as a first proof against real data before a wider build.

BOT "Your Data" regulated sharing (forward-looking)

The Bank of Thailand enacted a data-sharing regulation on 30 October 2025 under its "Your Data" project. Its phased schedule begins with individual deposit accounts by the end of 2026 and reaches loan and payment records only across 2027 and 2028 (per the BOT's own announcement). Once loan data is in scope, this becomes the durable, consent-native path with no client-side mapping to maintain. It is worth designing toward — but it is not a route you can call against สินเชื่อด่วน today, so we build on borrower consent now and keep the schema ready to switch onto it later.

Behind the login

Each row below is a surface the app puts in front of the borrower, mapped to what an integrator would do with it.

The build

What you get is the working integration for this app, not a report about it:

• An OpenAPI/Swagger spec covering the authenticate, credit-line, drawdown-list and repayment-schedule calls as observed on สินเชื่อด่วน.
• A protocol and auth-flow report: the login-to-token exchange, how the bearer session is carried, and refresh handling.
• Runnable source in Python and Node.js for each of those calls, with error handling for an expired token and an empty line.
• A normalized credit-line schema so the refill mechanic and the per-drawdown fee are represented once, cleanly.
• Automated tests with fixtures for a live line, a fully-drawn line, and a repaid-then-refilled line.
• Interface documentation plus PDPA-aligned consent and retention notes.

In code

A trimmed sketch of the two calls that carry the value — authenticate, then read the line. Field names are illustrative and get confirmed during the build against a consenting account.

# Illustrative. Endpoints/fields confirmed during the build.
POST /api/v1/auth/login
  { "mobile": "0xx-xxx-xxxx", "otp": "######" }   # OTP + device binding, per observed flow
  -> 200 { "access_token": "…", "expires_in": 3600 }

GET /api/v1/credit-line            Authorization: Bearer <access_token>
  -> 200 {
       "approved_limit_thb": 90000,   # ceiling of the approved line
       "available_thb":      61200,   # refills as repayments post
       "outstanding_thb":    28800,
       "apr_pct":            14.6,    # up to 14.6% per app description
       "currency":           "THB"
     }

Normalized to one object so a consumer never re-derives the refill logic, and the app's own worked example (฿10,000 at 14.6% over 120 days = ฿480 fee) drops straight into a schedule row:

{
  "borrower_ref": "<hashed-id>",
  "currency": "THB",
  "line": { "approved": 90000, "used": 28800, "available": 61200 },
  "drawdowns": [
    { "id": "dd_01", "amount": 10000, "opened": "2026-03-02",
      "apr_pct": 14.6, "term_days": 120, "fee_accrued": 480 }
  ],
  "schedule": [
    { "due": "2026-06-30", "principal": 10000, "fee": 480, "status": "scheduled" }
  ]
}

Consent & Thai rules

Two regimes touch this work, and only one is usable for loan data right now. Thailand's Personal Data Protection Act (PDPA), in full force since 1 June 2022, treats financial information as sensitive personal data that needs the borrower's explicit consent, and it grants data subjects a right of access and a right to portability in a structured electronic format. Those rights are what make a consented pull from a borrower's own account lawful and are the basis we build on. The Bank of Thailand's "Your Data" regulation adds a provider-to-provider sharing mechanism, but as noted its loan-data phase lands in 2027–2028, so it is where this integration can migrate, not where it starts. We keep consent scoped to the named data classes, honour withdrawal the same way it was given, log what was accessed, minimize what is stored, and work under an NDA where the engagement calls for one.

Build details

The revolving mechanic drives most of how this integration is written, and we account for it inside the build. The available limit is a derived figure, not a stored balance. It recomputes every time a repayment posts. We treat it as a computed field and reconcile it against the drawdown-and-repayment ledger, so a sync taken in the middle of a cycle agrees with itself instead of trusting one number that may already be stale.

Fee accrual is per-drawdown — amount × APR ÷ 365 × days — so two draws against the same line carry different running costs and different maturities. We split the schedule per drawdown, which keeps principal and cost of credit reportable on their own rather than blended into a single figure.

On housekeeping: the package namespace (in.money.rupee.bridge.cash) points to a lending stack that appears to serve more than one market, so we pin Thai locale and baht handling explicitly during the build. When the app ships an update, re-mapping the affected calls is part of the upkeep we do, not something the integration silently breaks on.

App screens

The screens we referenced while mapping the surfaces above — tap to enlarge.

Pricing

Source-code delivery starts at $300, and you pay after we hand it over and you have run the credit-line, drawdown and schedule calls yourself. That price buys the runnable source, the OpenAPI spec, the auth-flow report, the tests and the interface docs for สินเชื่อด่วน. If you would rather not host anything, the pay-per-call option puts the same integration behind our endpoints with no upfront fee — you call, you pay for calls. Either way a typical build is ready in one to two weeks. Tell us the account you want mapped and what you need out of it on the contact page, and we set up the consented access with you from there.

Related apps

Other Thai revolving-credit and personal-loan apps hold comparable per-borrower data, which is why a single normalized schema tends to serve a book that spans several of them. Named for context, not ranked:

• Rabbit Cash — revolving nano-loan under a Bank of Thailand licence, drawing against a set limit with flexible repayment.
• MoneyThunder — SCB Abacus revolving personal and nano-finance lending with a low minimum payment.
• FINNIX — MONIX/SCBX revolving credit line built around fast approval.
• PROMISE — a BOT-regulated revolving personal loan with per-cycle repayment.
• Kredivo Thailand — buy-now-pay-later plus cash loans, holding installment and limit data.
• LINE BK — social-banking Credit Line inside the LINE app, with account and borrowing records.
• Wealthi Techfin — a Pico Finance product with its own loan and repayment ledger.
• Good Money (GSB) — a state-bank digital lending app aimed at underserved borrowers.
• Siam Digital Lending — personal loan and nano-finance under BOT supervision.

What we checked

We read the สินเชื่อด่วน Play Store listing for the product mechanics, limits, term and the worked fee example, then cross-checked the Thai regulatory picture against primary sources: the Bank of Thailand's own regulation and its "Your Data" project page for the data-sharing timeline, and the PDPA overview for the consent and portability rights this build relies on. Sources opened for this write-up:

• Bank of Thailand — data-sharing regulation (30 Oct 2025)
• Bank of Thailand — "Your Data" project
• Thailand PDPA — data protection overview
• สินเชื่อด่วน — Google Play listing

Reviewed on 1 July 2026 by the OpenBanking Studio integration desk.

Questions

Does the available-limit figure update as a borrower repays?

Yes. In สินเชื่อด่วน the available line is a live server-side number that drops on a drawdown and refills when a repayment posts, with no new application. We model it as a computed value and reconcile it against the drawdown and repayment ledger so a sync taken mid-cycle stays correct.

Can you separate accrued fees from principal in the repayment schedule?

Yes. The app computes cost as amount used times APR divided by 365 times days, per its worked example (10,000 x 14.6% / 365 x 120 = 480). We split each schedule row into principal and accrued fee per drawdown so accounting sees the cost of credit on its own.

Is สินเชื่อด่วน covered by the Bank of Thailand Your Data rule yet?

Not for this data class today. The BOT enacted its data-sharing regulation on 30 October 2025, but the phased rollout starts with individual deposit accounts by end of 2026 and reaches loan data only across 2027 to 2028. Until then the dependable basis is the borrower's own PDPA consent, which is the route we build on now.

What does a สินเชื่อด่วน integration cost and how soon is it usable?

Source-code delivery starts at 300 USD and you pay after we hand it over and you have checked the credit-line, drawdown and schedule calls run. A typical build lands in one to two weeks; the pay-per-call hosted option carries no upfront fee.