Kennebec Savings Bank API integration (OpenBanking / FDX)

Deliverables checklist

• OpenAPI 3.1 / Swagger specification, FDX 6.x field-mapped
• Protocol & auth flow report (session, MFA, device-binding)
• Runnable Python and Node.js reference implementations
• Pytest / Jest integration suites against a sandbox account
• Webhook receiver examples for transactions and RDC events
• Compliance pack: Section 1033 consent template, GLBA notes

Engagement workflow

1. Scope confirmation (1 day) — we list the exact data fields needed.
2. Protocol analysis & API design (2–5 business days)
3. Build & internal validation (3–8 business days)
4. Docs, samples, and test cases (1–2 business days)
5. UAT with your sandbox account; iterate on edge cases.

Two engagement models

Pick the model that fits how your team prefers to consume integrations:

• Source delivery from $300 — runnable source plus docs; pay after delivery on satisfaction.
• Pay-per-call API — call our hosted endpoints, settle on usage; no upfront commitment.

1. Small-business accounting sync

A Maine landscaper running QuickBooks Online wants Kennebec checking transactions to land in their books within an hour. We schedule a poll against the transactions endpoint, normalise descriptions, and post into the QBO Bank Feeds API. Field mapping: txn.id→QBO.TransferTxnRef, txn.amount→QBO.Amount, txn.merchant→QBO.PayeeRef. Result: nightly reconciliation removed, ~6 hours/week saved per bookkeeper.

2. PFM dashboard / aggregator onboarding

A net-worth app needs Kennebec balances under the new Section 1033 framework. We wrap the consumer login, exchange the bank session for an FDX-format AccountDescriptors list, and emit FDX Transactions messages on demand. Mapping is 1:1 with the FDX 6.x core schema so downstream code does not branch by institution.

3. Treasury cash position for a multi-branch nonprofit

A nonprofit with seven sub-accounts at the bank polls a single /positions endpoint each morning. We aggregate available + pending balances per account, push to a Google Sheet via the Sheets API, and alert on Slack if any account falls below a threshold. The data path stays read-only and consent is logged for every poll.

4. Accounts-receivable mobile check deposit

A regional contractor receives paper checks at job sites. The internal field app calls our RDC wrapper with front/back image base64 + amount, we forward to the bank's mobile-deposit pipeline, and webhook back with rdc.status = accepted | held | rejected. AR auto-creates the deposit voucher and applies it to the invoice.

5. Tax-season statement bundle

A CPA firm pulls 12 months of .qbo and PDF statements for 80+ business clients in January. We script the /statements?from=...&to=... endpoint per client and assemble a per-client folder. The same export feeds a lender's underwriting workflow for SBA review packets.

Auth: token exchange

// 1. Authenticate & obtain an access token
POST /api/v1/ksb/auth/login
Content-Type: application/json

{
  "username": "<encrypted>",
  "password": "<encrypted>",
  "device_id": "uuid-v4",
  "mfa_token": "123456"        // OTP / push step
}

200 OK
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rt_...",
  "expires_in": 1800,
  "fdx_consent_id": "cns_2026_..."
}

Statement query (FDX-shaped)

POST /api/v1/ksb/statement
Authorization: Bearer <ACCESS_TOKEN>
X-FDX-Consent-Id: cns_2026_...

{
  "account_id": "acct_84..3921",
  "from_date": "2026-04-01",
  "to_date":   "2026-04-30",
  "format":    "json"          // or qbo | qfx | ofx | csv
}

200 OK
{
  "account_id": "acct_84..3921",
  "page": 1, "page_size": 50,
  "transactions": [
    {
      "id": "txn_8c...",
      "post_date": "2026-04-15",
      "amount": -42.30,
      "currency": "USD",
      "description": "HANNAFORD #8412",
      "category": "groceries",
      "balance_after": 4831.07
    }
  ]
}

Mobile deposit (RDC) webhook

POST /api/v1/ksb/deposit/check
Authorization: Bearer <ACCESS_TOKEN>

{
  "account_id": "acct_84..3921",
  "amount":  1250.00,
  "currency":"USD",
  "front_image_b64": "...",
  "back_image_b64":  "...",
  "client_ref": "INV-2026-0418-01"
}

202 Accepted
{ "rdc_id": "rdc_9f...", "status": "received" }

// Later, your webhook endpoint receives:
{
  "event": "rdc.posted",
  "rdc_id": "rdc_9f...",
  "status": "accepted",
  "hold_release_date": "2026-04-20",
  "client_ref": "INV-2026-0418-01"
}

What we follow

Kennebec Savings Bank is a state-chartered mutual savings bank and an FDIC member; consumer data access falls under the CFPB Section 1033 Personal Financial Data Rights rule. We align technical flows with the Financial Data Exchange (FDX) 6.x specification, which the CFPB recognised as a standard-setting body in 2025 and which now powers more than 114 million US customer data connections. On top of that we apply the GLBA Safeguards Rule, log every consent grant, and follow the bank's own privacy notice.

Operational guardrails

• Authorized API access only — user-consented or published endpoints.
• Data minimisation: pull only fields the downstream needs.
• Per-consent expiry and revocation; webhook on revoke.
• Encrypted secrets at rest (AES-256) and in transit (TLS 1.3).
• Audit log of every API call, retained for 7 years.
• NDAs signed on request; SOC 2-style change controls.

About us

We are an independent studio focused on fintech and open-data API integration. Our engineers come from banks, payment networks, mobile-app reverse engineering, and cloud platforms. We have shipped FDX-aligned, Section 1033-aware integrations for community banks, credit unions, and aggregators, and we know how to translate a marketing screen in a banking app into a clean REST endpoint your team can rely on.

• Community banking, payments, lending, and wealth-management stacks
• Enterprise API gateways and security reviews
• Python / Node.js / Go SDKs and test harnesses
• End-to-end pipeline: protocol analysis → build → validation → compliance
• Source code delivery from $300 — pay after delivery on satisfaction.
• Pay-per-call API — usage-based billing, no upfront commitment.

Contact

Send us the target app, the data fields you need, and your preferred delivery model. We reply within one business day with a quote and timeline.

Open the contact page

FAQ

What do you need from me to integrate Kennebec Savings Bank?

How long does delivery take for a community-bank integration?

How do you handle compliance and consumer data rights?

Can you connect Kennebec Savings Bank to QuickBooks, Quicken, or a custom ERP?

Why teams ask for this

Community-bank data is a long-tail problem: aggregators cover the big four well, but coverage for institutions like Kennebec Savings Bank can be thin, brittle, or limited to balance + transaction reads. Teams that need mobile deposit posting, bill-pay scheduling, or full FDX 6.x transaction shapes find the gap fastest at tax season, audit windows, and grant-reporting deadlines. We build the missing layer once, document it, and hand it over.