兴趣爱好============================
Integration API
Unlock Korean Household Ledger Data via Excel, Drive Backup, and Normalized JSON
============================
is one of South Korea's most widely used personal finance ledger apps,
developed by HS App and distributed free on Google Play under the package ID
cashbook.app.hs. The app covers the full household ledger pattern: cash balances,
(bankbook), (debit card), (credit card), monthly budgets,
debt records, installment schedules, and per-entry photo notes.
Because stores its ledger on the device, integrators do not call a
public server API. The real surfaces are three first-party export paths — Excel
export, Google Drive backup, and direct on-device read — plus a parallel Korean
MyData feed for the bank-and-card transaction half.
OpenBanking Studio delivers a parser, schema, test suite, and documentation for
each of these routes, letting downstream apps and data warehouses consume the
ledger without building their own Korean-header mapping or Drive-backup decoder
from scratch. From $300 for source delivery, or pay-per-call with no upfront fee.
--------------------
SUPPORTED API FEATURES
--------------------
The integration layer built for covers the following capabilities:
Excel Export Parsing
Reads the single-sheet .xlsx the app emits, maps Korean column headers
(, , , , , , /) to stable English
keys, and handles wording variants across app versions using a
column-position fallback.
Google Drive Backup Decoding
Connects to the owner's Drive via a scoped OAuth grant, decodes the
backup file, and normalizes the output — including base64-encoded photo
attachments with an optional redaction step for pipelines that should
not store images.
On-Device SQLite Extraction
Reads the app's private store directly via ADB or a small companion
utility on the owner's handset, reaching every record the UI shows,
photo blobs included. Suited to one-shot migrations.
Korean MyData Feed Integration
Wires the bank-and-card transaction half to a licensed /
MyData provider under the FSC scheme, returning auto-imported card and
bank rows from the source issuers directly.
Normalized JSON Output with OpenAPI 3.1 Specification
All routes produce a unified JSON schema covering assets, transactions,
budgets, debt records, and installments — documented in both English and
Korean.
PIPA-Compliant Data Handling
Consent text in Korean, per-class data scoping, retention guidance for
photo notes, and a delete-on-request channel, aligned with Korea's
Personal Information Protection Act.
--------------------
USE CASES & APPLICATIONS
--------------------
[1] Personal Finance Coaching and Planning Tools
Ingest asset balances across cash, bankbook, debit, and credit card
instruments to build a net-worth feed.
Combine budget caps with actual spend roll-ups for variance alerts.
Surface installment schedules and recurring entries in a forward-looking
ledger view.
Compare the owner's manual debt records against bank-sourced rows to
identify gaps.
[2] Spend Analytics and Category Dashboards
Normalize the / / / / kind vocabulary into a
consistent schema for downstream aggregation.
Roll up category and sub-category fields for period-over-period analysis,
even when the owner toggles the upper/lower category setting mid-month.
Serve the category statistics panel the app already computes, enriched
with cross-account views not available inside the app itself.
Export category roll-ups to a data warehouse for cohort and segment
reporting across many users.
[3] Data Migration from to Another Platform
Run the on-device extractor against a USB-connected handset to pull a
complete historical ledger in one pass.
Preserve photo attachments from simple notes (base64 from the Drive
backup route) so receipt images migrate alongside the entries.
Map the Korean asset-kind vocabulary to the target app's schema using
the provided translation table.
Carry debt records (borrowed, lent, repaid, received) and installment
series across to the new platform without manual re-entry.
[4] Cash Flow Projection and Credit-Card Cycle Management
Reconcile the parent credit-card purchase, the per-month installment
rows, and the card-payment deduction entry as three linked records to
avoid double-counting.
Project the settlement date and remaining installment balance for each
credit card cycle boundary.
Combine bankbook balances with scheduled outflows to generate a
forward-looking cash position for the household.
Alert when projected end-of-cycle balance falls below a threshold, using
the budget caps already set in the app.
[5] Receivables and Payables Sync for Household Accounting
Extract debt records per counterparty with origination date, repayment
events, and outstanding balance.
Sync borrowed and lent entries to an external receivables tracker or
shared household accounting tool.
Link debt entries to the transaction rows that represent the actual
cash movement for a complete audit trail.
Handle multi-counterparty debt ledgers where the owner tracks both
personal loans and household split expenses.
--------------------
BENEFITS & ADVANTAGES
--------------------
Covers All Data Domains — Assets, Transactions, Budgets, Debts, Installments
The integration spans every data class the app stores, not just the
transaction rows. Budget caps, debt records, and installment schedules are
first-class outputs alongside balances and spend history.
Three Export Routes Plus MyData for Maximum Coverage
Excel export for weekly batch refreshes, Google Drive backup for ongoing
sync without polling the device, on-device read for one-shot migration, and
a MyData feed for live bank-and-card data — the right route for each use
case, combined where needed.
Version-Resilient Korean Header Mapping
The parser pins against Korean column header text with a column-position
fallback, and the maintenance contract covers a recheck against the latest
export sample each quarter — so a header-label change in a new app release
does not break the pipeline.
Category Toggle Handled Gracefully
The upper/lower category toggle is a settings flag that can change mid-month.
The OpenAPI schema marks category_sub optional, so downstream maps continue
to work whether the owner has the toggle on or off, for both old and new rows.
Photo Attachment Support with Redaction Option
Drive-backup route output includes photo notes base64-encoded, with a
documented redaction option for pipelines that should not hold images —
handled at the parser stage, not retroactively.
PIPA and MyData Compliance Built In
Korean-language consent text, per-class data scoping, and a
data-processing agreement covering retention period and delete-on-request are
included in every engagement, not offered as add-ons.
Flexible Commercial Model — Source or Hosted Endpoint
Take delivery of the full runnable source (parser, decoder, tests, docs) from
$300 and run it in your own infrastructure, or skip the source and call a
hosted endpoint billed per call with no upfront fee. Both routes include the
OpenAPI spec and bilingual documentation.
OpenBanking Studio offers two ways to engage for integration:
------------
Source Delivery
------------
One-time fee from $300 (scope-dependent)
Includes: Excel-export parser, Google Drive backup decoder, optional
on-device extractor, pytest suite, OpenAPI 3.1 specification, interface
documentation in English and Korean, PIPA compliance brief
Review the code and run it against your own export before paying
Maintenance contract available for quarterly export-sample rechecks
No upfront fee — billed per API call
Same normalized JSON output as the source route
Includes OpenAPI spec and bilingual documentation
Suitable for teams that prefer managed infrastructure over self-hosting
Both plans are scoped through a contact form: describe the app and what you
need out of it, and OpenBanking Studio scopes the work back within a day.
stores one of the most complete household ledger data sets in the
Korean Android ecosystem — cash positions, card balances, budgets, debt records,
installment schedules, and photo-attached notes, all on the owner's device with
no public server API. The integration routes documented by OpenBanking Studio
turn those three export surfaces and the MyData parallel rail into a clean,
versioned, PIPA-compliant data pipeline.
Whether the goal is a spend analytics dashboard, a data migration, a cash flow
projection tool, or a receivables tracker, the normalized JSON output and OpenAPI
specification give downstream apps a stable foundation that survives app version
changes and category-toggle mid-month flips.
For integration scoping, pricing details, and technical documentation, visit:
https://openbankingstudio.com/-.html
Describe the app name and the data you need — OpenBanking Studio will scope
the work and respond within one business day.
