TN Military FCU API integration (OpenBanking / OpenData)

Authorized protocol analysis and production-ready APIs for Tennessee Military Federal Credit Union member data, payments and card controls.

From $300 · Pay-per-call available
OpenData · OpenFinance · OpenBanking · Section 1033 · Credit union integration

Connect TN Military FCU member balances, transactions and card controls to your stack — under member consent

The Tennessee Military Federal Credit Union mobile app (also known as ETMA FCU, package net.etmafcu.etmafcu) is the daily access point for service members, veterans and their families across East Tennessee. Behind that app sits a structured pool of member data — share account balances, posted and pending ACH transactions, card transactions, bill pay payees, scheduled transfers and remote deposit history — that finance teams, PFM apps and compliance platforms increasingly need to pull through a clean API rather than screen scraping.

Authenticated session APIs — Mirror the app's login, MFA challenge and Face ID / Touch ID enrollment flow into a server-side OAuth-style token exchange, suitable for member-authorized third-party access.
Statement & transaction history — Posted, pending and memo-posted transactions across share, share draft (checking), money market and loan accounts; paged by date range with structured merchant, amount and category fields.
Transfers, bill pay & RDC — Initiate internal transfers, ACH transfers, scheduled bill payments and remote deposit capture (RDC) submissions; pull confirmation receipts and item-level status.
Card controls & alerts — Toggle debit-card lock state, set merchant or geography rules, and stream eAlert events as webhooks for downstream fraud-monitoring pipelines.

What you receive — feature modules

Authentication & session

OAuth-style token issuance that wraps the credit union's member login and MFA step (one-time code, security questions, biometric re-auth). Includes refresh handling, device binding and session revocation, so a personal finance dashboard or accounting integration stays connected for weeks without re-prompting members.

Statement export & reconciliation

Pull transaction history per account with paging, date range and type filters. Output as JSON, CSV or OFX/QFX so an external general ledger, NetSuite reconciliation rule or QuickBooks classification job can match deposits and ACH debits without manual export.

Funds movement

Initiate internal share-to-share transfers, ACH push/pull to linked external accounts, scheduled transfers and bill pay payee management. Each call returns an item ID that can be polled or pushed via webhook for posted/returned/cancelled status — useful for treasury and family-office tooling.

Mobile check deposit (RDC) bridge

Submit front/back check images and amount to the RDC endpoint, with response codes for accepted, on hold, duplicate and failed. Lets a back-office app accept member-side captures without re-implementing the in-app capture UX.

Card controls & alerts

Programmatically lock/unlock debit cards, set transaction-type rules (e.g. block international, block ATM, set spend limits) and stream eAlert subscriptions — large transactions, low balance, deposit posted — as webhooks into Splunk, Slack or a custom fraud queue.

Loan & credit card snapshot

The 2024 app refresh added Loan and Credit Card snapshots showing balances, due dates and quick links to card controls. Our integration exposes those same fields — outstanding balance, next payment date, minimum due, payoff amount — so a household-finance dashboard or veteran benefit portal can surface them in one view.

Data available for integration

Below is the inventory of structured data surfaces we typically expose through a TN Military FCU integration. Granularity reflects what the mobile app already presents to members; access remains scoped to member-authorized sessions.

Data typeSource / screenGranularityTypical use
Member profileAccount summaryMember ID, name, masked SSN tail, contact, joint ownersKYC refresh, sanctions screening
Account balancesAccount summary, snapshotsAvailable, current, hold; per share & loanCash position dashboards, alerts
Transaction historyTransaction list, statementsPosted & pending; date, amount, type, description, merchantReconciliation, PFM categorization
Loan / credit card snapshotLoan & Credit Card snapshot (added 2024)Balance, APR, due date, minimum, payoffDebt dashboards, payoff planning
Transfers & bill payTransfers, Pay BillsPayee, amount, frequency, next-run, statusTreasury automation, payroll routing
RDC submissionsDeposit ChecksItem ID, amount, status, hold release dateReceivables, AP automation
Card controls & eAlertsCard management, AlertsCard lock state, rules, alert eventsFraud queues, family-account oversight

Typical integration scenarios

1. Veteran-services finance dashboard

A nonprofit assisting service members consolidates checking balance, loan payoff and recent transactions from TN Military FCU alongside other military-friendly institutions to advise on PCS-move budgeting. The integration pulls balance and transaction history under member consent every 30 minutes and writes a normalized event stream into a Postgres warehouse for analyst notebooks.

2. Small-business reconciliation for veteran-owned firms

A bookkeeping provider serving veteran-owned LLCs maps the credit union's posted transactions into chart-of-accounts buckets via the QFX/OFX export. Bill pay payees flow into a vendor master, and ACH debit returns are exposed as webhook events so the bookkeeper sees same-day reversals without polling.

3. Family financial oversight

A spouse-managed household app pulls balance, scheduled transfers and large-transaction eAlerts from the principal member's account (with that member's explicit, revocable consent). The family app surfaces a single weekly cash-flow chart and triggers a push notification when the loan minimum-due date approaches.

4. Fraud and identity monitoring

A monitoring service streams card-not-present alerts and atypical-merchant events from the credit union eAlert webhook into a SIEM rule. Suspicious transactions trigger an automated card-lock call back through the integration, achieving a containment loop without a member having to open the app first.

5. Section 1033 portability flow

Under the CFPB's Personal Financial Data Rights rule, an authorized third party requests a structured export of a member's transactions and account history when the member opts to portability-port to another provider. The integration delivers a 24-month JSON export and an audit log of the consent, request and delivery events.

Technical implementation

Member authentication (OAuth-style)

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

{
  "member_number": "*****1234",
  "password": "<cipher>",
  "device_id": "pf-dash-01",
  "mfa": { "method": "otp", "code": "482910" }
}

200 OK
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rt_...",
  "expires_in": 3600,
  "scopes": ["balances","transactions","transfers","rdc"]
}

Transaction history query

POST /api/v1/tnmilfcu/transactions
Authorization: Bearer <ACCESS_TOKEN>

{
  "account_id": "S0001",
  "from_date": "2026-04-01",
  "to_date":   "2026-04-30",
  "include_pending": true,
  "page": 1,
  "page_size": 100
}

200 OK
{
  "items": [
    {"id":"T882...","posted_at":"2026-04-29","amount":-42.18,
     "type":"DEBIT_CARD","desc":"COMMISSARY KNOXVILLE TN"},
    {"id":"T881...","posted_at":"2026-04-28","amount": 2400.00,
     "type":"ACH_CREDIT","desc":"DFAS-CLEVELAND DIRECT DEP"}
  ],
  "page":1,"total":124
}

eAlert webhook (card & balance events)

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

{
  "event":"card.transaction.high_value",
  "member_id":"M-93f...",
  "card_last4":"7741",
  "amount": 612.40,
  "merchant":"GAS STATION ATHENS TN",
  "occurred_at":"2026-05-07T22:14:08Z",
  "suggested_action":"lock_card"
}

Compliance & privacy

Credit-union member data is regulated under several overlapping U.S. frameworks. Our integrations are scoped to those obligations rather than improvised on top of them.

  • CFPB Section 1033 (Personal Financial Data Rights). The final rule was effective January 17, 2025, with staggered compliance windows running April 2026 through April 2030; an August 2025 Advance Notice of Proposed Rulemaking is reconsidering parts of the rule. Smaller institutions may be exempt — we confirm scope before scoping work.
  • GLBA & Regulation P. Non-public personal information is handled under data-minimization rules with clear notice to members.
  • NCUA third-party guidance. Logging, encryption, breach notification and vendor-risk controls follow NCUA's expectations for credit-union third-party access.
  • State law. Tennessee Information Protection Act and breach-notice obligations are observed for in-state members.

Data flow / architecture

A typical pipeline looks like this:

  1. Member device (TN Military FCU app or our integration SDK) authenticates with MFA.
  2. Auth gateway issues a short-lived access token bound to the member's consented scopes.
  3. Integration API calls the credit union's authorized member endpoints, normalizes fields and emits events.
  4. Storage / stream (Postgres, S3, Kafka) persists transactions and webhook events with a complete audit trail.
  5. Consumer — your dashboard, ERP or fraud platform — reads through a stable, versioned REST/GraphQL surface.

Market positioning & user profile

TN Military FCU primarily serves the East Tennessee military community — active-duty service members, National Guard and Reserve, military retirees, civilian DoD employees and their immediate family — across both Android and iOS. Members rely on the app for direct-deposit visibility (DFAS payroll), VA loan servicing, deployment-time card controls and remote check capture from forward locations. Compared with national-scale military institutions like Navy Federal or USAA, TN Military FCU is a community-scale credit union with deeper local branch presence in the Knoxville and Athens corridor; that profile shapes integration priorities — fewer concurrent connections, stronger emphasis on personalized member identity, and frequent overlap with other military-focused apps that members hold in parallel.

Screenshots

Click any thumbnail to view at full size. These reference screens illustrate where each integrated data surface comes from on the member side.

TN Military FCU mobile app screenshot 1
TN Military FCU mobile app screenshot 2
TN Military FCU mobile app screenshot 3
TN Military FCU mobile app screenshot 4

Similar apps & integration landscape

Members of TN Military FCU often hold accounts in parallel at other military-friendly or community institutions. Teams building consolidated dashboards, PFM tools, or veteran-services portals frequently need to integrate several of these in tandem. The list below describes what kind of structured data each app surfaces and how it fits into the broader credit-union and military-banking integration landscape.

Navy Federal Credit Union — The largest U.S. credit union by assets and members; the app exposes balances, transactions, ACH transfers, RDC and credit-card data. Users who also hold Navy Federal often need a unified transaction export across both providers.
USAA Mobile — Banking, lending and insurance for military members and families; integrations commonly cover checking transactions, auto-loan balances and policy data, which complement TN Military FCU deposit views.
PenFed Credit Union — Pentagon Federal serves a broad member base with checking, mortgage and credit-card products; aggregated dashboards typically fold PenFed transactions next to TN Military FCU share account history.
Service Credit Union — Designed for service members in the U.S. and overseas (Germany base communities); integrations focus on cross-border deposit visibility alongside domestic credit-union accounts.
Security Service FCU — Texas-headquartered military-affiliated credit union; surfaces transactions, card controls and rewards balances that fit the same data shape as TN Military FCU.
Armed Forces Bank — Military-focused bank with surcharge-free ATM access and early-pay direct deposit; integrations typically combine its checking-transaction stream with credit-union loan data.
Marine FCU Mobile Access — Coastal-community credit union app whose data surfaces (account summary, RDC, transfers) match TN Military FCU integration patterns closely.
Alliant Credit Union — Nationwide, digital-first credit union; users blending Alliant's high-yield savings with TN Military FCU checking often want a single transaction view.

About OpenFinance Lab

We are an independent technical studio focused on mobile-banking protocol analysis and OpenData / OpenFinance / OpenBanking API delivery. Our engineers come from core-banking platforms, payment processors, mobile-app reverse engineering and cloud security; we have shipped credit-union and bank integrations across the U.S., Europe and Asia.

  • Mobile-banking protocol analysis under member or institutional authorization
  • OpenAPI / Swagger specifications, runnable Python or Node.js source, and SDK packaging
  • End-to-end pipeline: scope → analysis → build → validation → compliance handover
  • Source code delivery from $300 — receive runnable API source and full documentation; pay after delivery upon satisfaction
  • Pay-per-call API billing — call our hosted endpoints and pay per request, with no upfront fee

Contact

To request a quote, share a sandbox or describe your TN Military FCU integration requirements, open our contact page:

Contact page

We respond to scoping requests within one business day. NDAs are signed before any member-data sample is shared.

Engagement workflow

  1. Scope confirmation — list the data surfaces (login, balances, transactions, transfers, RDC, alerts) and target consumers.
  2. Authorized protocol analysis and API design (typically 2–5 business days).
  3. Build, internal validation against test member accounts (3–8 business days).
  4. Documentation, code samples and Postman collection (1–2 business days).
  5. Compliance handover — Section 1033 alignment, GLBA notice templates, audit-log schema.
  6. First delivery typically lands in 5–15 business days; institutional approvals may extend timelines.

FAQ

What do you need from me to start?

The target app name (TN Military FCU, package net.etmafcu.etmafcu), the specific data or actions you need (e.g. transaction history, balance pull, RDC, scheduled transfers), and any sandbox credentials or member-authorized test accounts you can supply for validation.

How long does delivery take?

A first usable API drop covering login, balances and statement pull is typically 5 to 12 business days. Adding RDC, ACH transfers, bill pay or webhook/alert pipelines extends the timeline by another one to two weeks depending on multifactor and core-banking constraints.

How do you handle compliance?

We work strictly under member authorization or documented public APIs, log every consent and data pull, follow data-minimization for non-public personal information under GLBA, and align flows with CFPB Personal Financial Data Rights (Section 1033) and NCUA examination guidance for third-party access.
📱 Original app overview (appendix)

The Tennessee Military Federal Credit Union mobile app — also distributed as ETMA Federal Credit Union (East Tennessee Military Association) under package net.etmafcu.etmafcu — helps members manage their finances quickly, securely and conveniently from anywhere. The app supports both Android and iOS and serves the East Tennessee military community (active-duty, Guard/Reserve, retirees, DoD civilians and their families).

Key features described by the publisher:

  • View account balances and transaction history
  • Transfer funds between your accounts
  • Deposit checks remotely using your mobile device
  • Pay bills and manage payees
  • Send money with person-to-person payments
  • Apply for loans
  • Manage debit cards, including card controls and alerts
  • Chat with the Virtual Assistant for quick answers and guided support
  • Receive important account notifications

Recent app refreshes (within the last two years) added Loan and Credit Card snapshots — surfacing balances, due dates and quick links to card controls — plus an improved enrollment flow for Apple Face ID and Touch ID, and Text Banking with eAlert subscriptions. Together these signal that meaningful member data (loan balances, alert events, deposit confirmations) is now structured enough on the back end to make a clean API integration practical.

Last updated: 2026-05-08