Connect The National Bank of Adams County (NBAC) to accounting, ERP and analytics — without waiting on a public portal
NBAC’s mobile app (package com.fdc.nbacwuohsub, published by an FDC-hosted core) does not yet expose a self-serve developer API. We close that gap by delivering protocol-level integration of the existing app endpoints, mapped to the Financial Data Exchange (FDX) schema so the data lands in your stack the same way Plaid or MX would deliver it.
- Valuable data inside the app: running balances, transaction history searchable by date / amount / check number, scheduled bill payments, payee directory, transfer ledger.
- Why it matters: small-business clients of NBAC need this data inside QuickBooks Online, Xero, Sage Intacct, Bill.com and custom treasury dashboards.
- Why now: the CFPB’s Section 1033 final rule (October 2024) makes account-data portability a consumer right; community banks under $10B in assets get a runway through 2030, so the demand window is open today.
What we deliver
Deliverables checklist
- OpenAPI 3.1 specification covering balance, transactions, transfers, bill pay and payees
- Authentication report: enrollment, password login, biometric session refresh, 2FA challenge handling
- Runnable client in Python and Node.js (TypeScript), with a Go variant on request
- FDX v6 mapper plus an OFX / QFX exporter ready for QuickBooks Desktop & Online
- Postman / Bruno collections, integration tests and a fixtures-only sandbox
- Compliance write-up covering Section 1033 readiness and Gramm–Leach–Bliley data-handling notes
Two ways to engage
Source-code delivery from $300. You receive runnable client code, the OpenAPI spec, the protocol report, and a fixtures sandbox. Payment is released after delivery once the test suite passes against your test account.
Pay-per-call hosted API. We operate the integration on our infrastructure, you call REST endpoints with a bearer token. Pricing is metered per successful call — no monthly minimum, no setup fee. Suited to teams that want to avoid running a long-lived crawler themselves.
Data available for integration
The table below maps every screen in the NBAC mobile app to a concrete data feed. Each feed is delivered with FDX-aligned field names so your downstream tooling does not need to learn a bank-specific dialect.
| Data type | Source screen / feature | Granularity | Typical use |
|---|---|---|---|
| Account list & balances | “Accounts” tab | Per-account, available + ledger, refreshed on call | Cash position dashboards, daily reconciliation |
| Transaction history | Account detail / search by date, amount, check # | Per-transaction with description, amount, posted date, check number | QuickBooks / Xero sync, expense categorization, audit |
| Internal transfers | “Transfers” flow | Per-transfer with debit account, credit account, amount, status | Sweep automation, intra-company funding |
| Scheduled bill payments | “Bill pay” module | Per-payment with payee, amount, scheduled date, status | AP automation, treasury forecasting |
| Payee directory | “Manage payees” | Per-payee with name, address, account hint, last-paid date | Vendor master sync, AP onboarding |
| Authorization events | Login + Touch ID / Face ID | Per-session, timestamped, device-tagged | Fraud monitoring, consent records for 1033 |
Typical integration scenarios
1. QuickBooks & Xero sync for NBAC small-business customers
NBAC serves small businesses across south-central Ohio that close their books in QuickBooks Online or Xero. We poll the transaction history endpoint nightly, deduplicate against a stored watermark, and push the result as either a Plaid-shaped JSON payload or an OFX 2.x file. The OFX path is what QuickBooks Desktop expects when a bank is missing from the Direct Connect catalog.
2. Multi-bank treasury dashboard
A regional CFO holds operating accounts at NBAC plus two other community banks. Each bank is wrapped in the same FDX Account + Transaction response shape, so the dashboard layer stays bank-agnostic. The transfer endpoint is used to sweep idle balances back to a primary operating account at end of day.
3. AP automation with the bill-pay module
An accounts-payable platform reads the payee directory, matches it against its vendor master, and creates new scheduled payments through the bill-pay endpoint. Status webhooks feed the platform’s payment-status board so finance teams stop refreshing the bank app to confirm clearance.
4. Loan-origination & cash-flow underwriting
A community lender consents-in to twelve months of NBAC transaction history, runs cash-flow underwriting models (revenue stability, NSF count, average daily balance), and stores the FDX-shaped feed for the duration of the loan. This mirrors the Plaid Assets / Income use case but runs on permissioned access negotiated with the customer.
5. Compliance & consent ledger
Every API call is logged with a consent identifier, scope, expiration and the originating user agent, producing the kind of audit trail Section 1033 authorized third parties are expected to keep. The same ledger is used to honor revocation: a single API call disables the data feed and clears cached tokens.
Technical implementation
Login & session bootstrap
POST /api/v1/nbac/session
Content-Type: application/json
{
"username": "<customer_id>",
"password": "<encrypted_blob>",
"device": {
"platform": "ios",
"app_version": "5.4.1",
"biometric": "face_id"
}
}
200 OK
{
"session_id": "sess_8c4d...",
"expires_at": "2026-05-01T18:30:00Z",
"mfa_required": false,
"scopes": ["accounts:read", "transactions:read", "billpay:write"]
}
Transaction history (FDX-shaped)
GET /api/v1/nbac/accounts/{account_id}/transactions
?from=2026-04-01&to=2026-04-30&min_amount=100&check_number=2041
Authorization: Bearer <SESSION_TOKEN>
200 OK
{
"accountId": "acct_3f2a",
"transactions": [
{
"transactionId": "tx_91f0",
"postedTimestamp": "2026-04-12T00:00:00Z",
"amount": -428.55,
"currency": "USD",
"description": "OHIO POWER BILL PAY",
"checkNumber": null,
"category": "utilities",
"status": "posted"
}
],
"page": {"next": null, "count": 1}
}
Schedule a bill payment + webhook
POST /api/v1/nbac/billpay
Authorization: Bearer <SESSION_TOKEN>
Idempotency-Key: 2026-04-30-vendor-1042
{
"payee_id": "payee_77",
"from_account": "acct_3f2a",
"amount": 1250.00,
"send_on": "2026-05-03",
"memo": "INV-1042"
}
201 Created
{ "payment_id": "pay_7af1", "status": "scheduled" }
// Status webhook (delivered to your endpoint)
POST /your-webhook
{
"event": "billpay.status_changed",
"payment_id": "pay_7af1",
"status": "sent",
"occurred_at": "2026-05-03T13:02:11Z"
}
Errors follow RFC 7807 problem-details: a type URI, title, status, and a detail string. Rate limits are returned via X-RateLimit-Remaining and the standard Retry-After header on 429 responses, so your client can back off without a custom protocol.
Compliance & privacy
Regulatory alignment
Integrations are scoped to the consumer-data rights under CFPB Section 1033 and the FDX standard the CFPB recognized as a standard-setting body in January 2025. We also follow Gramm–Leach–Bliley (GLBA) Safeguards Rule expectations on encryption, access controls and incident response, and we minimize collection to the fields the customer authorized.
Operational guardrails
- Customer consent captured up-front; revocable through a single API call.
- Tokens encrypted at rest with envelope encryption (KMS-issued data keys).
- No biometric template storage — Face ID / Touch ID stays device-local.
- PII redacted in logs; full payloads kept only in the customer’s own bucket.
- Quarterly access review and a 24-hour breach-notification SLA.
Data flow / architecture
The pipeline is intentionally short, so a community-bank scale of traffic does not require a heavyweight platform:
- Client app / browser — the customer authenticates and consents to scopes (accounts, transactions, bill pay).
- NBAC integration gateway — our service replays the post-biometric session, retrieves the requested screens, and normalizes to FDX field names.
- Storage — encrypted token vault plus an append-only consent and audit log; transactional data is cached for the smallest window the use case allows (often only the duration of one API call).
- Outbound — FDX JSON, OFX / QFX, CSV, or webhook events to your accounting tool, ERP, dashboard, or data warehouse.
Market positioning & user profile
The National Bank of Adams County is a long-standing community bank headquartered in West Union, Ohio, serving retail and small-business customers across south-central Ohio and the surrounding Appalachian counties. Its mobile app, distributed on Android and iOS by FIS-affiliated mobile-banking host FDC, mirrors the “NBAC online banking” experience and is offered free to existing online-banking customers. The user base skews toward established small businesses (farms, contractors, retail, professional services) and individual retail customers who want a single relationship for checking, savings, transfers and bill pay. Integration buyers are typically third-party fintechs, accounting platforms, or back-office tools that need to bring NBAC accounts into a portfolio they already serve at larger national banks.
Screenshots
Screens from the live Google Play listing — click any thumbnail for a larger view. Each screen is the source for one or more endpoints in the integration.
Similar apps & integration landscape
Buyers who integrate NBAC almost always integrate one or more of the apps below. We name them here so the broader ecosystem is visible in one place — we do not rank or compare them, only point out where the data overlaps.
- ACNB Bank Mobile App — Adams County National Bank in Pennsylvania. Same shape of accounts, transactions, transfers and bill pay; common companion when consolidating NBAC and ACNB customers in a single AP system.
- Adams County Bank (Nebraska) — another “Adams County” community bank with a mobile app on Android and iOS. Buyers searching for either institution often need a unified extract.
- CBNA Mobile Banking — Community Bank N.A. covers similar small-town markets in the Northeast; transaction-history exports tend to be the highest-value endpoint.
- ACB Mobile (Adams Community Bank) — Western Massachusetts community bank with an Android/iOS app; integrators frequently bundle ACB and NBAC pipelines.
- United Community Bank — a larger regional player whose customers often hold a secondary NBAC account; balance and transfer feeds are the main overlap.
- Commonwealth Bank (MA) — supported by Plaid for Assets, Auth and Balance; useful as a reference shape for what NBAC fields should look like in your downstream tooling.
- NextStep Federal Credit Union — a community-focused credit union; AP and personal-finance tools often want to mix CU and bank data in the same dashboard.
- First Merchants Mobile Banking — Midwest regional bank with a strong small-business presence in Ohio and Indiana; common alternative for customers comparing community vs. regional banks.
If you need a similar wrapper for any of the apps above, the same protocol-analysis workflow applies and the same FDX-shaped output schema is reused.
About OpenFinance Lab
We are an independent studio focused on mobile-app protocol analysis and OpenFinance integration. The team has shipped production integrations against retail banks, neobanks, payment platforms and brokerages, and we know the FDX, OFX, ISO 20022 and FAPI shapes downstream tools expect.
- Authorized integrations only — under customer consent or documented public APIs.
- Source-code delivery from $300 with a runnable client and full documentation; pay after delivery once acceptance tests pass.
- Hosted pay-per-call API for teams that prefer not to run a long-lived crawler in-house.
- Operate worldwide with a focus on US, EU and APAC fintech buyers.
Contact
Send us the target app, the data feeds you need, and your preferred output shape (FDX, Plaid-style, OFX/QFX, CSV). We’ll come back with a scope, timeline and a fixed price.
Engagement workflow
- Scope confirmation — data feeds, output schema, hosting model.
- Protocol analysis on a test account (2–5 business days).
- Build & internal validation against fixtures (3–7 business days).
- Acceptance testing on your account, plus documentation hand-off (1–2 business days).
- Optional: ongoing maintenance retainer for protocol-change monitoring.
FAQ
Does NBAC publish a public developer API?
Which data can you actually pull from the NBAC mobile app?
How do you handle Touch ID and Face ID?
Is this compatible with CFPB Section 1033 and FDX?
How long does first delivery take?
📱 Original app overview (appendix)
The National Bank of Adams County mobile banking app lets existing NBAC online-banking customers run day-to-day banking from a phone. It is offered free to enrolled customers and is published on Google Play under package com.fdc.nbacwuohsub.
Accounts: check the latest balance and search recent transactions by date, amount or check number.
Transfers: easily transfer cash between accounts you hold at NBAC.
Bill pay: schedule new payments and view recent ones.
Manage payees: add new payees, view existing ones, or delete payees directly from the mobile app.
Touch ID / Face ID: a more efficient sign-on experience using fingerprint or facial recognition, with biometric data staying device-local.
The app is part of the National Bank of Adams County’s online-banking suite alongside the web channel at nbaconline.com.