SHPFCU To Go! API integration services (FDX / OpenBanking)

1. Authorization & session bridge

We replicate the SHPFCU To Go! login handshake (member number + password + device-bound MFA) into a stable OAuth 2.0 / token-refresh layer, so downstream services keep working even when the upstream app rotates session formats. Includes biometric re-auth hooks and SSL/TLS pinning notes.

2. Balance & share-account API

Single endpoint that returns all share IDs (S1, S2, club, IRA), checking, money market, certificate and loan balances with available vs. ledger split. Useful for personal-finance dashboards and treasury sweeps where members want one consolidated view.

3. Transaction & statement query API

Paginated, filterable transaction feed mapped to FDX field names (postedTimestamp, transactionType, amount, debitCreditMemo, payeeName, memo). Bulk PDF and OFX statement export for tax season, NCUA member statements, or accounting-software import (QuickBooks, Xero, Wave).

4. Transfers, A2A and Bill Pay

Internal transfers between SHPFCU shares, external A2A transfers to other US financial institutions, and Bill Pay payee CRUD with one-time and recurring schedules. Idempotency keys and webhook callbacks make reconciliation deterministic.

5. Remote Deposit Capture (mobile check)

Front/back image capture, MICR extraction, daily deposit limits enforcement, and status polling (received → in review → posted → cleared). Integrates with image-quality (IQA) checks recommended by FFIEC RDC guidance.

6. Locator & member-services

ATM and CO-OP shared-branch locator queries (lat/lng + radius), plus contact and member-services endpoints (secure messaging, card lock/unlock signals where authorized).

Scenario A — Accounting & bookkeeping sync

Business context: A member who runs a small business (or a tax preparer working on behalf of a member) wants SHPFCU checking and share-account activity to appear automatically in QuickBooks Online or Xero.

APIs involved: account list, transaction history (cursor-paginated by postedTimestamp), monthly statement PDF.

OpenFinance mapping: Plain FDX Accounts + Transactions resources, exported into the bookkeeping platform's bank-feed adapter.

Scenario B — PFM & cash-flow dashboards

Business context: A personal-finance app aggregates SHPFCU To Go! alongside a primary checking bank to show one unified spending view, including pending and recurring Bill Pay outflows.

APIs involved: balance, transaction feed with category enrichment, Bill Pay schedule list.

OpenFinance mapping: Member-permissioned data via FDX-aligned consent receipts; tokens scoped to read-only.

Scenario C — Income & deposit verification for lending

Business context: A mortgage or auto-loan underwriter needs 60–90 days of verified deposits and direct-deposit payroll lines for a SHPFCU member applying off-platform.

APIs involved: 90-day transaction history with payer name, statement PDF as evidence, balance snapshot.

OpenFinance mapping: Comparable to the Finicity / MX verification-of-asset (VOA) and verification-of-income (VOI) products, but sourced through SHPFCU's authorized member channel.

Scenario D — Treasury / payroll reconciliation

Business context: An employer or association that disburses to SHPFCU member accounts (common with State Highway Patrol payroll) needs deterministic confirmation that ACH credits posted.

APIs involved: transaction lookup by amount + date window, A2A status, webhook on posting.

OpenFinance mapping: Push notifications shaped like FDX events; idempotency keys keep retry logic safe.

Scenario E — Field deposit & back-office workflow

Business context: A member organization receives paper checks at remote events and wants to deposit them straight into a SHPFCU checking share, then post the cleared amount to a CRM or donor system.

APIs involved: Remote Deposit Capture submit, deposit status webhook, transaction posting confirmation.

OpenFinance mapping: mRDC submission flow with FFIEC IQA checks before image upload; cleared transaction event closes the loop.

1. Authorize and refresh a member session

POST /api/v1/shpfcu/auth/login
Content-Type: application/json

{
  "member_number": "********",
  "password": "********",
  "device_id": "8b3a-...-c12",
  "mfa": { "channel": "sms", "otp": "473921" }
}

200 OK
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rt_2f9c...",
  "expires_in": 900,
  "scope": "accounts:read transactions:read transfers:write rdc:write"
}

2. Statement & transaction query (FDX-shaped)

GET /api/v1/shpfcu/accounts/{accountId}/transactions
  ?fromDate=2026-01-01
  &toDate=2026-03-31
  &status=POSTED,PENDING
  &limit=200&cursor=eyJwYWdlIjoyfQ==
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "transactions": [
    {
      "transactionId": "tx_91c4...",
      "postedTimestamp": "2026-03-14T18:02:11Z",
      "amount": { "value": -42.18, "currency": "USD" },
      "debitCreditMemo": "DEBIT",
      "transactionType": "POS",
      "merchantName": "KROGER #318",
      "category": "GROCERIES",
      "memo": "Visa Debit"
    }
  ],
  "nextCursor": "eyJwYWdlIjozfQ=="
}

3. Mobile deposit + webhook callback

POST /api/v1/shpfcu/rdc/deposits
Authorization: Bearer <ACCESS_TOKEN>
Content-Type: multipart/form-data

fields: { account_id, amount: 250.00, idempotency_key }
files:  { front_image, back_image }

202 Accepted
{ "deposit_id": "dep_77a1...", "status": "RECEIVED" }

// Later, signed webhook to your endpoint:
POST https://your.api/webhooks/shpfcu
X-Signature: sha256=...
{
  "event": "rdc.deposit.cleared",
  "deposit_id": "dep_77a1...",
  "posted_transaction_id": "tx_91d8...",
  "cleared_amount": 250.00
}

Eastman Credit Union (Mobile Banking)

Tennessee-based CU with one of the highest-rated mobile apps in the US. Holds biometric login, smartwatch balance and standard transaction data — teams pulling unified PFM feeds often need a parallel SHPFCU + Eastman export.

Wright-Patt Credit Union (WPCU)

Ohio-based CU near SHPFCU's footprint, with strong mobile deposit and Popmoney P2P data. Combined with SHPFCU, gives Ohio member-employer payroll teams a shared transaction view.

Delta Community Credit Union

Georgia's largest credit union, Touch ID-driven flows, mobile deposit and bill-pay data; common counterpart for cross-state members.

ESL Federal Credit Union

Rochester, NY CU with a top-rated mobile app; same data shapes (balances, transactions, transfers) make multi-CU statement export straightforward.

Alliant Credit Union

Digital-first CU with balance preview and live in-app chat; dashboards that already pull Alliant frequently want SHPFCU appended for fuller household coverage.

Alternatives Federal Credit Union

Mobile check deposit, scheduled bill pay, and P2P payments — useful pairing for community-finance and CDFI integrations alongside SHPFCU.

CU SoCal Mobile Banking

Southern California CU with balance, transfer, deposit, bill-pay and CO-OP locator features — same shared-branch network as SHPFCU.

Redstone Federal Credit Union

Alabama-based CU with a widely-used mobile app; shows up alongside SHPFCU in cross-state public-sector member portfolios.

CO-OP Shared Branch & ATM Locator

Network app that powers the "Find Shared Branching" feature inside SHPFCU To Go!. Locator data merges naturally with SHPFCU's own ATM endpoint.

Auto-Owners Associates Credit Union

Mid-sized CU with a mobile app that also rides the CO-OP network, offering an analogous data surface for unified credit-union integrations.

Deliverables checklist

• OpenAPI 3.1 specification (JSON + YAML, FDX-aligned naming)
• Protocol & auth-flow report (login, MFA, refresh, signing)
• Runnable source: Python (FastAPI) or Node.js (Express/Fastify) reference server
• Sample clients: Python, Node, Go — covering balance, transactions, transfer, RDC
• Postman collection + automated pytest / vitest suite
• Compliance brief: GLBA, NCUA Part 748, FFIEC mRDC, NACHA notes
• Webhook signing keys, rotation playbook, and retry/backoff guidance

Engagement workflow

1. Scope confirmation: which screens / data types you actually need.
2. Protocol analysis & API design (2–5 business days).
3. Build & internal validation against authorized test accounts (3–8 business days).
4. Docs, sample apps, automated tests (1–2 business days).
5. Typical first delivery: 5–15 business days; deeper RDC + Bill Pay flows can extend.

FAQ

What do you need from me?

How long does delivery take?

How do you handle compliance?

About our studio

We are an independent technical studio focused on App interface integration and authorized API integration. Our team has deep, hands-on experience in mobile applications and fintech — banks, credit unions, payment gateways, protocol analysis, and cloud delivery. We routinely ship end-to-end financial APIs under security and compliance constraints relevant to the US OpenBanking landscape (FDX, NCUA, GLBA, NACHA) and to international markets.

• Fintech, retail banking, credit unions, payments and cross-border clearing
• Enterprise API gateways, security reviews, and consent-management flows
• Custom Python / Node.js / Go SDKs and automated test harnesses
• Full pipeline: protocol analysis → build → validation → compliance hand-off
• Source code delivery from $300 — receive runnable API source code and full documentation; pay after delivery upon satisfaction
• Pay-per-call API billing — access our hosted API and pay only per call, no upfront cost; ideal for teams that prefer usage-based pricing

Contact

For quotes or to submit your target app and requirements, open our contact page:

Contact page

Two engagement models: (1) source-code delivery from $300 — pay after delivery upon satisfaction; (2) pay-per-call billing on our hosted API endpoints, no upfront fee.