Wymar Federal Credit Union API & OpenBanking integration

Member login & MFA

An authenticated session layer that wraps the It's Me 247 login challenge. Members consent once; the integration stores a refreshable token and replays MFA challenges only when CU*Answers requires step-up. Used by personal-finance dashboards that want a stable connection without daily re-auth friction.

Balance & account list

One call returns every share, share draft, money market, certificate and loan attached to a member number, including type code, nickname, available balance, current balance and pledge holds. Useful for net-worth dashboards and Personal Finance aggregation parity with the It's Me 247 "link external accounts" feature.

Transaction history & statement

Date-bounded transaction lists with transaction code, posted date, effective date, description, ACH counterparty, amount and running balance. Pages stably so reconciliation jobs can re-pull last 90 days without duplicates. Cross-month statement exports map cleanly to FDX 5.x objects for aggregator handoff.

Mobile remote deposit capture

A submission endpoint that accepts front/back check images plus the destination share, returns a deposit ticket id and emits a webhook when funds clear. Implements the 2024–2025 Wymar instant-deposit path for checks under $500 with no scheduled processing wait, and the standard hold schedule for larger checks.

Transfers & Nationwide CU Access

Member-to-member, member-to-self and shared-branch transfers through the Nationwide CU Access partnership that lets Wymar members transact at roughly 5,000 partner branches. The API normalizes routing, fee schedules and posting windows so back-office systems do not need to model each network separately.

Bill pay & scheduled payments

Read scheduled and recurring bill payments, post one-time payments and cancel pending items. Mirrors the It's Me 247 Bill Pay capabilities so finance copilots can suggest "pay this on the 1st" without dropping members back into the native app.

1) Member login & token exchange

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

{
  "member_number": "0123456",
  "credential": "<encrypted>",
  "device_id": "ios-9F2A-..."
}

200 OK
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rt_8c1...",
  "expires_in": 1800,
  "mfa_required": false,
  "session_scope": ["accounts.read", "transactions.read", "deposit.write"]
}

2) Statement / transaction query

POST /api/v1/wymarfcu/statement
Authorization: Bearer <ACCESS_TOKEN>
Content-Type: application/json

{
  "account_id": "SH-000",
  "from_date": "2026-03-01",
  "to_date":   "2026-04-30",
  "page": 1,
  "page_size": 100,
  "format": "fdx"
}

200 OK
{
  "account": {"id":"SH-000","type":"SHARE","available_balance":1842.55},
  "transactions": [
    {"posted":"2026-04-28","amount":-42.10,"code":"DEBIT_CARD",
     "description":"ROUSES MARKET GEISMAR LA","running_balance":1842.55},
    ...
  ],
  "page_info": {"page":1, "has_more":true, "next_cursor":"c2..."}
}

3) Mobile deposit webhook

POST https://your-app.example/hooks/wymarfcu
X-Signature: sha256=...

{
  "event": "mrdc.deposit.cleared",
  "deposit_id": "mrdc_9f12",
  "member_number": "0123456",
  "account_id": "SH-010",
  "amount": 312.75,
  "path": "instant_under_500",
  "submitted_at": "2026-05-09T14:02:11Z",
  "available_at": "2026-05-09T14:02:14Z"
}

// Verify HMAC, then post to ledger.
// Retries: exponential, 5 attempts, idempotency key = deposit_id.

Regulatory posture

Integrations are designed to align with the U.S. open-banking direction set by the CFPB Personal Financial Data Rights Rule (Section 1033). The CFPB stayed the tiered compliance schedule in July 2025 and opened an accelerated rulemaking in late 2025, so production integrations follow the spirit of the rule — consumer consent, revocability, secure developer interfaces — without assuming a fixed date. Smaller credit unions (≤ $850M in assets, which includes Wymar) are explicitly out of the mandatory compliance bucket, but adopting the same shape now means the data is portable when the rule resettles.

Privacy & security controls

• Member consent recorded with scope, timestamp and revocation endpoint (GLBA-aligned).
• NCUA Part 748 security-program expectations baked into the deployment guide.
• Data minimization: only the requested fields leave the gateway; full transaction blobs stay inside.
• BSA / AML hooks for transaction streams that feed monitoring tools.
• FDX schema mapping so aggregator hand-offs avoid bespoke field translation.

About us

OpenFinance Lab is an independent studio focused on mobile-app protocol analysis and OpenBanking/OpenData integration. The team blends engineers from U.S. community banks, credit-union service organizations, payment gateways and cloud platforms, and ships compliant API layers that other shops won't touch because they require careful consent and regulator-aware design.

• Credit union and community-bank integrations, including CU*BASE / It's Me 247 deployments.
• FDX 5.x schema work for aggregators, fintechs and Section 1033-aware client apps.
• Custom Python, Node.js and Go SDKs plus test harnesses with sandbox seed data.
• End-to-end pipeline: protocol analysis → build → validation → compliance review.
• Source code delivery from $300 — runnable API source code and full documentation, paid only after delivery upon satisfaction.
• Pay-per-call API billing — hosted endpoints with usage-based pricing and no upfront fee.

Contact

For quotes, NDAs or to submit your Wymar FCU integration scope (data types, expected call volume, hosting preference), open our contact page.

Contact page

Engagement workflow

1. Scope confirmation: which data types and which screens of the Wymar FCU app you need exposed (login, balances, statements, mRDC, transfers).
2. Protocol analysis and API design (2–5 business days), covering It's Me 247 challenge flow and CU*BASE field mapping.
3. Build and internal validation (3–8 business days), with sandbox member seed.
4. Docs, code samples, OpenAPI spec and test cases (1–2 business days).
5. Hand-off and pilot: typical first delivery 5–15 business days; institutional approvals can extend timelines.

FAQ

What do you need from me to start a Wymar FCU integration?

How long does a first Wymar FCU API delivery take?

How do you handle compliance for credit-union data?

Can you export Wymar FCU statements to accounting tools?