Money Manager (Realbyte) API integration & data export

Deliverables checklist

• OpenAPI 3.1 specification covering accounts, transactions, budgets, recurring entries, and backup ingestion
• Protocol report on the Money Manager Excel/JSON backup schema and the Wi-Fi PC Manager channel
• Runnable reference implementation in Python (FastAPI) and Node.js (NestJS), including a parser for the sub-currency Excel format
• Postman collection, sample backup fixtures, and an integration test suite covering ledger balance invariants
• Compliance pack: data minimization map, retention policy, GDPR data subject request handlers, audit-log schema

Data available for integration

Typical integration scenarios

1. Accounting back-office sync. A small business owner records every cash and card expense in Money Manager. Our integration polls the daily Google Drive backup, parses the sub-currency Excel format, and posts each double-entry pair into Xero or QuickBooks via their journal entry endpoints, preserving category mappings.

2. Personal-finance dashboard mash-up. A neobank wants to display unified spend across its own card and the user's other wallets. The user grants consent, our API exposes Money Manager transactions and budgets, and the bank renders one combined timeline alongside its real-time card feed.

3. Tax-prep automation. At year end, freelancers ask their bookkeeper to fetch all deductible expenses. Our API returns transactions filtered by category and date range as JSON, ready to drop into local tax templates (Korean NTS Hometax, US Schedule C, UK self-assessment).

4. Couples & family budgeting. Two partners both keep separate Money Manager ledgers. Our consolidator endpoint merges both streams, deduplicates transfers between household accounts, and emits one shared budget-vs-actual report each Sunday.

5. Loan underwriting affordability check. A regulated lender needs evidence of stable income and discretionary spend. With explicit user consent, the lender ingests three months of Money Manager statements through our API, scores affordability, and stores only the aggregate fields permitted by local consumer-credit rules.

1. Authorize and bind a user

POST /api/v1/moneymanager/auth/bind
Content-Type: application/json
Authorization: Bearer <PARTNER_API_KEY>

{
  "user_ref": "u_3f9a",
  "consent_id": "c_2026_05_03_001",
  "backup_source": "google_drive",
  "drive_oauth_token": "ya29.a0Af..."
}

200 OK
{
  "binding_id": "bind_8c1e",
  "status": "active",
  "next_sync_at": "2026-05-04T02:00:00Z",
  "scopes": ["transactions:read", "budgets:read", "accounts:read"]
}

2. Fetch a transaction statement

GET /api/v1/moneymanager/transactions
  ?binding_id=bind_8c1e
  &from=2026-04-01&to=2026-04-30
  &account=KEB_HANA_CHECKING
  &currency=KRW
Authorization: Bearer <PARTNER_API_KEY>

200 OK
{
  "page": 1,
  "page_size": 100,
  "total": 184,
  "items": [
    {
      "id": "tx_0001",
      "ts": "2026-04-02T11:24:00+09:00",
      "type": "expense",
      "amount": 18500,
      "currency": "KRW",
      "account": "KEB_HANA_CHECKING",
      "category": "Food",
      "sub_category": "Cafe",
      "memo": "Morning coffee",
      "double_entry": {
        "debit": "Food:Cafe",
        "credit": "KEB_HANA_CHECKING"
      }
    }
  ]
}

3. Webhook on new backup

POST https://your-app.example.com/hooks/moneymanager
X-OFL-Signature: t=1714694400,v1=8b0c...
Content-Type: application/json

{
  "event": "backup.ingested",
  "binding_id": "bind_8c1e",
  "backup_id": "bk_2026_05_03",
  "summary": {
    "tx_added": 47,
    "tx_updated": 3,
    "budget_changes": 1,
    "currencies": ["KRW", "USD"]
  },
  "occurred_at": "2026-05-03T02:14:11Z"
}

// Verify with HMAC-SHA256 over the raw body using your shared secret.
// On 2xx response we mark the event delivered; otherwise we retry with
// exponential backoff up to 24h.

Compliance & privacy

Money Manager backups can carry granular spending behavior, so our integration treats every export as personal data under the EU GDPR and Korea's PIPA. We collect explicit, revocable user consent before reading any backup, scope tokens to the minimum endpoints needed, and ship a data-subject-access handler that can produce or delete a user's record on demand.

Where the integration also touches a regulated bank account (for example to reconcile a Money Manager ledger against a real statement), we layer on the PSD2 account information service pattern, including 90-day strong customer authentication renewal. Korean deployments additionally honor the Financial Services Commission's MyData accreditation rules where partners are licensed.

We never publish credentials, never persist Google Drive refresh tokens unencrypted, and rotate our HMAC webhook secrets on a 30-day cadence. Audit logs cover every read against a binding and are retained for the period your jurisdiction requires.

Data flow / architecture

The pipeline is intentionally short and inspectable:

1. Source. The user's Money Manager app writes a backup to Google Drive (daily/weekly) or exports an Excel file by hand.
2. Ingestion worker. Our worker authenticates with the user's Drive scope, downloads the new backup, and parses the sub-currency Excel schema or the JSON variant into a normalized ledger.
3. Storage. Records land in a partitioned PostgreSQL table keyed by binding and date, with row-level encryption on amount and memo fields.
4. API / webhooks. Partner systems either pull via the REST endpoints above or subscribe to backup.ingested, budget.exceeded, and recurring.due events.

About OpenFinance Lab

We are an independent studio focused on mobile fintech and OpenData API integration. Our engineers come from retail banking, payment gateways, mobile app reverse engineering, and cloud platform teams. We have shipped end-to-end integrations for personal-finance ledgers, neobanks, e-commerce ordering systems, and travel apps across Asia, Europe, and the Americas, working under both authorized partner agreements and documented public-data scenarios.

• Personal finance, neobank, and SME bookkeeping integrations
• Mobile protocol analysis and authorized data extraction
• Custom Python, Node.js, and Go SDKs with full test harnesses
• Compliance review against GDPR, PSD2, PIPA, and regional MyData regimes
• Source-code delivery from $300 — receive runnable API source and full documentation; pay after delivery upon satisfaction
• Pay-per-call API billing — access our hosted Money Manager endpoints and pay only per call, with no upfront cost

Contact

For quotes, sandbox access, or to submit your specific Money Manager integration requirements, open our contact page:

Contact page

We respond to most enquiries within one business day and can sign an NDA before reviewing technical scope.

Engagement workflow

1. Scope confirmation: which Money Manager data surfaces (transactions, budgets, accounts, card schedules) and which downstream systems.
2. Protocol & backup-format analysis (2–5 business days), including the 2024 sub-currency Excel schema and Wi-Fi PC Manager channel.
3. Build and internal validation against ledger balance invariants (3–8 business days).
4. Documentation, sample fixtures, Postman collection, and integration tests (1–2 business days).
5. First delivery typically lands in 5 to 15 business days; partner-side OAuth approvals may extend the timeline.

FAQ

Does Money Manager (Realbyte) provide an official public API?

What financial data can I extract from a Money Manager backup?

How long does the integration take and how is it priced?

Is the integration compliant with GDPR and other data protection laws?