Pulling Pilot Grove Savings Bank data out of MyPGSB

Two facts shape any MyPGSB build. The portal at mypgsb.pilotgrovesavingsbank.com is a NetTeller deployment, and Jack Henry has published a NetTeller retirement of July 1, 2027 on its Banno statement page. That puts every Pilot Grove integration on a two-year clock against a known migration target — the Banno Digital Platform, also Jack Henry, also API-first by design.

The route we actually recommend for most clients is a consumer-consent pull. It is the basis Pilot Grove customers already use whenever they link their account to a budgeting tool, and it survives the NetTeller-to-Banno cutover with a token rotation rather than a rewrite. Where a client wants something that aggregators do not expose — a specific statement archive, a check-deposit audit trail, raw debit-card-control state — we add a documented protocol implementation against the portal under the customer's authorization.

Routes into MyPGSB account data

Four routes are practically available for Pilot Grove. We score each on what it reaches, the effort to ship it, and how durable it is across the 2027 cutover.

1. Consumer-consent aggregator pull (FDX-aligned)

Plaid, MX, Akoya and Finicity all carry Jack Henry institutions in their networks; Fiserv's Plaid partnership in particular covers thousands of community banks on Jack Henry-equivalent cores. A pull goes through FDX-shaped endpoints — accounts, transactions, statements, identity — under an OAuth-style customer consent. Reach: native PGSB accounts and (with broader scope) the linked accounts a customer has aggregated through My Money Manager. Durability: high. The aggregator absorbs the NetTeller-to-Banno change; the integration sees a token rotation, not a rewrite. We arrange the aggregator account and the developer credentials with the client during onboarding.

2. Direct protocol implementation under customer authorization

For data an aggregator does not return — for example, the SHAZAM-side card controls handled inside brella™, or specific statement-cycle PDFs older than the aggregator window — we implement the MyPGSB / NetTeller request chain directly. Authentication, the MFA challenge, session cookies and the AccountListing / AccountActivity / Statements responses are mapped during the build, with the customer's written authorization on file. Durability: medium until the Banno migration; we schedule a remap visit at cutover.

3. User-consented credential broker

A narrower sibling of route 2: we accept the customer's MyPGSB credentials inside a one-time consent flow, exchange them for a session, and never persist them in cleartext. Useful when the client needs a one-shot historical pull (e.g. five years of statements) rather than a live feed.

4. Native export as fallback

The MyPGSB app already lets a user "view and save your monthly statements" as PDFs (per the bank's own description). For small-volume back-office cases — a single business owner wanting their own statements ingested — a scheduled PDF export plus an OCR/parse pipeline is the cheapest deliverable. We use it when it actually fits; we do not pretend it scales.

Most clients end up paying for route 1 as the daily feed, with a small route-2 carve-out for data the aggregator does not return. That pairing is what survives the 2027 NetTeller sunset with the least re-work.

Where US data rights sit while §1033 is reconsidered

Pilot Grove Savings Bank is supervised by the Iowa Division of Banking under state charter, with FDIC insurance — that part is settled. The federal piece is not. CFPB Section 1033, the Personal Financial Data Rights rule (12 CFR Part 1033), was finalized in October 2024 and would have phased compliance in by asset size. As finalized, since stayed, it would have first hit the largest banks well before community institutions like Pilot Grove. In October 2025 the Eastern District of Kentucky enjoined the CFPB from enforcing the rule, and on August 22, 2025 the CFPB published an Advance Notice of Proposed Rulemaking reopening the four core questions — who counts as a representative, fee assessment, data security and data privacy. The comment window closed in October 2025; no rewritten rule has issued.

We do not build to §1033 as if it governed. The dependable basis for a Pilot Grove pull today is the customer's own authorization, captured and logged, with revocation routed back to the customer. If a future §1033 rewrite changes the contours, the integration is positioned to follow it — the FDX shape Plaid and Akoya already use is the most likely landing — but the page does not pretend the rule is settled when it is in reconsideration.

What sits inside MyPGSB

The table reflects surfaces the app actually carries, mapped to where the data lives and what an integrator typically does with it.

A worked sketch of the pull

The block below is illustrative — a sketch of the request chain a route-2 build follows against the NetTeller front end. Exact endpoint paths and cookie names are confirmed during the integration; Jack Henry institutions run slightly different NetTeller revisions, and the wiring is mapped per deployment.

# Authorized consumer-consent build against a MyPGSB-fronted account.
# Endpoints + cookie names mapped during the integration.
# Host: mypgsb.pilotgrovesavingsbank.com

POST  /login2008/Authentication/Login
      body  : { user_id, password, device_fp }
      sets  : NetTellerASP.NET_SessionId; ASP.NET_SessionId

POST  /login2008/Authentication/Challenge
      body  : { challenge_id, answer, remember_device: true }
      # MFA fires on first-seen-device; remember_device suppresses it next time

GET   /login2008/AccountListing/GetAccounts
      → [{ account_id, masked_number, type,
            current_balance, available_balance, last_activity }]

GET   /login2008/AccountActivity/Get
      ?account_id=<id>&start=YYYY-MM-DD&end=YYYY-MM-DD
      → [{ posted_at, amount, description,
            balance_after, category_mmm }]

GET   /login2008/Statements/View
      ?account_id=<id>&period=YYYY-MM
      → application/pdf  (archive + OCR fallback for older cycles)

# Refresh policy
# Session cookies survive ~15–30 min idle; the build refreshes
# on a heartbeat and re-authenticates cleanly when the cookie dies,
# so a long-running sync does not get stuck waiting on an MFA prompt.

For a route-1 build the same data domains arrive shaped to the FDX schema the aggregator exposes — accounts, transactions, statements, identity — and the auth chain is replaced by an OAuth handshake the aggregator handles. The two shapes are reconciled in a thin adapter so the downstream code does not care which route fed it.

What gets handed over

Every Pilot Grove build hands back a concrete set of artefacts. The list is tied to the surfaces above, not a generic deliverables menu:

• OpenAPI 3.1 specification covering the five primary endpoints (accounts, activity, statements, transfers, card-state) in the shape the client will call, whether the back end is route 1 or route 2.
• Auth-flow report documenting the NetTeller login + MFA chain, cookie lifetime, refresh behaviour, and the aggregator-side OAuth equivalent. Includes a session-state diagram.
• Runnable source in Python (httpx + pydantic) and Node.js (fetch + zod) for the daily balance pull, monthly statement archive, transaction sync, and a webhook adapter for transfer-status events.
• Test fixtures recorded against a consenting account, replayable offline so the client can run the suite without re-burning a live session.
• Interface documentation covering field semantics, MMM-versus-native data paths, and the 2027 Banno migration plan with the exact endpoints that will need re-mapping.
• Consent and data-retention guidance — consent capture, scope, refresh window, revoke endpoint, and a logging schema that satisfies Iowa state-banking expectations and survives whatever §1033 becomes.

Engineering notes that shape a Pilot Grove build

Three things genuinely matter for this app, and we account for them up front rather than hitting them in week three:

• The 2027 NetTeller sunset. Jack Henry's published date is July 1, 2027 per Banno's monthly statement page. We ship the first cut against the current portal and plan a maintenance pass timed to Pilot Grove's cutover to Banno, so the integration does not break on migration day. Banno is 100% API-enabled by Jack Henry's own description, which makes the cutover a remapping rather than a re-architecture.
• The MMM data path is not the same as the native one. My Money Manager aggregates external accounts inside MyPGSB; that data is third-party-fed, not core-fed. We scope the consent and the schema so native PGSB accounts and aggregated externals are handled as separate sources with a clear merge step, rather than as one undifferentiated feed.
• NetTeller's MFA + session model is per device. The first session from a new device fingerprint triggers MFA; subsequent sessions ride a remember-device flag. We tune the heartbeat and re-auth path so a long-running sync does not silently stall on a challenge prompt, and we document the fingerprint contract so the client can rotate hosts without losing the trust state.
• brella™ is a separate auth domain. Debit-card controls live in the SHAZAM-network app, with its own login. If the brief includes card-state, we set up the brella-side access with the client and treat it as a second token store rather than pretending it shares MyPGSB's session.

Access, consent capture, and any sponsor or sandbox arrangement are handled with the client during onboarding — not framed as paperwork the client clears before we begin. The compliance posture (authorized, logged, data-minimized, NDA where the client needs one) is how we operate, not a gate.

How a MyPGSB engagement is priced and shipped

A working MyPGSB pull starts at $300 for source-code delivery — runnable code for the endpoints above, the OpenAPI spec, the test fixtures and the interface documentation, paid only after delivery once the client has checked it works against their own accounts. The hosted alternative is the pay-per-call option: call our endpoints on demand and pay only for what gets used, no upfront fee. Delivery cycle is one to two weeks for either model.

The simplest start is the app name and what you want from its data — send the brief at /contact.html and we'll come back with the route, the scope, and a price.

How this was put together

The brief draws on the bank's public materials (the MyPGSB description on Google Play and Apple's App Store, the NetTeller portal at mypgsb.pilotgrovesavingsbank.com, the My Money Manager and brella pages on the bank's site), Jack Henry's own Banno statement page on the NetTeller retirement, the Federal Register notice on the CFPB §1033 reconsideration, and the FDX standard documentation. Specific citations:

• MyPGSB on Google Play (com.pilotgrovesavingsbank.grip)
• Banno monthly statement — NetTeller retirement notice (July 2025)
• Federal Register — Personal Financial Data Rights Reconsideration (Aug 22, 2025)
• Pilot Grove Savings Bank — My Money Manager

Reviewed by the OpenBanking Studio integration desk, May 2026.

Adjacent community-bank apps

If a client is integrating MyPGSB they often need a handful of neighbouring institutions in the same pull. These are the same-category apps a unified integration commonly sits across — listed as plain references, not endorsements:

• brella™ — the same bank's SHAZAM-issued debit-card companion app; holds card-on/off state, transaction controls and freeze status that the main MyPGSB app does not expose.
• My Two Rivers — Two Rivers Bank & Trust's mobile app, another southeast-Iowa community bank with overlapping customer demographics.
• FSB Now — Farmers State Bank (Iowa) mobile banking app, common alternative for eastern-Iowa account holders.
• Hills Bank Mobile — Hills Bank and Trust (Iowa City area) account access and transfers, common in the same regional footprint.
• Greater Iowa Mobile Banking — Greater Iowa Credit Union app, balances, transfers and messaging for credit-union members alongside community-bank customers.
• MO Central Mobile Banking — Missouri Central Credit Union, the northeast-Missouri side of Pilot Grove's footprint.
• Iowa State Bank Mobile — Iowa State Bank & Trust (Ottumwa / Centerville), mobile deposit, transfers and ACH origination.
• First Community CU — St. Louis-area credit union app with card-controls inside the mobile banking flow, frequent overlap with PGSB's southwest-Illinois customers.

Each of these speaks a similar shape of data — accounts, transactions, statements, transfers — and a single FDX-aligned consent layer can carry them into one unified feed.

Questions a Pilot Grove integrator asks

Mapping reviewed 2026-05-24.