How to reach a member's My GBT data — balances, pending posts, deposit images

Inside My GBT, a member's money moves as a few distinct things: an available balance and a current balance that rarely match, a queue of pending card and Zelle items waiting to post, images of deposited checks and of checks the member has written, and a thread of secure messages with the branch. Guaranty Bank and Trust Company has banked the Mississippi Delta out of Belzoni since 1943 — FDIC BankFind lists it under certificate 15953 — and today runs roughly three dozen branches across Mississippi and Tennessee, per public aggregator listings. My GBT is where those members read their accounts. This page covers what that data is, the member-authorized way to reach it, and what OpenFinance Lab ships when you hire us to build the connection.

The bottom line: everything a member sees in My GBT is server-side state behind a device-bound login, so the dependable way to read it is with that member's permission — not a scrape pretending to be them. We map the app's own session and transaction traffic, model the available-versus-current balance math, and hand you a feed your systems can poll or receive on a schedule. Where a member only needs records out, the statement and check-image exports cover the slower path.

What a member's account actually holds

Mapped to where each surface lives in the app, and what an integrator does with it:

Pending, posted, and the freshness window

Two numbers on the My GBT dashboard rarely agree: available balance and current balance. The gap is the pending set plus any deposit holds, and it is the part naive integrations get wrong. We treat current balance as the source of record and available balance as derived, so a pending Zelle debit or a card authorization is not counted twice when it finally posts. Items are keyed on their My GBT item id; when one flips from pending to posted we update in place rather than appending a duplicate. Mobile check deposits get their own clock — the image lands at once, the funds clear on a hold window — so the feed marks deposited money as un-spendable until that window closes. What you get is a reconciliation that holds at the close of each banking day, not a running total that drifts.

How we reach the account data

We work three routes here, and they are not equal.

Member-authorized session integration

With the member's authorization we capture and map My GBT's own login, OTP step-up, and account and transaction calls, then implement them as a stable client. This returns the full set a member sees — live balances, the pending queue, posted history, images. Effort is moderate; durability is tied to app updates, which we re-validate on a maintenance cadence. Access is arranged with you during onboarding, against a consenting member account or a sandbox.

User-permissioned aggregation

The consumer, as a member, authorizes access to their own data. The scope is narrower than full session mapping today, but the consent model carries straight over if and when a US data-access rule settles into force.

Native export fallback

Statements (PDF/CSV) and the deposit and check images a member can already download. Lowest effort, slowest cadence, and no live balance math — useful when a member simply needs records out.

For most teams the session route is the one worth building. It returns the live balance math and the pending queue the export path can't, and we keep it current as the app changes.

What we hand back

Code first. You get a runnable client — Python and Node.js — that performs the device-bound login and OTP step-up, pulls balances, walks the posted-and-pending feed, and retrieves deposit and check images. Around it sits a test harness with fixtures for the cases that actually bite: a pending item posting, a held mobile deposit, a Zelle transfer that settles a day late. A poller, or a small webhook handler where the project warrants pushing events onward, drives the scheduled sync and the day-close reconciliation. Then the paperwork that keeps it maintainable: an OpenAPI description of the mapped surface, a written account of the auth and token chain, and a short data-retention and consent note for your compliance file.

Reading the posted-and-pending feed

An illustrative shape of the session-and-transaction flow — confirmed against captured app traffic during a build, not a published My GBT endpoint:

# Device-bound login, then OTP step-up
POST /mobile/auth/session
  -> 200 { "session_token": "...", "expires_in": 900, "mfa": "passed" }

# Posted + pending in one call, scoped by date
GET  /mobile/accounts/{acctId}/transactions?status=posted,pending&since=2026-05-01
  Authorization: Bearer <session_token>
  -> 200 {
       "balance_available": 1843.22,
       "balance_current":   1903.22,
       "items": [
         { "id": "t_88f1", "status": "pending", "amount": -60.00,
           "desc": "ZELLE TO ...", "posted_at": null },
         { "id": "t_88e0", "status": "posted",  "amount": -24.13,
           "desc": "CARD PURCHASE", "posted_at": "2026-06-06" }
       ]
     }

# Reconcile: pending items carry posted_at = null. The 60.00 gap between
# current and available is the pending sum plus holds. When t_88f1 posts,
# match on id and update in place — never append a second row.
      

Consent and the US data-rights picture

Guaranty Bank and Trust Company is a Mississippi state-chartered, FDIC-insured bank (certificate 15953 on FDIC BankFind), so a member's account data sits under federal bank-privacy law — Gramm-Leach-Bliley and its safeguards — alongside Mississippi's own supervision. The dependable footing for any integration here is the member's own authorization to reach their data: we build on consent, with consent records, an NDA where the engagement needs one, and data kept to what the use case requires. The CFPB's Personal Financial Data Rights rule (Section 1033) is where US open banking may eventually land, but it is not in force. A federal court in the Eastern District of Kentucky enjoined enforcement in late October 2025, and the Bureau reopened the rule for reconsideration through an August 2025 notice, leaving the planned April 2026 first compliance date in limbo, per CFPB and court reporting. We treat §1033 as a direction of travel, not a present obligation, and rely on the member's consent today.

What this build has to account for

A few specifics of My GBT shape the work, and we plan around them rather than hand you a list of conditions.

• Available versus current balance is computed, not stored as one figure. We carry both and derive availability from the pending set and any holds, so downstream systems never treat pending money as spendable.
• The app lets a member add outside accounts to view balances. We keep Guaranty-held data separate from those aggregated third-party balances, so the feed never presents another institution's numbers as Guaranty's.
• Deposited-item images and copies of checks written are first-class records here, not an afterthought. We pull each with the transaction it belongs to and store the linkage, which is what makes them usable for proof-of-payment or audit later.
• Access is arranged with you during onboarding — a consenting member account or a sandbox — and the session and OTP flow is re-established within its window so the sync keeps running.

Where teams put a My GBT feed

• A Delta small business reconciling daily card and Zelle settlement against its own books.
• An accounting tool pulling posted transactions and check images for a member's bookkeeping.
• A personal-finance app folding a My GBT balance into a member's net-worth view alongside their external accounts.
• A lender verifying recent deposit history, images included, with the member's permission.

Neighboring banking apps in Mississippi and Tennessee

Same category, same region — useful when a project needs one integration layer over several community banks:

• Trustmark (myTrustmark) — Jackson, MS; holds a member's balances, transfers, mobile deposit and bill pay across a multi-state footprint.
• Renasant Bank — Tupelo, MS; account balances, mobile deposit and payments across MS, TN, AL, GA and FL.
• Cadence Bank — regional bank with deposit, card and lending records behind its app.
• BankPlus — Mississippi bank with a wide Delta and central-state footprint; checking, savings and bill-pay records.
• Citizens National Bank — Meridian, MS; community-bank balances and transaction history.
• Planters Bank & Trust — Indianola, MS; deposit accounts and online banking.
• The Peoples Bank — Biloxi, MS; coastal community bank with mobile deposit and transfers.
• BNA Bank — New Albany, MS; north-Mississippi deposit and payment records.
• First Horizon — Memphis, TN; broader regional bank with accounts, cards and payments.
• Pinnacle Financial Partners — Nashville, TN; community-style bank app with deposit and transfer data.

Questions integrators bring us

My GBT lists pending and posted transactions separately — how does an integration keep the two reconciled?

We key every item on its My GBT id and treat current balance as the record of truth, with available balance derived from the pending set and any deposit holds. When an item moves from pending to posted we update it in place, so nothing is counted twice, and the feed reconciles cleanly at the close of each banking day.

Can you pull mobile-deposit images and copies of checks written, or only the transaction lines?

Both. The images are a first-class surface in My GBT, so we retrieve each one alongside the transaction it belongs to and preserve the link, which is what makes them usable for proof-of-payment, bookkeeping or audit.

With CFPB Section 1033 enjoined, what's the legal basis for reaching My GBT data?

The member's own authorization. A federal court paused enforcement of the Personal Financial Data Rights rule in late October 2025 and the CFPB reopened it for reconsideration, so we don't rely on it. We build on the member's consent, with consent records and data minimization, and Guaranty's data stays under bank-privacy law either way.

Will I get runnable source for the My GBT login and transaction pull, or only documentation?

Runnable source. You receive a working Python and Node.js client that handles the device login and OTP step-up, balances, the posted-and-pending feed and image retrieval, with a test harness and the auth-flow write-up alongside it.

Starting a build

Source-code delivery starts at $300: we build the My GBT client and its docs, and you pay after it lands and works to your satisfaction. If you would rather not run anything yourself, the hosted option lets you call our endpoints and pay per call, with nothing upfront. Either way the build runs in about one to two weeks once we have scoped what you need from the account data. Tell us the surfaces you want and how you will use them — Start a build

Screens from My GBT

What I checked, and when

I worked from the My GBT listings on the App Store and Google Play (feature set, data-collection labels, and the package com.guarantybankandtrust4290.mobile per the Play listing), the bank's own site and FDIC BankFind for its charter and Belzoni base, and CFPB and court reporting for the current status of US open-banking rules. Checked 2026-06-08.

• My GBT on the App Store
• FDIC BankFind — Guaranty Bank and Trust Company (cert 15953)
• CFPB — Personal Financial Data Rights Reconsideration
• Guaranty Bank and Trust Company — gbtonline.com

OpenFinance Lab · protocol assessment — June 2026.