Getting structured data out of Dime!, KKP's all-in-one wealth app

Six asset classes share one login in Dime!: a THB savings account, a USD foreign-currency deposit, US equities bought in fractions from 50 THB, Thai equities, mutual funds, gold, and corporate bonds. The app is operated by KKP Dime Securities, a member of the Kiatnakin Phatra Financial Group, per its About page. That breadth is the reason an integrator looks here — one account holds a balance sheet that elsewhere takes five separate connections to assemble. The work is mapping each of those surfaces to a clean, consented API.

The route we would actually take starts from the account holder's own authorization. Dime! settles Thai stock trades straight from the savings account, so the cash ledger and the order ledger are tightly coupled — a detail that shapes every later schema decision. Below: what the app holds, how we reach it, and what lands in your repo.

What lives behind the login

Each row is a surface the app actually exposes to its own user, named the way Dime! names it.

How we reach it

Two routes carry the bulk of the work here, with a third as a forward path. Access, onboarding and any sandbox are arranged with you during the engagement — not something you line up first.

User-consented access and protocol analysis

With the account holder's authorization, we map the app's own client-to-server traffic: the login and token-refresh chain, the portfolio and statement endpoints, the order-history calls. This reaches everything the table above lists, because it is the same data the app shows the user. Effort is moderate and the result is durable as long as we account for client updates; the studio runs a re-check pass when the front end shifts.

Native export under PDPA portability

Thailand's PDPA gives the account holder a right to a portable copy of their data. Where Dime! fulfils an export, it is a low-effort, well-grounded baseline — good for periodic statement and holdings pulls, weaker for real-time positions. We use it as a reconciliation anchor against the live mapping.

Bank of Thailand Open Data sharing

The Bank of Thailand enacted its Open Data regulation in late 2025, letting consumers direct a provider to share their financial data with another supervised provider; holders are expected to start exercising this in the second half of 2026, per the BOT. For deposit and payment data this becomes the cleanest consented channel over time. We design the integration so it can adopt that channel for the savings and FCD surfaces as it goes live, without re-plumbing the rest.

For a build today we recommend the consented mapping as the working integration, with the PDPA export as a periodic cross-check, and the Open Data channel adopted for the savings and FCD surfaces once it reaches retail holders. We lead with the mapping here for a concrete reason: Dime!'s highest-value surfaces — equities, funds, gold — sit outside the deposit scope BOT opens first, so a deposit-only channel would miss most of the book.

What lands in your repo

Concrete artifacts, each tied to a surface above:

• An OpenAPI 3 specification covering the endpoints we map: auth, portfolio, per-asset holdings, order history, statement lines.
• A protocol and auth-flow report documenting the login, token issuance and refresh chain, and how the Thai-stock fill ties to the savings debit.
• Runnable source for the key endpoints in Python and Node.js — authenticate, pull holdings per asset class, page through orders, normalize currency.
• A normalized schema that folds savings, FCD, US and Thai equities, funds, gold and bonds into one position model with currency and FX-at-fill preserved.
• Automated tests against recorded fixtures, plus interface documentation and data-retention guidance aligned to PDPA.

A holdings pull, sketched

Illustrative — field names are confirmed against live traffic during the build, not guessed from the listing.

# Consent-scoped session, then a unified holdings read
POST /auth/token
  { "grant": "user_consent", "device_id": "...", "scope": ["portfolio","statements"] }
  -> { "access_token": "...", "refresh_token": "...", "expires_in": 1800 }

GET /v1/portfolio/positions?asset=all
  Authorization: Bearer <access_token>
  -> { "positions": [
        { "class": "us_equity", "symbol": "VOO", "qty": 0.4213,
          "ccy": "USD", "avg_cost": 511.20, "fx_at_fill": 36.42 },
        { "class": "thai_equity", "symbol": "PTT", "qty": 200,
          "ccy": "THB", "settles_from": "dime_save" },
        { "class": "fund", "amc": "...", "nav": 12.83, "units": 540.11 },
        { "class": "gold", "grams": 3.50, "ccy": "USD", "spot_ref": 2410.5 }
      ] }

# Refresh before expiry so a long gold session (07:00-03:00) never drops mid-poll
if token.expires_in < 120: POST /auth/token { "grant": "refresh_token", ... }
      

Consent and the Thai rulebook

KKP Dime Securities is licensed under the SEC Thailand securities regime, and the app sits under the PDPA, in force since 2022, which grants the account holder access and portability over their own records. Everything we do rests on that holder's explicit authorization, scoped to the surfaces the project needs. The Bank of Thailand's Open Data regulation, enacted in late 2025, adds a supervised consumer-directed sharing channel for deposit, loan and payment data; we treat it as where deposit access is heading, not as something already serving retail holders. Consent is recorded with scope and expiry, access is logged and data-minimized to the agreed fields, and we work under NDA where the engagement calls for it.

Things we account for in the build

Two details about Dime! specifically shape the integration, and we handle both:

• The cash leg under the equities. Because the savings account is also the settlement account for Thai stocks, a buy shows up as both an order and a cash debit. We model that one-to-one so the unified view reconciles rather than counting the money twice.
• Currency spread across the book. THB savings, a USD FCD deposit, USD-priced US stocks and USD-or-THB gold coexist. We normalize each position to its native currency and capture the FX rate at the fill, instead of reapplying a single rate after the fact.
• The long gold session. Gold trades roughly 07:00 to 03:00 against live global prices; we design the price and holdings sync around that near-continuous window and its cross-midnight boundary so a poll never lands in a phantom gap.

Interface evidence

Store screenshots we referenced while mapping the surfaces. Click to enlarge.

Freshness, by asset class

Not every surface moves at the same speed, and the sync respects that. Mutual fund NAV settles end-of-day, so a daily pull is enough. US equity prices and orders are real-time during the US session. Gold runs near-continuously against global spot. Savings interest accrues on KKP's schedule. We tag each domain with its cadence and poll accordingly, instead of hammering every endpoint on one timer.

Where Dime! sits among Thai investing apps

Same-category apps an aggregator would map alongside Dime!, each holding overlapping but distinct data:

• Webull Thailand — US and Thai equities with extended-hours trading; holds order and position data per account.
• InnovestX — SCB's investment app spanning Thai and global assets plus funds; account-bound portfolio records.
• Finnomena — fund-focused advisory and trading; holds goal-based fund portfolios and transaction history.
• Wealthmagik — mutual-fund aggregation across AMCs; consolidated fund holdings and NAV history.
• Liberator — commission-free Thai equity trading; order and position data behind the login.
• Bualuang Securities — Bangkok Bank's brokerage app; Thai equity orders and settlement records.
• Saxo Investor — multi-asset global trading available to Thai investors; cross-market positions and statements.

A unified wealth view across these reads the same shapes Dime! exposes — balances, orders, fund holdings — which is why one normalized schema serves the set.

Questions integrators ask about Dime!

Can one integration cover both the savings cash leg and the Thai-stock settlement it funds?

Yes. In Dime! the savings account doubles as the settlement account for Thai stock trades, so a fill and the matching cash debit are two sides of one event. We model that linkage explicitly so positions and cash reconcile instead of double-counting.

Which Thai regulator sits behind Dime!'s securities data, and how does that shape consent?

KKP Dime Securities operates under the SEC Thailand securities regime, and the app falls under the PDPA, which carries a data-portability right effective since 2022. The Bank of Thailand's Open Data rules, enacted in late 2025, add a consented financial-data sharing channel that account holders are expected to begin exercising in the second half of 2026. We build on the user's own authorization and design for that consent layer as it lands.

How do you handle the USD FCD account and USD-priced US stocks and gold alongside THB balances?

Each position is normalized to its native currency, with the FX rate captured at the moment of the fill or statement line rather than recomputed later. THB savings, the USD FCD deposit, US equities and gold all land in one schema with currency and rate preserved per row.

Does mutual-fund coverage span all the asset management companies in the app?

Dime! lists more than 1,700 funds from around 20 asset management companies, as the app describes it. Holdings, NAV and subscription or redemption records are mapped into one fund schema regardless of which AMC issued the fund, so the integrator sees a single portfolio.

Sources and how this was put together

Mapped in June 2026 from the app's own description and store listing, the operator's site, and current Thai regulatory material. Primary references: the BOT's Open Data data-sharing regulation and its earlier Your Data project note; KKP Dime's About page; the Google Play listing; and a Nation Thailand report on the app. Surface field names are verified against live traffic during the build, not asserted from these pages.

Mapped by the OpenBanking Studio integration desk · 2026-06-26

The build that comes out of this is the runnable source for Dime!'s key surfaces plus the OpenAPI spec, auth-flow report, tests and interface docs — delivered as a one-time package from $300, billed only after you have looked it over and you are satisfied. If you would rather not host anything, call our endpoints instead and pay per call with nothing upfront. The cycle is one to two weeks from the point we have the app name and what you want pulled out of it; access and compliance are arranged with you along the way. Tell us the surfaces you need at /contact.html and we will scope it.