Meritrust Colorado API integration & OpenBanking data services

01Authentication & session

Capture the member login flow used by the Meritrust Colorado app, including device-binding, biometric step-up (Touch ID / Face ID), and refresh-token rotation. Output a documented OAuth-style wrapper your backend can call to obtain a member-scoped access token, with logging hooks for every consent event so a Rule 1033 audit trail is preserved.

02Account snapshot API

Aggregate balances and metadata across checking, savings, certificates, and loan products into a single response — matching what the app shows on its dashboard. Useful for treasury dashboards, member-experience portals, and personal-finance aggregators that need to render a unified household view.

03Transaction history & statements

Paged transaction queries with date-range, account, type, and amount filters, plus statement pulls in PDF/CSV/OFX. Supports cash-flow underwriting, accounting sync (QuickBooks, Xero), and dispute/chargeback investigation pipelines that need 24+ months of clean data.

04Bill pay & P2P transfers

Programmatic access to payee management, scheduled payments, recurring transfers, and pay-other-people flows. Returns settlement status and posts a webhook on completion so your AR/AP, payroll, or rent-collection product stays in sync without polling.

05Card controls & alerts

Lock and unlock debit and credit cards, register card-not-present alerts, and subscribe to budget-category, savings-goal, large-transaction, and overdue-payment notifications. Useful for fraud-prevention layers, parental-control fintechs, and high-touch wealth advisors.

06Mobile check deposit (RDC)

Image-capture and submission flow for remote deposit capture, including front/back image normalization, MICR parsing, and deposit-status callbacks. Pairs well with small-business invoicing apps that want to convert paid checks into reconciled deposits without manual handoff.

Scenario A — Small-business accounting sync

Context: A Colorado-based bookkeeping SaaS wants to import Meritrust Colorado checking and credit-card activity for member businesses without asking for credentials each month.
Data & APIs: account directory + transaction history + monthly statement export.
OpenBanking mapping: Member grants consent under a Rule 1033-style flow; FDX accounts and transactions resources are pulled nightly via a member-scoped access token that the bookkeeper refreshes silently.

Scenario B — Cash-flow underwriting for auto loans

Context: An indirect auto-lending fintech wants 12–24 months of deposit and withdrawal history to assess capacity for a vehicle refinance offer.
Data & APIs: long-window transaction pulls, recurring-payment detection, salary deposit recognition.
OpenBanking mapping: One-time consent retrieves the historical window; webhook events trigger re-pulls at decision checkpoints, eliminating PDF statement uploads.

Scenario C — Family budget & savings coach

Context: A consumer PFM app wants to surface the member's existing budget categories and savings-goal progress alongside outside accounts.
Data & APIs: budget summary, savings-goal endpoint, alert subscriptions.
OpenBanking mapping: Read-only scope plus push-style webhook subscriptions; the PFM never stores raw credentials, only the consent token.

Scenario D — Rent collection for landlords

Context: A property-tech platform wants to schedule recurring rent transfers from member tenants and confirm settlement on landlord books.
Data & APIs: recurring-transfer scheduling, transfer-status webhook, P2P pay-people flow.
OpenBanking mapping: Write-scope consent for scheduled transfers, narrowly limited to a named beneficiary; revocation honored via the standard consent endpoint.

Scenario E — Card-fraud overlay for merchant gateways

Context: A fraud-prevention vendor wants to instantly disable a Meritrust Colorado debit card the moment its rules engine detects a high-risk auth.
Data & APIs: card lock endpoint, alert webhook for posted transactions, push notification path.
OpenBanking mapping: A scoped write token allows lock/unlock only; alert webhooks feed the vendor's risk pipeline in near real time.

1. Member login & consent

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

{
  "member_id": "PMCU-8821xxxx",
  "credential": "<password-or-mfa-blob>",
  "device": {
    "platform": "ios",
    "biometric": "face_id",
    "device_fingerprint": "0a3f...c2"
  },
  "consent": {
    "scope": ["accounts:read","transactions:read","transfers:write"],
    "purpose": "accounting_sync",
    "ttl_days": 90
  }
}

200 OK
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rt_3f82...",
  "consent_id": "csnt_2025_04_25_abcd",
  "expires_in": 1800
}

2. Statement / transaction query

GET /api/v1/meritrust-co/accounts/{account_id}/transactions
  ?from=2026-01-01&to=2026-04-25&page=1&page_size=100
Authorization: Bearer <ACCESS_TOKEN>
X-Consent-Id: csnt_2025_04_25_abcd

200 OK
{
  "account_id": "acc_chk_4421",
  "page": 1,
  "total": 318,
  "transactions": [
    {
      "id": "txn_9f12",
      "posted_at": "2026-04-22T14:08:00Z",
      "amount": -42.18,
      "currency": "USD",
      "description": "KING SOOPERS #0125 BOULDER CO",
      "category": "groceries",
      "status": "posted"
    }
  ]
}

3. Settlement webhook

POST https://your-app.example.com/webhooks/meritrust
X-Signature: sha256=...
Content-Type: application/json

{
  "event": "transfer.completed",
  "transfer_id": "tr_7821",
  "account_id": "acc_chk_4421",
  "amount": 1850.00,
  "counterparty": "LANDLORD-LLC",
  "settled_at": "2026-04-25T12:00:11Z",
  "consent_id": "csnt_2025_04_25_abcd"
}

# Recommended: verify HMAC, idempotency-key on transfer_id,
# retry policy: exponential backoff up to 24h, then DLQ.

Compliance & privacy

Every Meritrust Colorado integration we deliver is scoped against current US financial-data regulation. The CFPB's Personal Financial Data Rights Rule (12 CFR Part 1033), finalized October 22, 2024 and effective January 17, 2025, requires covered data providers to make consumer transaction and account data available in a standardized electronic form to authorized third parties — with explicit consent, revocation, and audit logging. Although tiered compliance dates were stayed by court order in late 2025, we already build to the rule's data-minimization, scope-binding, and consent-revocation expectations.

We further align payload shapes to FDX API v6.4 (Spring 2025), which incorporates 24 new RFCs, a refreshed Consent API behavioral specification, and the CSDF security model. Where applicable we honor the GLBA Safeguards Rule, NCUA member-data guidance, and state-level privacy statutes (e.g. the Colorado Privacy Act). NDAs, retention windows, and per-purpose access scoping are documented per engagement.

Data flow / architecture

A typical pipeline we ship looks like this:

1. Client app / member browser → consent handshake against our adapter, returning a scoped access token.
2. Ingestion API → pulls accounts, transactions, statements, and consent events from the member-scoped session, normalizing to FDX-shaped JSON.
3. Storage layer → encrypted at rest (AES-256), partitioned by member, with retention tags for Rule 1033 revocation handling.
4. Downstream API or webhook bus → serves your product (PFM, lender, accounting tool) and pushes settlement / alert events with HMAC-signed payloads.

Bellco Banking

The mobile app of the second-largest Colorado credit union (Greenwood Village HQ). Members commonly need cross-institution transaction exports between Bellco and Meritrust Colorado for household budgeting and small-business books.

Canvas Credit Union

Lone Tree-based community CU with broad Front Range membership. Aggregators that ingest Canvas transaction data typically reuse the same FDX-aligned client to pull from Meritrust Colorado as well.

Ent Credit Union

Colorado's largest credit union by membership, headquartered in Colorado Springs. Card-control and bill-pay flows in Ent's app overlap heavily with Meritrust Colorado's, so a unified card-lock orchestration is a common ask.

Elevations Credit Union

Boulder-based CU with strong digital adoption among the same university and tech-employer segments Meritrust Colorado serves. Statement-export pipelines often run side-by-side for both apps.

Westerra Credit Union

Denver community CU. Westerra's transfer and recurring-payment data shapes are close enough to Meritrust Colorado's that a single normalization layer can serve both downstream products.

Meritrust Mobile (Kansas charter)

The Kansas-side Meritrust banking app from the same combined credit union. Cross-charter members benefit from a unified household-level transaction view that bridges the two apps.

Premier Members Mobile (legacy)

The legacy app brand for the same Colorado member base prior to the 2025 merger; useful historical reference for migration testing and dual-version rollout windows.

Bellco FCU Mobile Banking

A separate Pennsylvania-based credit union app sometimes confused with Colorado's Bellco. Naming-disambiguation aside, integration patterns mirror typical Symitar-backed CU stacks.

Premier America Credit Union

California CU running on Symitar Episys. Frequently referenced when our clients want a cross-state, multi-charter integration template that includes Meritrust Colorado.

Quorum Federal Credit Union

National-charter credit union with FDX-style data-sharing initiatives. Useful comparison point for how member-permissioned APIs are evolving across the broader credit-union sector.

Source code & documentation

• OpenAPI / Swagger 3.1 specification for every endpoint we expose
• Auth flow report (token chain, biometric step-up, refresh rotation)
• Runnable Python and Node.js reference clients
• Postman collection & pytest / Jest test harness
• Webhook signing keys, idempotency & retry guidance
• Compliance memo: Rule 1033 mapping, FDX v6.4 alignment, GLBA notes

Engagement workflow

1. Scope confirmation: which member-permissioned data and write actions
2. Protocol analysis & API design (3–5 business days)
3. Build & internal validation against sandbox member accounts (4–8 days)
4. Docs, samples, compliance memo, handover (1–2 days)
5. Typical first delivery: 8–15 business days end-to-end

Pricing

Source code delivery from $300: we hand over runnable API source, OpenAPI spec, and full documentation; payment after delivery upon acceptance.

Pay-per-call API: use our hosted endpoints with per-call billing — no upfront fee, ideal for teams that want usage-based pricing without standing up infrastructure.

What do you need from us to start?

The target app name (Meritrust Colorado), a written description of the data flows you want (e.g. transaction history sync, card lock, recurring transfers), and any sandbox or test credentials you can lawfully share. We handle the protocol analysis from there.

How long is a typical first delivery?

Most engagements ship a working API plus documentation within 8–15 business days. Multi-scope writes (transfers, card actions) or third-party approval cycles can extend that.

How do you handle compliance and consent?

We work strictly under member authorization or documented public/authorized APIs. Consent records, scoping, and revocation are persisted in line with CFPB Rule 1033 expectations and FDX v6.4 patterns. We sign NDAs on request.

Will the integration survive the post-merger app changes?

Yes — we monitor the published Meritrust Colorado app over an agreed support window and ship update patches when login flows, payload shapes, or alert webhooks shift after the August 2025 merger consolidation.