Reaching member data inside Marine Credit Union's Banno-backed app

Marine Mobile runs on Jack Henry's Banno Digital Platform, and the credit union's own online-banking page tells members to keep Banno Mobile at version 3.25 or newer on iOS and Android. That single fact sets the shape of the work. Behind the app is one authenticated, OIDC-style session that fronts the member's whole picture: checking and savings balances, posted and pending transactions, statement documents, scheduled and one-time bill pay, internal and external transfers, and the other banks a member has linked for a combined view. The app also surfaces a free FICO score. The integration question here is not what data exists — the surfaces are broad and member-specific — it is how to reach them on a stable, authorized footing.

We would anchor a Marine Mobile build on the member-consented Banno session and treat the federal data-rights path as the durable successor as it firms up for cooperatives of Marine's size. The rest of this brief is what is reachable, how a session is structured, what we hand over, and what we handle so it keeps working.

What member data the app actually holds

Each row below is a surface the app exposes to a signed-in member, named close to how Marine presents it.

Authorized ways into the data

Three routes genuinely apply to this app. They are not equivalent in durability.

Member-consented interface integration of the Banno session

The app authenticates a member through a Banno OIDC-style flow, then reads JSON surfaces for accounts, activity, documents and transfers. Working from a consenting member account, we map that token lifecycle and those surfaces and rebuild them as a clean interface. Reach is the full signed-in picture. Effort is moderate. Durability tracks Banno's release cadence, which we plan maintenance around. Access to a consenting account or a sponsor sandbox is arranged with you during onboarding — it is part of the engagement, not something you sort out first.

Federal consumer data-rights access

The CFPB Personal Financial Data Rights framework, 12 CFR Part 1033, defines consumer-authorized access to transactions, balances, payment-initiation and bill information, phased in by institution asset size. For a cooperative of Marine's profile this is the most stable long-run path once it is live for that tier. We build the consented Banno route now and design the data model so a later switch to the Part 1033 path is a swap, not a rewrite.

Member-consented credential aggregation

Marine Mobile already links other banks the same way an aggregator would — credential login or micro-deposit confirmation. The same consented mechanism can mirror the member's Marine data outward. It is the lightest path for a single-member proof of value and a useful fallback.

Native export is a thin backstop: a member can pull statement PDFs and downloaded activity, useful for one-off document needs but not for an ongoing sync. On this build the consented Banno session is the spine and the Part 1033 route is the planned successor; the credential path covers early validation.

Inside a Marine Mobile session

Illustrative shape of the authenticated Banno-style flow, confirmed against a consenting account during the build — field names are normalized in delivery, not guessed from the outside.

# 1. Member auth → short-lived access token (Banno OIDC-style)
POST /a/consumer/api/oauth/token
  grant_type=authorization_code  code=<auth_code>
  device_id=<bound_device>        # step-up MFA may gate this
-> 200 { "access_token": "...", "expires_in": 600,
         "refresh_token": "...", "scope": "accounts tx documents" }

# 2. Accounts the member can see
GET /a/consumer/api/users/me/accounts
  Authorization: Bearer <access_token>
-> 200 [ { "id": "acct_***", "type": "share_draft",
           "name": "Marine Checking", "available": 1842.55,
           "current": 1907.10, "currency": "USD" }, ... ]

# 3. Paginated activity for one account
GET /a/consumer/api/accounts/{id}/transactions?limit=100&cursor=<next>
-> 200 { "items": [ { "postedAt": "2026-05-12", "amount": -54.20,
           "description": "ACH BILL PAY", "status": "posted" } ],
         "next": "<cursor>" }

# Handling notes carried into the client we ship:
#  - refresh before expiry; re-auth path on step-up MFA challenge
#  - linked external accounts: skip while link_state == "pending_microdeposit"
#  - FICO panel is a dated snapshot, surfaced with its refresh date
      

What you receive for the Marine Mobile build

Everything below is scoped to this app's real surfaces, not a generic kit.

• An OpenAPI specification covering the mapped Marine Mobile surfaces — accounts, transactions, statements, transfers, bill pay, linked-account list.
• A protocol and auth-flow report: the Banno OIDC-style token exchange, device binding, refresh and the step-up MFA path, written up so a new engineer can follow it.
• Runnable source for the key endpoints in Python and Node.js — sign-in, balance pull, paginated activity, statement fetch, linked-account read.
• Automated tests against the documented surfaces, including the pending-versus-verified linked-account case and token-refresh behaviour.
• Interface documentation and field mapping, with the FICO snapshot represented as a dated value.
• Consent, logging and data-retention guidance fit to an NCUA-insured cooperative.

Where teams use this

Concrete end-to-end uses we have scoped for apps of this shape:

• A personal-finance app syncing a member's Marine balances and categorized transactions on a nightly schedule.
• A lender collecting statement PDFs and twelve months of activity for underwriting, under explicit member consent.
• An accounting tool reconciling a small-business cash position across the Marine account and the external banks the member already linked inside the app.
• A budgeting feature reading scheduled bill-pay items so upcoming obligations show before they post.

Consent and the NCUA picture

Marine Credit Union is an NCUA-insured cooperative, so access here is grounded in consumer data rights and explicit member consent. The governing US framework is the CFPB Personal Financial Data Rights rule, 12 CFR Part 1033, which covers consumer-authorized access to balances, transactions, payment-initiation and bill data and phases obligations in by institution asset size. Whether Marine is directly a covered data provider depends on its asset tier, which we do not assert here. Our build does not wait on that question: every read runs on explicit member authorization, scoped to the data the use case needs, with consent timestamps and revocation honoured, request logging, data minimization, and an NDA where the engagement calls for one.

What we account for on this build

The judgment that keeps a Marine integration alive lives in a few specifics:

• Banno release drift. Banno Mobile ships on its own cadence and Marine pins members to 3.25 or newer. We budget a recheck step keyed to Banno point releases and fold it into handover, so a platform update does not quietly break the session map.
• Two linking states for external accounts. A member can add another bank by instant credential login or by confirming two micro-deposits that land in one to three business days. We model both, so an account still in micro-deposit confirmation is reported as pending rather than treated as a live balance.
• Step-up MFA and device binding. The Banno flow can challenge a bound device. We design the token lifecycle around refresh and the re-auth path so a long-running sync does not silently drop the session.
• The FICO panel is not real-time. It is a periodic third-party refresh. We carry it as a dated snapshot with its refresh date, never as a live field.

Interface evidence

Store screenshots reviewed while scoping the surfaces above. Select to enlarge.

Peer apps in the same data shape

Other US credit-union apps an integrator commonly touches alongside Marine, each with a comparable member-data footprint. Listed for ecosystem context, not ranked.

• Connexus Credit Union — Wausau, Wisconsin cooperative on an Alkami-built app; balances, transactions, transfers and deposits behind one member login.
• Royal Credit Union — Eau Claire, Wisconsin and Minnesota; statements, activity and transfers, a common counterpart in a multi-credit-union view.
• Summit Credit Union — Madison, Wisconsin; checking, savings and bill-pay data behind an authenticated session.
• Altra Federal Credit Union — Onalaska, Wisconsin; accounts, loan and transaction data for the same regional membership base as Marine.
• Westby Co-op Credit Union — Westby, Wisconsin; member balances and activity, often aggregated next to Marine for rural members.
• Capital Credit Union — Wisconsin; everyday balances, transfers and statement documents per member.
• Educators Credit Union — Wisconsin, serving since 1937; deposit, loan and payment data behind a member account.
• UW Credit Union — Madison, Wisconsin; balances, transactions and transfers, a frequent linked account in cross-institution sync.

Sources we opened for this brief

Scoped in May 2026 against the credit union's own member-facing pages, the app store listing, and the federal data-rights text. Primary sources, opened directly:

• Marine Credit Union — Online & Mobile Banking (Banno platform and version requirement)
• Marine Credit Union — Link External Accounts (instant and micro-deposit linking)
• eCFR — 12 CFR Part 1033, Personal Financial Data Rights
• Marine Credit Union — Apple App Store listing

Mapped by the OpenBanking Studio integration desk · May 2026.

Questions integrators ask about Marine Mobile

Is this the same app as Marine FCU Mobile Access?

No. This brief covers Marine Mobile from Marine Credit Union, the La Crosse, Wisconsin cooperative, package com.marinecu.marinecu and iOS App Store id 890089257. Marine FCU Mobile Access is a separate app from a different institution. We pin the integration to the com.marinecu.marinecu build so the wrong endpoints are never mapped.

Does the app running on Banno change what is reachable?

The credit union's site states Marine Mobile runs on Jack Henry's Banno Digital Platform and supports Banno Mobile 3.25 or newer. That tells us the session is an OIDC-style authenticated flow with JSON account and transaction surfaces behind it, which is what we map. Balances, transaction history, statements, transfers, bill pay, the linked-account view and the FICO panel all sit behind that one authenticated session.

Can you reach the external accounts a member already linked inside Marine Mobile?

Yes. Marine Mobile lets a member add other banks under Transfers, either by instant credential login or by confirming two micro-deposits that arrive in one to three business days. The linked-institution list and its balances are part of the consented surface. We model the pending-versus-verified state so an account still in micro-deposit confirmation is not reported as live.

How does the US consumer financial data-rights framework affect a Marine integration?

Marine Credit Union is an NCUA-insured cooperative. The CFPB's Personal Financial Data Rights framework under 12 CFR Part 1033 governs consumer-authorized access to data such as transactions, balances and bill information for covered institutions, phased in by asset size. Whether Marine is directly in that scope turns on its asset tier, which we do not assert here. Either way the build runs on explicit member authorization with consent records and revocation honoured.

Starting work on a Marine Mobile integration

A Marine Mobile build is scoped surface by surface — accounts and transactions first, then statements, transfers and the linked-account view. Source-code delivery starts at $300: you get runnable source, the OpenAPI spec, automated tests and the interface write-up, and you pay only after delivery, once it works for you. If you would rather not run anything yourself, the same integration is available as a hosted, pay-per-call API with nothing upfront. Either way the cycle is one to two weeks. Tell us the app and what you need from its data at /contact.html and we will come back with scope and the route we would take.