Reaching the hire-purchase ledger inside SG Finance

SG Capital's hire-purchase book — electrical appliances, household goods, captive finance and auto-title lending sold through Singer and Jaymart outlets, per the company's business overview — is what the SG Finance app exposes to each borrower. The app's job is narrow and that is exactly why it integrates cleanly: it shows one customer their contracts, the installment schedule attached to each, the next due date, and a QR code to pay the current installment. There is real structured state behind every screen. The practical question is how to read it out reliably and under proper authorization, and that is the work described here.

What the contract holds

The records below come from the app's own described surfaces — contract lookup, the due-date reminder system, and the scan-to-pay flow. Granularity reflects what a borrower can see for their own account; an integration mirrors that scope for a consenting user.

Getting to the data

Three routes genuinely apply to SG Finance. They are not equal, and the choice depends on how soon you need it and how much of the book you are touching.

Authorized protocol analysis (app and portal traffic)

The SG Finance app and the customer portal at customer.sgcapital.co.th both call the same hire-purchase backend. With the borrower's authorization we observe that traffic, map the auth handshake and the contract and installment endpoints, and turn them into a stable client. This reaches everything in the table above and works today. Effort is moderate; durability depends on how often SGC reshapes the front end, which we plan for.

User-consented credential access

Where a borrower (or a business holding many SGC contracts) consents to act through their own login, we run the same endpoints on their behalf inside a logged, data-minimized session. This suits portfolio holders who want their own contracts pulled on a schedule.

Regulated data sharing as it arrives

The Bank of Thailand's “Your Data” mechanism, formalized in its 30 October 2025 regulation, is built to let a consumer direct loan and payment data held by a financial service provider to a recipient of their choice. Consumer use is expected to begin in the second half of 2026, per BOT announcements. When that channel reaches a non-bank lender like SGC, it becomes the cleanest long-run path. We design the integration so it can adopt that channel without a rebuild.

For most clients the honest recommendation is to start on authorized protocol analysis — it is the only route that returns SG Finance data this quarter — while structuring the client and consent records so the “Your Data” channel slots in once it covers SGC. The choice is driven by timing, not preference.

What lands in your repo

Delivery is a working integration, not a report. For SG Finance that means:

• An OpenAPI specification covering the contract, installment-schedule and payment-status endpoints as we mapped them.
• A protocol and auth-flow report: the login, token issuance and refresh chain the app uses, plus the QR-mint call.
• Runnable source — Python or Node.js — for the key calls: list contracts, fetch a contract's installment schedule, read payment status, decode a payment QR.
• Automated tests that assert a reconstructed schedule reconciles to the contract terms and outstanding balance.
• Interface documentation and a data-retention and consent-logging note keyed to the PDPA.

Each piece is tied to a surface the app actually has. We do not ship stubs for screens SG Finance does not expose.

A contract call, sketched

Illustrative shape only — exact paths, field names and the token mechanism are confirmed during the build against a consenting account, not asserted here.

POST /auth/token
  { "username": "<member>", "password": "<secret>", "device_id": "<bound>" }
  -> { "access_token": "...", "refresh_token": "...", "expires_in": 1800 }

GET /contracts/{contractId}/installments
  Authorization: Bearer <access_token>
  -> {
       "contract_id": "HP-...",
       "hire_purchase_price": 11204.00,
       "down_payment": 2000.00,
       "interest_rate_month": 1.25,
       "installments": [
         { "no": 1, "amount": 767.00, "due_date": "2024-09-30", "status": "PAID" },
         { "no": 2, "amount": 767.00, "due_date": "2024-10-31", "status": "DUE" }
         /* ... 12-24 entries, month-end due dates ... */
       ]
     }

# Reconcile: sum(installments[].amount) and the rate must agree with the
# figures the app renders, or we flag a mapping drift before delivery.

The numeric example mirrors the rate calculation SG Capital publishes on the app's store listing; treat the constants as a worked example, not a live record.

Consent and the BOT rules

Thailand's Personal Data Protection Act has been in full force since 1 June 2022, and the PDPC names financial information as sensitive personal data — which means explicit, purpose-bound consent before collection or use, per the PDPC's September 2022 consent guidance. That consent is the anchor for any SG Finance work we do: scoped to the records you actually need, with expiry and a revocation path, and recorded.

On the open-banking side, SGC is a non-bank lender, so the bank-to-bank dStatement service does not directly carry its data. The relevant instrument is the BOT's October 2025 data-sharing regulation under the “Your Data” programme, which is forward-looking for this kind of provider rather than a switch that is on today. We treat the borrower's PDPA consent as the dependable present-day basis and the BOT channel as where this can move next.

Things we account for

A few specifics about SG Finance shape how we build, and we handle each as part of the engagement:

• Month-end due dates and flat-rate math. The app uses month-end installment dates and a flat per-month interest example (1.25%/month in its published calculation). We model that amortization precisely so reconstructed schedules match the displayed amounts to the cent.
• QR payloads regenerate per installment. Rather than scrape the rendered code, we capture the QR-mint call and decode the EMVCo PromptPay payload, so payment matching survives image and layout changes.
• Two front ends, one backend. App and portal overlap; we map both and choose the steadier surface per record, then re-check on each release so a front-end change does not silently break the feed.
• Bilingual fields. Thai and English labels appear side by side; we normalize them to a single schema so downstream systems get consistent keys.

Access to a consenting account or a sponsor environment is arranged with you during onboarding — it is something the project sets up, not a checklist you clear first.

Interface evidence

Store screenshots we reviewed while mapping the surfaces above. Select to enlarge.

Comparable apps

Other Thai lending and installment apps hold the same kind of contract and payment state, which is why integrators often want them mapped to one schema. Named here for context, not ranked:

• AEON (Thailand) — installment and hire-purchase financing for appliances, IT and more, with member-tier installment plans.
• Krungsri — consumer finance, auto loans and credit cards under MUFG-affiliated Bank of Ayudhya.
• SCB EASY — carries the UP-Ngern-Yuem revolving installment line alongside core banking.
• Krungthai NEXT — transfers, bill pay and loan application from Krungthai Bank.
• Paotang — Krungthai's state-linked wallet and services app.
• KTC Mobile — Krungthai Card statements, credit lines and installment conversions.
• Home Credit Thailand — point-of-sale installment and cash loans.
• Singer Thailand — SGC's parent brand, with its own sales-and-financing footprint.

How this was checked

The surfaces and terms here come from the SG Finance Google Play listing and SG Capital's own corporate pages, cross-read against the Bank of Thailand's open-data material and Thailand's PDPA guidance. Regulatory status reflects BOT announcements current to mid-2026.

• SG Finance on Google Play
• SG Capital — company overview
• Bank of Thailand — data-sharing regulation (Oct/Nov 2025)
• Bank of Thailand — Open Data

Mapped by the OpenBanking Studio integration desk — June 2026.

Questions integrators ask

Can you reconstruct an SG Finance installment schedule that matches the figures the app shows?

Yes. The app states month-end due dates and a flat 1.25% per month example (12 installments of 767 THB on a financed price of about 11,204 THB, per its store listing). We model that amortization so a reconstructed schedule reconciles to the contract terms and outstanding balance the borrower sees in the app.

Does Thailand's open-banking work cover a non-bank lender like SG Capital?

The Bank of Thailand enacted a data-sharing regulation on 30 October 2025 covering loan and payment information held by financial service providers, with consumers expected to begin exercising the right in the second half of 2026 per the BOT's announcements. Until that mechanism reaches SGC, the dependable basis is the borrower's own explicit consent under the PDPA, with authorized protocol analysis of the app and customer portal as the working route.

How do you handle the QR-code payments the app generates?

We capture the call that mints each installment QR and decode the EMVCo PromptPay payload rather than reading the rendered image. That gives a stable, machine-readable reference for matching a confirmed payment back to a specific installment.

Do you integrate the app or the SG Capital customer portal?

Both front the same hire-purchase backend. The mobile app and customer.sgcapital.co.th expose overlapping contract and payment surfaces, so we map both and pick whichever is steadier for the records you need, then re-validate on releases.

A typical SG Finance build wraps up inside one to two weeks. You can take it as runnable source from $300, paid only after delivery once you have checked it does what you need, or call our hosted endpoints and pay per request with nothing up front. Either way you give us the app name and what you want out of its data; access and the PDPA consent paperwork are arranged with you as part of the work. Start the conversation at our contact page.