Five Lakes API integration services (debt resolution & OpenFinance)

Deliverables checklist

• OpenAPI 3.1 specification covering login, enrolled debts, trust ledger and scheduled activity
• Protocol report: TLS pinning, request signing, token refresh, replay-protection details captured during analysis
• Runnable client source for login + statement endpoints in Python (httpx) and Node.js (undici)
• Webhook receiver template that normalizes scheduled-activity events into a tabular ledger
• Compliance pack: consent-record schema, retention policy template, CFPB / FTC alignment notes

Engagement models

• Source-code delivery — from $300. You receive the runnable code, OpenAPI spec, and tests; pay only after delivery and acceptance.
• Pay-per-call hosted API. Skip the build entirely and call our hosted Five Lakes endpoints. No upfront fee; usage-based billing per successful response.
• Optional white-label SDK packaging for embedding inside accounting, CRM, or financial-coaching products.

1. Household financial dashboard

A personal-finance product (think a YNAB-style budgeting app or a financial-coach SaaS) wants to surface the enrolled-debt balance and the next scheduled draft alongside the user's bank balances. The Five Lakes integration provides a daily pull of /v1/debts for portfolio totals and a webhook subscription for scheduled.activity.upcoming so the dashboard can warn about insufficient-funds risk three days before the draft hits.

2. Bookkeeping & reconciliation

An accounting integrator pushes the trust ledger into QuickBooks or Xero through an accounting-API aggregator. Each Five Lakes trust-ledger entry becomes a journal line tagged by transaction type — deposit, program fee, attorney fee, or settlement disbursement — so the consumer's tax preparer can reconcile what was paid into the program and what reached creditors.

3. Underwriting & risk control

A lender evaluating a borrower in active debt resolution requests, with explicit consent, a snapshot of /v1/debts?status=active and the projected_completion_date field. Combined with a credit-bureau pull, the lender models when the borrower will exit the program — material context the bureau file alone does not surface.

4. Compliance evidence locker

Law firms operating in the debt-relief space need durable evidence that each settlement was reviewed and accepted by the client. The integration captures every settlement.offer.accepted webhook with the original offer document and a hashed audit log, satisfying recordkeeping expectations under the FTC Telemarketing Sales Rule's debt-relief amendments.

5. Customer-success & retention

A debt-resolution operations team mirrors the scheduled-activity stream into its CRM. When a draft fails or a settlement gets rescheduled, an automation creates an outreach task within minutes — instead of waiting for the consumer to log in to the app and discover the problem themselves.

Login & session bootstrap (Python)

# pip install httpx
import httpx, time, hashlib

def login(email: str, password: str, device_id: str) -> dict:
    body = {
        "email": email,
        "password": password,
        "device_id": device_id,
        "client": "com.fivelakes",
        "ts": int(time.time()),
    }
    sig = hashlib.sha256(
        f"{body['email']}|{body['ts']}|{device_id}".encode()
    ).hexdigest()
    r = httpx.post(
        "https://api.openfinance-lab.com/v1/fivelakes/auth/login",
        headers={"X-Signature": sig},
        json=body,
        timeout=20,
    )
    r.raise_for_status()
    return r.json()  # { access_token, refresh_token, expires_in, user_id }

Trust ledger query (HTTP)

GET /v1/fivelakes/trust-account/ledger
  ?from=2026-01-01
  &to=2026-04-30
  &type=deposit,settlement
  &cursor=eyJwYWdlIjoyfQ HTTP/1.1
Host: api.openfinance-lab.com
Authorization: Bearer <ACCESS_TOKEN>
Accept: application/json

200 OK
{
  "items": [
    {
      "txn_id": "fl_trust_8e91...",
      "posted_at": "2026-04-12T14:03:00Z",
      "type": "deposit",
      "amount": 412.00,
      "currency": "USD",
      "running_balance": 3270.50,
      "memo": "Scheduled program draft"
    },
    {
      "txn_id": "fl_trust_8eaa...",
      "posted_at": "2026-04-18T09:11:00Z",
      "type": "settlement",
      "amount": -1850.00,
      "currency": "USD",
      "creditor": "Capital One N.A.",
      "running_balance": 1420.50,
      "settlement_id": "fl_settle_2207..."
    }
  ],
  "next_cursor": "eyJwYWdlIjozfQ"
}

Scheduled-activity webhook (Node.js)

// npm i fastify
import Fastify from 'fastify';
import crypto from 'node:crypto';

const app = Fastify();
const SECRET = process.env.FIVELAKES_HOOK_SECRET;

app.post('/webhooks/fivelakes', async (req, reply) => {
  const sig = req.headers['x-fl-signature'];
  const expected = crypto
    .createHmac('sha256', SECRET)
    .update(JSON.stringify(req.body))
    .digest('hex');
  if (sig !== expected) return reply.code(401).send();

  const evt = req.body;
  // evt.type: scheduled.activity.upcoming | settlement.offer.created
  //         | trust.ledger.posted     | debt.status.changed
  await persist(evt);
  return reply.code(204).send();
});

app.listen({ port: 8787 });

US debt-relief rules

Five Lakes Law Group operates as a debt-resolution law firm in the United States, so any integration must respect the Federal Trade Commission's Telemarketing Sales Rule debt-relief amendments and the consumer-protection guidance issued by the Consumer Financial Protection Bureau. The CFPB and FTC together brought nine debt-collection and debt-settlement enforcement actions in 2024 alone — a clear signal that consumer-funds handling, fee disclosure, and consent records are scrutinized.

Data minimization & retention

Our default client only persists the fields required for the stated use. Personally identifying data (full name, SSN fragments, full account numbers) is masked at ingest. The raw payload is held in a short-lived encrypted buffer; downstream services receive a minimized projection. Consent grants and revocations are written to an append-only ledger so a consumer can prove, after the fact, that their permission was scoped.

Trust-account handling

Funds shown in the Five Lakes app sit in a dedicated, third-party-administered consumer account. The integration never moves money on its own. Read-only ledger pulls are clearly distinguished from any approval-style write that the client might enable, and the on-page consent screen restates that distinction in plain language before the user authorizes the connection.

Authorization model

We do not bypass authentication. The integration runs against credentials the consumer provides, or under a documented partner permission granted by the firm. Sessions follow OAuth 2.0-style refresh patterns with short-lived access tokens, and a kill-switch lets the consumer or the firm revoke access at any time — the API responds with consent_revoked and stops serving data immediately.

About OpenFinance Lab

We are an independent technical studio specializing in mobile app interface integration and authorized API delivery for fintech, debt resolution, payments, and OpenBanking surfaces. Our engineers come from banks, payment gateways, and consumer-fintech backgrounds, and we routinely work with US regulators' guidance, EU PSD2 patterns, and APAC equivalents.

• End-to-end pipeline: protocol analysis → API design → implementation → QA → compliance documentation
• Python, Node.js, Go, and Kotlin client SDKs with realistic integration tests
• Source-code delivery from $300, with payment after acceptance, or hosted pay-per-call API
• NDA on request; written scope & deliverables before any engagement begins

Contact

To request a quote or share your integration requirements for the Five Lakes app, open the contact page below — please include the data domains you care about (enrolled debts, trust ledger, scheduled activity) and your preferred engagement model.

Open the contact page

Engagement workflow

1. Scope confirmation: which Five Lakes domains (enrolled debts, trust ledger, scheduled activity, settlement offers, document vault) you need.
2. Protocol analysis & API design (2–5 business days).
3. Build and internal validation (3–8 business days).
4. Documentation, sample clients, and integration tests (1–2 business days).
5. First usable delivery: 5–15 business days; webhooks and write-back flows may add a week.

FAQ

What information do I need to provide to start a Five Lakes integration?

How long does a Five Lakes API delivery take?

How do you keep Five Lakes integrations compliant with US debt-relief rules?

Can the integration write back into Five Lakes, or is it read-only?