Connect Clear Fork Bank balances, statements and bill-pay to your stack — under documented authorization
Clear Fork Bank (formerly First National Bank Albany/Breckenridge, founded 1883) is one of the oldest privately-owned banks in Texas, with roughly $840 million in assets and branches across Albany, Breckenridge, Abilene, Gordon, Strawn and Mineral Wells. Its Android package com.fdc.fnbatxsub and iOS app id 694855155 sit on top of an FDC/Fiserv community-banking core, the same vendor stack used by hundreds of US community banks. That makes the structured account, transaction and bill-pay data surfaced in the app a strong candidate for OpenBanking-style integration.
What we deliver
Deliverables checklist
- OpenAPI 3.1 specification for balance, transactions, transfers and bill-pay endpoints
- Protocol and auth-flow report (login challenge, MFA, device binding, token refresh)
- Runnable reference clients in Python (httpx + pydantic) and Node.js (axios + zod)
- Postman collection with sandbox examples and replayable fixtures
- Test plan with golden-path, error-path and reconciliation cases
- Compliance notes covering CFPB 1033, GLBA Safeguards and FFIEC guidance
Engagement options
- Source code delivery from $300 — runnable API source plus documentation; pay only after acceptance.
- Pay-per-call hosted API — call our managed endpoints, no upfront fee, useful for small accounting tools and prototypes.
- Scoped retainer — for shops integrating multiple Texas community banks, we re-use the auth and parsing layer to reduce per-bank cost.
Data available for integration
The Clear Fork Bank app exposes a focused but high-value data surface. The table below maps each data object to the screen it originates from, the granularity that can be retrieved, and a typical downstream use that customers actually pay for. Field names are illustrative — final names track whatever the FDC/Fiserv core returns once protocol analysis is complete.
| Data type | Source screen / feature | Granularity | Typical use |
|---|---|---|---|
| Account profile | Accounts list | Per account: nickname, masked number, type, status, owner role | KYC enrichment, multi-account dashboards |
| Available & ledger balance | Account detail / dashboard | Per account, refreshed on demand | Liquidity monitoring, cash-flow forecasting |
| Transaction history | Transaction search (date / amount / check number) | Per transaction: posted date, amount, type, memo, check #, running balance | Accounting sync, reconciliation, expense categorization |
| Internal transfers | Transfers | Source/destination, amount, scheduled vs. immediate, status | Sweep automation, treasury operations |
| Bill payments | Bill Pay (recent + scheduled) | Payee, amount, scheduled date, posted date, status, confirmation # | AP automation, payee master, exception alerts |
| Session & device binding | Touch ID / Face ID sign-on | Token TTL, device fingerprint, MFA factor | Risk scoring, compliant headless integration |
| Statements & check images | Online services portal (linked from app) | PDF statements, check image URLs | Audit trails, lender document collection |
Typical integration scenarios
1. Accounting & ERP sync for West Texas SMBs
Many Clear Fork Bank business customers are ranchers, oil-services firms and contractors running QuickBooks Online or Xero. The integration polls the transaction history endpoint nightly, normalizes posted entries to the customer's chart of accounts, and pushes them into the ERP through OAuth. This maps the Clear Fork Bank statement export pattern onto a standard OpenBanking transaction feed.
2. Cash-position roll-up across branches
A finance officer that runs accounts in Albany and Mineral Wells calls the balance endpoint every fifteen minutes during business hours. The integration aggregates available balances, exposes them as a single dashboard tile, and triggers an alert when concentration risk crosses a threshold. The data flow stays inside the customer's tenant — the studio never persists balances on shared infrastructure.
3. Bill-pay automation as AP backbone
The bill-pay scheduling endpoint is wrapped behind an internal "pay vendor" service. When AP approves a vendor invoice, the service files a scheduled payment, captures the confirmation number, and writes both the scheduled and posted records back to the ERP. Idempotency keys prevent duplicate payments after retries — a recurring failure mode in custom community-bank scrapers.
4. Lender income & asset verification
For mortgage and small-business lenders, transaction history and check-image links replace the back-and-forth of emailing PDF statements. The export ships as a signed JSON bundle (similar to how Finicity Verify packages data) with a 12-month transaction window and account-ownership attestation, accelerating underwriting for community-bank customers.
5. Fraud monitoring & consent revocation
An anti-fraud workflow listens for unusual posted transactions through a webhook bridge and cross-references them against device-binding metadata captured at login. If the consumer revokes consent through the bank's app, the integration's refresh-token grant is invalidated within minutes, keeping the consent posture aligned with CFPB 1033 expectations.
Technical implementation
Below are illustrative request and response shapes. Final names follow the upstream FDC/Fiserv responses uncovered during protocol analysis. Each call is wrapped behind our gateway so the client never holds raw bank session cookies.
Auth — challenge & token issue
POST /v1/clearfork/auth/login
Content-Type: application/json
{
"username": "user@example.com",
"credential": "<encrypted>",
"device_id": "ios-694855155-9f3a",
"factor_hint": "biometric"
}
200 OK
{
"access_token": "eyJhbGciOi...",
"refresh_token": "rtk_...",
"expires_in": 900,
"mfa_required": false,
"session_scope": ["accounts:read","tx:read","billpay:write"]
}
Statement query — search by date / amount / check #
POST /v1/clearfork/statement
Authorization: Bearer <ACCESS_TOKEN>
{
"account_id": "ckfk_chk_4823",
"from_date": "2026-01-01",
"to_date": "2026-04-30",
"filters": {
"min_amount": 50.00,
"check_number": null,
"type": ["debit","credit","check"]
},
"page": 1, "page_size": 100
}
200 OK
{
"account_id": "ckfk_chk_4823",
"available_balance": 12840.55,
"ledger_balance": 13120.10,
"transactions": [
{"posted_at":"2026-04-29","amount":-128.43,"type":"debit","memo":"HEB #382","check_number":null},
{"posted_at":"2026-04-28","amount": 3500.0,"type":"credit","memo":"ACH PAYROLL"},
{"posted_at":"2026-04-27","amount":-450.00,"type":"check","check_number":"1042"}
],
"page": 1, "has_more": true
}
Bill pay — schedule a payment with idempotency
POST /v1/clearfork/billpay/schedule
Authorization: Bearer <ACCESS_TOKEN>
Idempotency-Key: ap-2026-04-30-inv-7781
{
"from_account": "ckfk_chk_4823",
"payee_id": "payee_oncor_electric",
"amount": 214.80,
"send_on": "2026-05-05",
"memo": "INV-7781"
}
201 Created
{
"billpay_id": "bp_01HX5...",
"status": "scheduled",
"confirmation_number": "CF-7841902",
"estimated_post_date": "2026-05-06"
}
Webhook — posted-transaction event
POST https://customer.example.com/webhooks/clearfork
X-Signature: t=1714600000,v1=hmac-sha256...
{
"event": "transaction.posted",
"account_id": "ckfk_chk_4823",
"transaction": {
"id": "tx_01HX...",
"posted_at": "2026-05-02T13:42:11Z",
"amount": -89.10,
"memo": "BUC-EE'S 13"
},
"consent_id": "cns_01HW...",
"delivery_attempt": 1
}
Compliance & privacy
Regulatory alignment
Clear Fork Bank, National Association is an OCC-chartered FDIC-insured institution, so its consumer data sharing falls under the CFPB Section 1033 Personal Financial Data Rights framework. The 1033 Final Rule was published October 2024, took effect January 17, 2025, and is being reconsidered through an Advance Notice of Proposed Rulemaking issued in August 2025. Our deliverables track that file: every change in the rule's scope, fee posture or representative definition is reflected in updated consent templates.
We additionally align with GLBA Safeguards Rule controls, FFIEC IT Examination Handbook expectations for third-party access, and standard NACHA operating rules where ACH-style transfers are involved. Read-only integrations strongly prefer aggregator-style consent and tokenization to direct credential sharing.
Privacy posture
- Data minimization: we only request the scopes the customer's use case actually needs
- Consent records: each authorization stores subject, scope, expiry and revocation handle
- Encryption: TLS 1.2+ in transit, AES-256 at rest, field-level encryption for account numbers
- Retention: tunable from "never persist" (proxy mode) to capped windows for reconciliation
- Audit logs streamed to the customer's SIEM, not retained on our shared infrastructure
Data flow & architecture
The data path is intentionally short to keep latency and the audit surface small:
- Clear Fork Bank app / FDC core — source of truth for accounts, balances, transactions and bill-pay state.
- OpenFinance Lab gateway — handles auth, MFA, token refresh, idempotency, request shaping and signature verification.
- Normalization layer — converts vendor responses to a stable schema (ISO-4217 currencies, ISO-8601 timestamps, signed amounts).
- Customer destination — your ERP, BI warehouse, lending platform, or hosted endpoint; delivered via REST pull or webhook push.
The pipeline is stateless by default. When a customer needs replay or backfill, we add a short-TTL store inside their tenant rather than a shared multi-tenant cache, so a request from an Albany branch never co-mingles with anyone else's transactions.
Market positioning & user profile
Clear Fork Bank serves consumers and small-to-mid-sized businesses across Shackelford, Stephens, Taylor, Palo Pinto and surrounding counties — a profile of West Texas agriculture, energy services, retail and professional firms. The mobile app runs on Android and iOS and is positioned as a workhorse account-management tool rather than a fintech super-app: balance, transaction search, transfer, bill pay, biometric login. That focus is exactly the surface most OpenBanking buyers want — accountants, lenders, AP automation vendors and treasury teams need clean, dated, reconciled data, not gamified UI. Integration buyers in this region are usually B2B fintechs, multi-entity SMBs and lenders building cash-flow underwriting on Texas community-bank deposits.
App screenshots
Tap any thumbnail to enlarge. Screenshots are from the official Google Play listing and are shown for reference only.
Similar apps & integration landscape
Clear Fork Bank sits inside a broader Texas community-banking ecosystem. Customers integrating one bank usually need at least one or two peers covered, and the same FDC/Fiserv or Jack Henry Banno auth patterns often re-apply. The apps below are listed only to describe the landscape — not to rank or critique them.
About OpenFinance Lab
OpenFinance Lab is an independent technical studio focused on mobile-banking protocol analysis and OpenBanking-style API integration. Our team includes engineers from US community-bank technology vendors, fintech aggregators, payments processors and cloud security. We have shipped integrations against FDC/Fiserv, Jack Henry Banno and FIS digital banking surfaces for community-bank workloads, and we treat compliance, consent and audit logging as core deliverables rather than afterthoughts.
For overseas teams: we deliver English documentation, work in your time zone for daily standups when needed, and sign mutual NDAs before any protocol material is shared. Our practice is concentrated in financial services — banking, payments, lending, insurance — with adjacent work in e-commerce and travel where transaction data overlaps.
- Source code delivery from $300 — runnable API code plus full documentation; pay only after acceptance.
- Pay-per-call hosted API — no upfront cost, ideal for prototypes and small volumes.
- Custom Python / Node.js / Go SDKs and reusable test harnesses.
- End-to-end pipeline: protocol analysis → build → validation → compliance review.
Contact
Send us the target app (Clear Fork Bank, package com.fdc.fnbatxsub), the data scope you need, and the system you want to feed. We will scope a fixed-price drop or a pay-per-call quote within one business day.
Engagement workflow
- Scope confirmation: which Clear Fork Bank objects (balance, transactions, bill pay, transfers) and which downstream system.
- Authorized protocol analysis: 2–5 business days, depending on MFA and device-binding complexity.
- API build and internal validation: 3–8 business days, including idempotency and retry tests.
- Documentation, OpenAPI spec, Postman collection and sample clients: 1–2 business days.
- Typical first delivery: 5–15 business days. Bank-side approvals or sandbox provisioning may extend timelines.
FAQ
What do you need from me to start a Clear Fork Bank integration?
How long does delivery take for a community bank like Clear Fork Bank?
How do you handle CFPB 1033 and consumer consent?
Can the same integration cover other Texas community banks?
📱 Original app overview (appendix)
Clear Fork Bank is the official mobile banking app for Clear Fork Bank, National Association — formerly First National Bank Albany/Breckenridge. The bank traces its roots to 1883 and is one of the oldest privately-owned banks in Texas, with approximately $840 million in assets and branches in Albany, Breckenridge, Abilene, Gordon, Strawn and Mineral Wells. The app is published under package com.fdc.fnbatxsub on Google Play and as app id 694855155 on the App Store, and runs on the FDC/Fiserv community-banking core.
According to the official description, available features include:
- Accounts — Check your latest account balance and search recent transactions by date, amount, or check number.
- Transfers — Easily transfer cash between your accounts.
- Bill Pay — Make payments and view recent and scheduled payments.
- Touch ID / Face ID — Sign on more efficiently using fingerprint or facial recognition.
This page describes how Clear Fork Bank's data surface can be exposed through OpenBanking-style APIs under documented authorization. It is not affiliated with, endorsed by or sponsored by Clear Fork Bank, N.A., and does not provide banking services. Trademarks belong to their respective owners.