Texhillco School Employees FCU API integration

Deliverables checklist

• OpenAPI 3.1 specification for login, balances, transactions, RDC and bill pay
• Protocol report: request signing, dynamic API keys, cookie chain, MFA path
• Runnable reference client in Python and Node.js (typed, with retries and pagination)
• Postman / Bruno collection plus pytest / vitest integration suite
• Section 1033 consent log schema and revocation endpoint
• Deployment notes for AWS, GCP and on-prem reverse proxies

Why the data behind this app matters

Texhillco SEFCU serves school employees in Kerrville and the surrounding Hill Country counties. Members are typically dual-income households with payroll direct deposit, periodic vehicle and home-equity loans, and seasonal savings activity. That makes the underlying data set unusually clean: payroll cadence, recurring deductions and stable employer codes are all signals that consumer-finance, lending and compliance vendors will pay to access — provided the member explicitly consents.

1. Cross-bank PFM dashboard for educators

A Texas-focused budgeting app wants to show teachers their full payroll picture across Texhillco SEFCU and a side checking account. We expose a member-authorized read API (balances + 12 months of transactions) and emit OFX-compatible exports the dashboard ingests every 24 hours. Maps to the OpenBanking pattern of consent-driven account data sharing under CFPB Section 1033.

2. Lending pre-qualification with balance proof

An auto-loan partner needs payroll-deposit evidence and a clean 60-day balance trend. The integration returns a signed snapshot (member-authorized) including direct-deposit cadence and average daily balance, so the lender skips manual statement uploads. Mirrors what aggregators like Plaid Income and Finicity Verification of Assets provide for larger banks.

3. RDC anti-fraud webhook

The credit union (or its core processor) wants to push every mobile check deposit to a fraud scoring service. We wrap RDC events into a webhook with image hash, amount and member ID; the scoring service returns hold or release within 800 ms. Latency budget and retry semantics are documented; nothing is buffered to disk.

4. Accounting sync for member-owned small businesses

Many SEFCU members run side businesses (tutoring, summer camps, coaching). Their bookkeepers want a one-click feed into QuickBooks Online or Xero. We deliver a CUFX-aligned transactions endpoint plus a small ETL that maps SEFCU posting codes to the accounting platform's chart-of-accounts hints.

5. Compliance evidence pack

Auditors increasingly ask for an evidence trail of consent, access scope, retention and revocation. The integration ships with a consent log table and an admin endpoint that lists every active and revoked permission, ready for NCUA examiners and Section 1033 reporting.

Login & token issuance

// Step 1 — issue a session-bound member token
POST /api/v1/texhillco/auth/login
Content-Type: application/json

{
  "member_id": "1234567",
  "password": "<hashed_member_secret>",
  "device_fingerprint": "a1f3...e2",
  "mfa_token": "823910"
}

200 OK
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rt_8f...",
  "expires_in": 1800,
  "scope": ["balances","transactions","rdc","billpay"]
}

Statement export

POST /api/v1/texhillco/statement
Authorization: Bearer <ACCESS_TOKEN>

{
  "account_id": "S0010",
  "from_date": "2026-01-01",
  "to_date":   "2026-04-30",
  "format":    "json",
  "page":      1,
  "page_size": 200
}

200 OK
{
  "account_id": "S0010",
  "currency": "USD",
  "opening_balance": 1843.22,
  "closing_balance": 2117.06,
  "transactions": [
    {"id":"tx_001","date":"2026-01-03","amount":-42.18,
     "merchant":"HEB #482","mcc":"5411","status":"posted","running":1801.04},
    {"id":"tx_002","date":"2026-01-15","amount": 2150.00,
     "type":"ACH_CREDIT","desc":"PAYROLL ISD","status":"posted","running":3951.04}
  ],
  "next_page": null
}

Mobile check deposit webhook

POST https://your-host/hooks/texhillco/rdc
X-OFL-Signature: t=1715240120,v1=8b2c...
Content-Type: application/json

{
  "event": "rdc.deposit.accepted",
  "member_id": "1234567",
  "deposit_id": "rdc_2026050900014",
  "amount": 487.50,
  "image_sha256": "9a3c...",
  "hold_release": "2026-05-12",
  "channel": "ios",
  "received_at": "2026-05-09T14:18:42Z"
}

Errors return JSON with error.code and error.retry_after; clients should back off exponentially up to 60 s.

Regulatory alignment

Texhillco SEFCU is a US federally chartered credit union, so any data integration must respect the GLBA Safeguards Rule, NCUA cybersecurity expectations, and the CFPB's Personal Financial Data Rights framework under Section 1033 of the Consumer Financial Protection Act. The Section 1033 final rule was published in late 2024 and is presently undergoing reconsideration following an August 2025 ANPR; our patterns are designed to forward-port to whichever final shape the rule takes.

Operational controls

• Member-authorized OAuth-style scopes; no shared admin keys
• Dynamic, short-lived API credentials in the spirit of the It's Me 247 dynamic-key model
• PII redaction in logs; image hashes instead of raw RDC images for downstream services
• Encrypted at rest (AES-256) and in transit (TLS 1.3); customer-controlled KMS optional
• Quarterly access reviews and a documented Section 1033-ready consent revocation flow

About OpenFinance Lab

We are an independent studio focused on mobile-app protocol analysis and authorized API integration for fintech, banking and credit-union software. Our engineers come from core banking, payment switching, and OpenBanking aggregator backgrounds, and have shipped read-and-write integrations against It's Me 247, Jack Henry Symitar, Fiserv DNA, Plaid, MX and Finicity.

• Credit unions, community banks, lenders and PFM apps as recurring clients
• Multi-region delivery: US, EU and APAC time zones covered
• Custom Python / Node.js / Go SDKs and test harnesses, never a black box
• Full pipeline: protocol analysis → build → validation → compliance
• Source-code delivery from $300 — receive runnable API source plus full docs; pay after delivery upon satisfaction
• Pay-per-call API billing — access our hosted endpoints and pay only per call, no upfront cost

Contact

Send your target app and the data you want to surface — we reply with scope, timeline and a fixed quote within one business day.

Contact page

Engagement workflow

1. Scope confirmation: which Texhillco surfaces (login, balances, transactions, RDC, bill pay) and which downstream consumer.
2. Protocol analysis and OpenAPI design (2–5 business days).
3. Build, internal validation and consent-log wiring (3–8 business days).
4. Documentation, sample apps, Postman collection and pytest suite (1–2 business days).
5. First delivery 5–15 business days; aggregator certification or NCUA-style review may extend this.

FAQ

What do you need from me to start a Texhillco SEFCU integration?

How long does delivery take for a small credit union app?

How do you handle compliance and member privacy?