Wymar Federal Credit Union runs on It's Me 247 — here is how its member data is integrated

Wymar's online and mobile banking is not an in-house build — it is It's Me 247, the member-facing front end CU*Answers runs on its CU*BASE core processor, the same stack many small US credit unions sit on. That single fact decides the integration: the data lives behind an authenticated It's Me 247 session scoped to Wymar's tenant, reached through documented protocol analysis of that session under the member's authorization. The mobile app, as its store listing describes it, wraps the It's Me 247 mobile-web surface plus native remote deposit, branch and contact lookups, and help.

The route we would take is member-consented interface integration of that session, normalized into a clean read API. It is durable because the surface is a maintained platform product, not a one-off page, and we account for its update cycle. Below: the records that come back, a concrete sketch of the session, what we hand over, and how the credit union's size changes the regulatory picture.

Member records the It's Me 247 session carries

These map to surfaces a Wymar member sees after login. Granularity reflects what It's Me 247 presents for a CU*BASE-backed account; exact field names are confirmed against a consenting account during the build.

A consented It's Me 247 session, in pseudocode

Illustrative only — the precise host path, challenge order and JSON shapes are pinned during the engagement against a consenting Wymar account. It's Me 247 instances resolve under a per-credit-union path segment; Wymar's online-banking help pages were observed under an obc.itsme247.com/<cu-id>/ form.

# Authorized, member-consented session — illustrative, not a final contract
session = http.client(base="https://obc.itsme247.com/<wymar-cu-id>/")

# 1. Establish session with member-supplied credentials (consent on record)
r = session.post("/auth/login", data={
        "member": MEMBER_ID,            # member number / username
        "secret": CONSENTED_SECRET })   # never stored beyond the consent scope

# 2. Personal Internet Branch / device challenge, when presented
if r.requires_pib_or_otp():
    session.post("/auth/challenge", data={"answer": pib_or_otp()})

# 3. Pull the account summary, then walk each sub-account
summary = session.get("/accounts/summary").json()
for acct in summary["accounts"]:
    txns = session.get(f"/accounts/{acct['id']}/transactions",
                       params={"period": "P90D"}).json()
    emit(normalize(acct, txns))   # -> stable schema we define and document

# 4. Refresh before idle timeout; back off and re-auth on session expiry
on_error(SESSION_EXPIRED, lambda: reauth_then_resume())
      

What lands in your hands

Concrete artifacts, scoped to Wymar's surfaces rather than a generic credit-union template:

• An OpenAPI specification for a normalized read API over balances, transactions, statements, transfers, bill pay and remote-deposit status.
• A protocol and auth-flow report covering the It's Me 247 login, the PIB security layer and any device challenge, session lifetime and refresh behavior.
• Runnable source for the key endpoints in Python or Node.js — session establishment, account walk, transaction pagination, statement retrieval.
• Automated tests against a consenting account or a sponsor-provided test context, including session-expiry and challenge paths.
• Interface documentation and data-retention guidance written to NCUA-aligned security expectations and the member consent scope.

The route we'd actually take for Wymar

Two routes genuinely apply here, and they rank clearly.

Member-consented interface integration of the It's Me 247 session

This is the route we recommend. Everything in the data table is reachable through it, it does not depend on a regulatory mandate the credit union is too small to trigger, and the It's Me 247 surface is a maintained product rather than an ad-hoc page, which makes the mapping stable between vendor updates. Effort is moderate: the session, the PIB step and pagination are the work; we set up access with you during onboarding against a consenting member account or a test context.

Native export as a fallback

Where a member can pull statement documents or transaction exports from It's Me 247 directly, that covers document-level retrieval and slow-moving history. It is low effort and durable but coarse — no real-time balance or intra-period transaction stream — so we treat it as a supplement for archival needs, not the primary feed.

For a live integration, route one carries the product; export backfills history and statements where a member opts to use it.

NCUA supervision and where Section 1033 sits for a CU this small

Wymar is a federal credit union under NCUA supervision, share-insured, with a single-SEG field of membership tied to the BASF Geismar workforce. That size and structure matter for data rights. The CFPB's Personal Financial Data Rights rule, as finalized, scoped covered data providers by asset size and placed the smallest institutions far out on the compliance timeline, with those below the SBA size standard outside coverage; an institution Wymar's size sits well under that line. The rule has since been reopened for reconsideration and is in litigation, so there is no settled federal data-portability mandate to build against for a credit union this small. We therefore work from member consent and authorized interface integration, with consent recorded, scope limited to the member's own accounts, credentials never retained beyond the consent window, data minimized to the requested domains, and an NDA where the engagement calls for one.

Engineering notes for the CU*BASE / It's Me 247 stack

Specific things we account for so the integration holds up:

• Multi-tenant host. It's Me 247 serves many credit unions from a shared platform, with each routed under its own tenant path. We key every request to Wymar's tenant and member context so the integration never cross-talks with another credit union on the same host.
• Platform update cadence. CU*Answers ships periodic It's Me 247 releases. When a release lands, we re-pin the session and field mapping against Wymar's instance and confirm it before the next sync runs, so a vendor UI change is caught rather than discovered through a broken pull.
• PIB / challenge timing. The Personal Internet Branch layer and any device or one-time-code step are designed into the session handling, with refresh ahead of idle timeout, so a consented session establishes and stays alive rather than dropping mid-pull.
• Native vs. mobile-web split. Remote deposit is a native-app feature distinct from the mobile-web surface. If check capture is in scope we account for that separate flow and its image payload; otherwise we scope cleanly to read-only balance, transaction and statement pulls.

Access and any test context are arranged with you during onboarding — that setup is our step, not a hurdle put in front of you.

Where teams use Wymar account data

• A personal-finance app aggregating a member's Wymar balances and transactions into a single net-worth and cash-flow view.
• A bookkeeping tool reconciling share-draft activity against ledgers, with statement documents pulled for the audit trail.
• A lender verifying balances and recent transaction history with the member's consent before underwriting.
• A member-facing analytics product syncing periodic statements and transfer schedules for spending insights.

App screens

From the public store listing — opens full size.

Other credit-union apps in the same family

Same category, neutral context — several sit on shared digital-banking cores, and the Louisiana names are in Wymar's own market. Useful when one normalized API needs to span more than one credit union.

• Navy Federal Credit Union — very large member base; balances, transactions, transfers and card controls behind an authenticated app.
• Pentagon Federal Credit Union (PenFed) — accounts, loans and card data across iOS and Android, server-side per member.
• Alliant Credit Union — balances, transaction history, transfers, bill pay and check deposit in one app.
• BECU — large Washington-state credit union with full digital-banking account data.
• Preferred Credit Union — runs It's Me 247 online banking, the same CU*Answers front end as Wymar.
• MyPelican (Pelican State Credit Union) — Baton Rouge credit union; accounts, loans, Zelle, budgeting and check deposit.
• Neighbors Federal Credit Union — Southeast Louisiana credit union with mobile check deposit and account access.
• Campus Federal Credit Union — Louisiana credit union serving the LSU community with digital-banking account tools.

How this brief came together

Checked in May 2026 against the credit union's own It's Me 247 and online-banking pages, the CU*Answers product documentation for It's Me 247 on CU*BASE, a third-party credit-union directory for institution facts (Geismar location, single-SEG field of membership, asset size on the order of $150M as those directories report it), and the current Federal Register and CFPB status of the Personal Financial Data Rights rule. The package ID com.wymarfcu.wymarfcu is per the Google Play listing; the credit-union charter and member-count figures are not asserted here.

• Wymar FCU — It's Me 247 online banking
• CU*Answers — It's Me 247 mobile app on CU*BASE
• Federal Register — Personal Financial Data Rights Reconsideration
• Wymar Federal Credit Union directory profile

OpenBanking Studio integration desk · mapping reviewed May 2026.

Integrator questions about Wymar FCU

Wymar's banking runs on It's Me 247 — does that change how the data is reached?

It shapes the whole approach. It's Me 247 is CU*Answers' shared digital-banking front end on the CU*BASE core, so the work is authorized interface integration of Wymar's own member session on that platform, keyed to Wymar's tenant rather than a generic credit-union endpoint. We map the session, the PIB security step and the account surfaces specific to Wymar's instance.

Which member records come back from a consented Wymar session?

Share and checking balances, transaction history per account, periodic statements, internal and member-to-member transfer records, bill-pay schedules, and loan account positions, at the granularity the It's Me 247 surface presents them. Remote deposit status is reachable if check-deposit flows are in scope.

Does Section 1033 give a small credit union like Wymar a ready-made data feed?

No. Wymar is a single-SEG federal credit union under NCUA supervision and well below the asset size standard the finalized Personal Financial Data Rights rule used to scope covered providers. That rule has also been reopened for reconsideration and is in litigation, so there is no settled federal mandate to lean on here. The practical route is member-consented interface integration of the It's Me 247 session.

How do you handle the PIB security layer and any MFA step?

We design session handling around Personal Internet Branch and any device or one-time-code challenge so a consented session establishes reliably and refreshes before timeout, rather than failing silently mid-sync. The exact challenge sequence is confirmed against a consenting account during the build.

Working with us

Source for the Wymar endpoints lands in one to two weeks. You give us the app name and what you want out of its data; we handle access, the It's Me 247 session work and the compliance posture. You choose the model: source-code delivery from $300, where you receive the runnable integration and documentation and pay after delivery once you are satisfied; or a pay-per-call hosted API with no upfront fee, where you call our endpoints and pay only for calls. Tell us the target at /contact.html and we will scope it.