St. Johns Bank & Trust Company has served northwest St. Louis and St. Charles County, Missouri since 1926. Family-managed, locally held under parent Unity Bancshares LLC, the bank runs a well-bounded digital footprint: four branches, a Jack Henry Banno-powered mobile app (Android package com.stjohnsbank.grip), and a customer base that does most of its day-to-day banking through that single app.
For fintech developers, aggregators, PFM tools, and accounting platforms, this smallness is an advantage. The data behind login is tightly scoped — checking, savings, loan products, statement PDFs, mobile-deposit history, bill pay, and account-to-account transfers — with no exotic instrument types to model. The March 2024 platform cutover introduced a new digital-banking experience with unified mobile-and-web design and mandatory two-factor authentication on first sign-in. Any integration targeting the old platform will not authenticate against the current system.
OpenBanking Studio maps the post-March-2024 surface and delivers a runnable integration — source-code or pay-per-call endpoint — that exposes St. Johns Bank account data through a clean, developer-friendly API layer.
Learn more and start an engagement at:
https://openbankingstudio.com/st-johns-bank.html
--------------------
SUPPORTED API FEATURES
--------------------
The St. Johns Bank integration surfaces the full range of data visible to an authenticated accountholder through the Jack Henry Banno app. Key capabilities include:
Account list and real-time balances across checking and savings products
Full transaction history with memo, amount, sign, posted and effective dates
Monthly statement PDF retrieval by billing cycle
Mobile-deposit history including accepted-deposit list and front/back check images
Internal and external transfer records — initiated and posted entries
Bill-pay activity — payee list, scheduled and historical payments
Alert configuration mirroring — low-balance thresholds and delivery channels
OpenAPI specification for all exposed endpoints, ready to consume
Runnable source in Python or Node.js with typed clients and a CLI smoke-tester
Auth-flow report covering the post-March-2024 login handshake and 2FA capture
Automated unit and integration tests against a consenting test account
Compliance and retention notes: no PAN stored, no full statements at rest
------------
INTEGRATION ROUTES
------------
Three delivery paths are available depending on buyer footprint and use case:
[Route A] Customer-consented session through the app — the accountholder authorizes in writing, supplies credentials and the 2FA factor at first sign-in, and the integration drives the same session a person would. Works for any St. Johns Bank account today without depending on what the bank publishes externally.
[Route B] Native export baseline — statements export as PDFs and transaction history exports to CSV/QFX from the desktop view. Low-risk baseline for accounting integrations or historical backfill.
[Route C] Aggregator-mediated open-banking connection — Jack Henry has been migrating Banno-platform institutions onto API-based links with Finicity, Akoya, and Plaid. Applicable when the buyer already holds an aggregator relationship with one of those providers.
============================
USE CASES & APPLICATIONS
============================
[1] Personal Finance Management (PFM) Tools
Pull real-time balances and categorized transactions into spending dashboards
Mirror existing low-balance alert thresholds from the bank app into a third-party tool
Build cash-flow forecasting panels using per-account balance snapshots
Aggregate St. Johns Bank data alongside accounts from other Missouri community banks
[2] Accounting and Bookkeeping Platforms
Import transaction history with memo and category hints for automated reconciliation
Retrieve monthly statement PDFs for year-end accounting packs and audit collections
Match mobile-deposit credits to accounts-receivable records for small businesses
Export to CSV/QFX for legacy bookkeeping tools with no custom parser required
[3] Lending and Document Collection
Pull statement PDFs automatically during loan origination document workflows
Retrieve balance snapshots for income and asset verification
Access transaction history within configurable date windows for underwriting inputs
Automate payee and bill-pay history retrieval to verify recurring obligations
[4] Account Aggregation Services
Integrate St. Johns Bank alongside Midwest BankCentre, Reliance Bank, and other
Missouri community banks under a single normalized data contract
Wire in the Jack Henry Banno open-banking layer via Finicity, Akoya, or Plaid
for buyers who already hold aggregator relationships with those providers
Normalize transaction data across community bank formats for unified reporting
[5] Business Treasury and Operations Platforms
Cover business checking and savings accounts through a separate authorization scope
Access ACH batch records, wire entries, and entitlement roles (signer, viewer,
ACH originator) as a second integration target priced independently from retail
Monitor scheduled transfers and bill-pay entries for corporate cash-management tools
Track mobile-deposit history and resulting credits for AR matching workflows
============================
BENEFITS & ADVANTAGES
============================
Customer-consented access — authorization basis rests on the accountholder's own
consent under Reg E and the bank's online-banking agreement, with a signed record
kept on file and an explicit revocation path available to the accountholder.
Post-March-2024 platform coverage — the integration is built against the current
Jack Henry Banno surface, not the retired prior platform. The auth chain is designed
to survive minor Banno UI revisions, and a monthly smoke-test job ships with handover.
No-surprise delivery model — source-code payment is due only after the codebase is
in your repo, smoke tests pass on your machine, and you have signed off. No upfront
commitment required.
Complete deliverables package — OpenAPI spec, auth-flow report, runnable Python or
Node.js source, automated tests, interface documentation, and compliance notes all
land in your repository in one handover.
Retail and business scopes independently priced — smaller buyers are not charged for
business-banking entitlement plumbing they do not need. The retail path (checking,
savings, statements) and business path (ACH batches, wires, entitlements) are
separate line items.
Aggregator-compatible — for buyers who already plug into Finicity, Akoya, or Plaid,
the integration can wire in the Jack Henry open-banking connection alongside the
direct customer-consent route as a parallel path.
Minimal data footprint by design — the integration deliberately avoids logging
PANs or storing full statements at rest; compliance and retention notes document
exactly what is logged, where the consent record lives, and how revocation works.
Two delivery models are available with no long commitment required on either path.
------------
Source-Code Delivery
------------
Starts at $300. Payment is collected only after the codebase is in your repository,
the smoke tests pass on your machine, and you have signed off on the integration.
Includes the full deliverables package: OpenAPI spec, auth-flow report, runnable
source (Python or Node.js), automated tests, Markdown documentation, and compliance
notes. One to two weeks from kickoff to handover.
------------
Pay-Per-Call Endpoint
------------
No upfront cost. Billed per call against the hosted endpoint. Suited for buyers who
want to skip the run-ops and maintenance side entirely and consume St. Johns Bank data
as a managed service. The same data domains are available — balances, transactions,
statements, deposits, transfers, bill pay — through a documented endpoint with no
local infrastructure required.
Business-banking scope (ACH batches, wires, entitlements) is priced separately from
retail on both delivery models. Contact the team via the engagement page for a
business-only scope quote.
St. Johns Bank represents a well-bounded integration target: a locally held Missouri
community bank with a clean Jack Henry Banno digital footprint, predictable data
domains, and a customer base that concentrates its activity on a single mobile app.
For fintech platforms, aggregators, PFM tools, and accounting systems serving the
St. Louis metro area or building multi-bank Midwest coverage, pulling this data into
a normalized API layer is a one-to-two-week effort with clearly scoped deliverables
and a consent-first authorization model.
Whether the goal is real-time balance feeds, statement retrieval for lending workflows,
transaction categorization, or business-treasury coverage, the integration described
here maps the current post-March-2024 platform surface and ships as runnable code
ready to drop into your stack.
To start an engagement — send the app name and a short note on what the integration
is for — visit the full integration brief at:
https://openbankingstudio.com/st-johns-bank.html
The team handles access, the consent paperwork with the accountholder, the test
environment, and the build, and replies with a first-week plan.
============================
2026 OpenBanking Studio
St. Johns Bank is a separately operated FDIC-insured institution.
This article is independent integration research and is not affiliated
with St. Johns Bank, Unity Bancshares LLC, or Jack Henry & Associates.
============================