Connect HRCCU Mobile Banking accounts, deposits and transfers to your stack — securely
HRCCU Mobile Banking holds member-permissioned data that fintech, accounting and small-business platforms increasingly need. We deliver protocol analysis, login and session refresh flows, balance and 90-day transaction queries, mobile remote deposit capture (RDC) hooks, scheduled transfer APIs, bill pay status, and loan-payment endpoints. Every deliverable is structured around the Financial Data Exchange (FDX) API v6.4 schema so it slots straight into existing aggregator pipelines.
Data available for integration
The HRCCU Mobile Banking app surfaces a focused set of member-permissioned data points. The table below maps each data type to the screen or feature it originates from, the typical granularity exposed by the underlying core (the credit union runs on a virtual-branch core accessed via secure.myvirtualbranch.com), and the most common downstream uses we see in client work.
| Data type | Source feature / screen | Granularity | Typical use |
|---|---|---|---|
| Account list & share types | Accounts dashboard | Per share/loan, with type code (S, S1, L, etc.) | Onboarding, KYC refresh, account aggregation |
| Current & available balance | Account detail | Real-time on poll, USD, two-decimal precision | Cash-flow dashboards, sweep automation |
| Transaction history (90 days) | Transactions screen | Per posted item: date, amount, type, description, running balance | Reconciliation, bookkeeping, fraud analytics |
| Mobile deposit metadata | Deposit a check flow | Front/back image refs, amount, status, deposit ID | RDC reporting, audit, hold management |
| Scheduled & recurring transfers | Transfer center | From/To, amount, schedule (one-time / weekly / monthly) | Treasury automation, savings plans |
| Bill pay records | Pay bills | Payee, amount, send date, status | AP automation, household budgeting |
| Loan balance & payment history | Loan accounts | Principal, payoff, next due, last payment | Refinance tools, credit scoring inputs |
| ATM / Shared Branch locations | Locate ATMs & branches | Geo (lat/lng), hours, surcharge-free flag | Locator widgets, member self-service apps |
Typical integration scenarios
1. Small-business bookkeeping sync
An upstate-New York contractor uses HRCCU as the primary operating account and a third-party ledger (QuickBooks, Xero, Wave) for taxes. Our API exposes the 90-day transaction window in FDX transactions shape, supplemented by a nightly delta endpoint, so the ledger imports posted items, categorizes them via memo strings, and reconciles deposits captured through RDC. The account-list and balance endpoints feed the chart of accounts. This maps directly to FDX accounts and transactions resources.
2. Personal financial management (PFM) aggregation
A PFM app already aggregating Chase and Capital One via Plaid wants to add HRCCU without writing a custom connector. We deliver a Plaid Core Exchange-compatible facade backed by HRCCU member sessions; balance, transactions and identity calls return in the exact Plaid Core Exchange JSON shape. Net result: the PFM team flips a config flag and HRCCU members appear in the same UI.
3. Mobile deposit batch automation
A property-management firm receives dozens of paper rent checks each month. Instead of staff tapping through the HRCCU app one check at a time, an internal tool automates RDC: scanned images are POSTed to our deposit endpoint, the response includes deposit ID and provisional credit status, and webhook callbacks fire when the credit union finalizes posting. This is the fastest workflow change clients actually pay for.
4. Treasury & sweep automation
A nonprofit holding several HRCCU shares wants idle cash above a threshold to move automatically to a higher-yielding share. Our scheduled-transfer API supports both immediate and recurring intra-CU moves; combined with the balance polling endpoint, the customer's job runner moves funds at end-of-day. Audit logs show who ran the transfer, with consent records for Section 1033 compliance.
5. Loan servicing dashboards
An auto-loan refinance startup needs to verify HRCCU loan balance, payoff amount, and payment history before quoting. We deliver a /loans/{id} endpoint returning principal, payoff (good through a date), next due, and last 12 payments. The startup can also post a payment via the same loan-payment endpoint members use in-app, so payoff completes inside their flow.
Technical implementation
Authentication: token exchange
POST /api/v1/hrccu/auth/login
Content-Type: application/json
{
"username": "MEMBER_LOGIN",
"password": "MEMBER_PASSWORD",
"device_id": "9b1f...c0",
"biometric": false
}
200 OK
{
"access_token": "eyJhbGciOi...",
"refresh_token": "rk_8a4...",
"expires_in": 900,
"mfa_required": false,
"session_state": "ACTIVE"
}
Statement query (FDX-aligned)
GET /api/v1/hrccu/accounts/{accountId}/transactions
?fromDate=2026-02-01&toDate=2026-04-30&type=POSTED
Authorization: Bearer <ACCESS_TOKEN>
200 OK
{
"transactions": [{
"transactionId": "TX-20260415-0001",
"postedTimestamp": "2026-04-15T14:22:00Z",
"amount": -42.18,
"currency": "USD",
"description": "POS HANNAFORD GLENS FALLS",
"category": "Groceries",
"runningBalance": 1284.07
}],
"nextPageToken": "eyJvZmZzZXQiOjUwfQ"
}
Mobile deposit (RDC) callback
POST /api/v1/hrccu/deposits
Authorization: Bearer <ACCESS_TOKEN>
Content-Type: multipart/form-data
front=@check_front.jpg
back=@check_back.jpg
amount=325.00
account_id=S1-100245
201 Created
{
"deposit_id": "RDC-2026-04-29-7710",
"status": "PROVISIONAL",
"available_on": "2026-05-01",
"hold_amount": 0.00
}
# Webhook (server -> your endpoint)
POST https://yourapp.example.com/hooks/hrccu/rdc
{
"deposit_id": "RDC-2026-04-29-7710",
"status": "POSTED",
"posted_amount": 325.00
}
Compliance & privacy
Regulatory framing
US credit union integrations sit at the intersection of several regimes. The most relevant is the CFPB Section 1033 Personal Financial Data Rights Rule, finalized in October 2024, which requires covered financial institutions to make consumer account data available to authorized third parties. The Financial Data Exchange (FDX) was approved by the CFPB as a recognized standard-setter, making FDX API v6.4 the natural format for HRCCU-style data sharing. Smaller credit unions (≤ $850M assets) are partially exempt, but member-permissioned access patterns still apply.
We additionally align deliverables with NCUA cybersecurity expectations, Regulation E (electronic fund transfers), and where members are New York residents the New York DFS Part 500 cybersecurity rules. Image handling for RDC follows Check 21 record-retention conventions.
What we put in every package
- Member-permissioned consent flow with revocation
- End-to-end TLS 1.3 and short-lived access tokens (≤15 min)
- Structured audit log for every data read and money-movement call
- Data-minimization guidance: only the fields the downstream actually uses
- Deletion / forget-me hook so partners can satisfy member requests
- Optional NDA and member-disclosure language for marketing pages
Data flow & architecture
The deliverable runs as a thin, stateless adapter between the HRCCU mobile app surface and your downstream stack. A typical pipeline:
- Client app (member device or partner backend) issues a member-authorized request with a short-lived bearer token.
- HRCCU adapter / API gateway handles auth, rate limits, and FDX-shape translation. It speaks to the credit union's virtual-branch core over the same secure protocol the official mobile app uses.
- Storage & cache (optional) — a short-TTL cache for balances, plus an append-only audit store for every consent event and money-movement call.
- Analytics / API output — partner dashboards, accounting ledgers, PFM aggregators, or your own product surface, consuming the FDX-aligned JSON.
For higher-volume customers we add a Kafka or SQS pipe between step 2 and step 4 so transaction deltas can fan out to multiple consumers without each one re-polling.
Market positioning & user profile
HRCCU Mobile Banking serves members of Hudson River Community Credit Union, headquartered near Glens Falls, New York, with branches across the upstate New York / Capital Region corridor. The user base is regional rather than national: working families, small contractors, and seniors using the app primarily on Android and iOS phones. Integration demand we see typically comes from three groups: regional small-business accounting tools that want first-class HRCCU support, PFM apps adding US credit-union coverage beyond the big banks, and back-office automation at non-profits and property managers who handle paper checks and recurring intra-credit-union transfers. Compared with national mega-banks, the appeal of integrating a community credit union is precisely its niche: members are sticky, transaction patterns are local, and a working API endpoint immediately differentiates a fintech that claims "comprehensive US coverage."
What we deliver
Deliverables checklist
- OpenAPI / Swagger 3.1 specification
- Protocol & auth-flow report (token chain, MFA, biometric exchange)
- Runnable source: login, balances, transactions, RDC, transfers, loan payments (Python / Node.js / Go available)
- FDX v6.4 facade adapter and a Plaid Core Exchange compatibility shim
- Postman collection and pytest / Jest test suites
- Docker Compose for local end-to-end testing
- Compliance guidance: Section 1033, Regulation E, Check 21 image handling
Engagement workflow
- Scope confirmation: which scenarios (e.g. read-only PFM vs. RDC + transfers)
- Protocol analysis & API design (2–5 business days)
- Build & internal validation against a member-authorized test session (3–8 business days)
- Docs, samples, and test cases (1–2 business days)
- Typical first delivery: 5–15 business days. Mobile RDC and transfer flows may add a sandbox cycle.
Screenshots
Selected screens from the live HRCCU Mobile Banking app — click any thumbnail to open a larger preview.
Similar apps & integration landscape
HRCCU Mobile Banking lives in the broader US credit-union mobile-banking ecosystem. Teams that need an HRCCU connector usually need others alongside it. The apps below are part of the same landscape; we list them here for ecosystem context, not as a ranking.
- Navy Federal Credit Union — The largest US credit union by assets and members. Holds checking, savings, auto loans and mortgage data; members frequently appear alongside HRCCU in PFM aggregators that need full US coverage.
- PenFed Credit Union — National credit union with strong card and auto-loan data. Customers integrating HRCCU often want a parallel PenFed connector for portfolio dashboards.
- Alliant Credit Union — Digital-first national credit union with high-yield savings and a popular budgeting tool; users often link Alliant and a community CU like HRCCU in the same PFM app.
- Eastman Credit Union — Tennessee-based, consistently rated among the highest US credit-union mobile apps. A useful reference target for "best-in-class" feature parity in any HRCCU-style integration.
- Delta Community Credit Union — Atlanta-area credit union with a heavy mobile-deposit user base, making it a natural sibling for any RDC-focused integration we ship for HRCCU.
- Redstone Federal Credit Union — Alabama-based, strong member-business banking; transaction-export use cases mirror HRCCU small-business workflows.
- ESL Federal Credit Union — Rochester, NY based; geographically adjacent to HRCCU, common in upstate New York multi-CU households.
- Wright-Patt Credit Union — Ohio-based with a large mobile-banking footprint; transaction and bill-pay structures map cleanly to the FDX shape we use for HRCCU.
- Alternatives Federal Credit Union — Ithaca, NY based community development credit union; small but in the same upstate-NY orbit as HRCCU and frequently appears in regional aggregation requests.
Users who already work with these apps often need unified transaction exports across all of them. The same FDX-aligned adapter we ship for HRCCU is reused, with a different auth flow per institution, so a partner can roll out additional credit unions on the same internal contract.
About OpenFinance Lab
We are an independent technical studio focused on mobile-app protocol analysis, OpenData / OpenFinance integration, and authorized API delivery. Engineers on the team have shipped integrations for retail banks, credit unions, brokerages, payment processors and accounting platforms. We understand the difference between a "scraper" and a member-permissioned, audit-logged data path — and we ship the latter.
- Banking, credit-union and payments specialists with hands-on FDX, Plaid Core Exchange and MX Open experience
- End-to-end pipeline: protocol analysis → build → validation → compliance review
- Custom Python / Node.js / Go SDKs and test harnesses
- Source code delivery from $300 — runnable API source plus full documentation; pay after delivery upon satisfaction
- Pay-per-call API billing — call our hosted endpoint and pay only per call, no upfront cost
Contact
Send us the target app name (already provided here as HRCCU Mobile Banking) and your concrete needs — for example "FDX-aligned read-only feed for transactions and balances, plus mobile deposit webhook." We will reply within one business day with a scoped quote and timeline.
FAQ
What HRCCU data can be exposed through your APIs?
How long does delivery take?
How do you handle compliance for credit union data?
Do you support FDX, Plaid Core Exchange, and MX Open?
📱 Original app overview (appendix)
HRCCU Mobile Banking is the official mobile banking app of Hudson River Community Credit Union (HRCCU), a not-for-profit credit union headquartered in upstate New York. The app gives members 24/7 access to their HRCCU accounts on Android and iOS phones and tablets, on the move and away from a branch.
According to the publisher description, members can securely sign in to view HRCCU account balances and transactions, deposit checks remotely when not near an HRCCU branch, transfer funds among HRCCU accounts, and locate nearby ATMs and branches in HRCCU's network and the broader Shared ATM/Branch Network.
- Secure and convenient access to accounts, balances and transactions for the past 90 days
- View account balances and transaction history 24 hours a day
- Deposit checks using a mobile device (mobile remote deposit capture)
- Schedule transfers between accounts (immediate, future and recurring)
- Schedule, manage and pay bills securely; send money to friends and family
- Apply for a loan and make loan payments inside the app
- Sign in with fingerprint or facial recognition (device dependent)
- Find nearby ATMs and branches owned by HRCCU and partners in the Shared ATM/Branch Network
This page describes how the data and capabilities surfaced by the official app can be exposed to authorized third parties as compliant, FDX-aligned APIs. It is not affiliated with or endorsed by HRCCU.