First Guaranty Bank Mobile (MyFGB) API integration

1. Authentication & consent

Mirrors the MyFGB online-banking login flow, including biometric step-up and Out-of-Band device binding. Sessions are wrapped in an OAuth-style envelope with refresh tokens and per-scope grants (read:balances, read:transactions, write:transfer), so callers never touch raw banking credentials. Useful for reconciliation tools and personal-finance dashboards that need standing access without re-prompts.

2. Balances & account inventory

Returns FGB checking, savings, money-market and demand accounts with available, current and hold balances, plus the unauthenticated PreView snapshot used by the app's home-screen peek. Includes account-number masking, routing-number echo and product-code mapping so downstream systems can classify each account without bespoke lookups.

3. Transaction history & statement export

Paged transaction feed (default 50 rows) with date-range, type and amount filters. Covers posted, pending and authorization-hold rows, merchant-cleaned descriptions, MCC enrichment, eBills line items and bill-pay debits. Exports to JSON, CSV, Excel and bank-grade PDF for download or attachment to accounting workflows.

4. Transfers, bill pay & P2P

Initiates intra-bank transfers, external ACH transfers and pay-a-friend P2P pushes, mapped to FGB's online bill-pay backend. Supports biller add, recurring schedule and same-day vs. standard ACH dispatch flags. Webhooks signal status transitions (queued, sent, returned), which is what reconciliation tools need rather than nightly batch files.

5. Mobile check deposit ingestion

Wraps the mobile remote deposit capture (RDC) pipeline so partner accounting tools can attach signed check images, recommended endorsements and deposit references against the resulting credit. Limits, eligibility flags and hold-release dates are exposed, which makes downstream cash-availability forecasting accurate.

6. Locator & service metadata

Branch and ATM locator with hours, drive-through availability and MiBY (FGB's Interactive Teller Machine) flags, plus the secure-messages metadata feed (counts, unread badges). This is the data corporate dashboards and treasury portals tend to forget about, but it removes a recurring source of customer-support tickets.

A. Small-business bookkeeping sync

An LA-based contractor uses QuickBooks Online or Xero and needs nightly imports of FGB checking activity. We map MyFGB transactions to FDX /accounts/{id}/transactions output, then push them into the accounting platform's import endpoint. Bill-pay debits and mobile-deposit credits flow as separate transaction-type codes so the bookkeeper does not need to manually reclassify. Maps cleanly to OpenBanking "data-aggregator" patterns under CFPB Section 1033.

B. Mortgage application packaging

Origination platforms need 60–90 days of statements plus current balance proof when underwriting an FGB customer for a one- to four-family residential loan (an FGB specialty). We expose a single signed-PDF statement endpoint plus a structured-rows endpoint so verifiers can both eyeball and machine-check the same data. This replaces emailed PDFs and shortens VOA (verification of assets) turnaround.

C. Treasury cash-positioning for SMBs

A Kentucky construction firm with three FGB operating accounts wants a single dashboard showing available cash, outstanding bill-pay debits and pending RDC holds. We pipe balances and pending-transaction streams into a websocket fan-out; the dashboard renders a same-day cash-position view. This is exactly the gap that FDX v6.4/v6.5 endpoints are designed to fill for US community banks.

D. Personal-finance management (PFM) link

A consumer-facing PFM (think Monarch, Copilot, Empower-style) requests scoped read access. We provide an OAuth-style consent screen and FDX-shaped /accounts, /transactions and /statements endpoints. Aggregators such as Plaid, MX or Yodlee can route to this surface or be replaced entirely, depending on the customer's preference around per-call cost and data freshness.

E. Compliance-ready audit feed

Banks providing third-party data access need consent records, scope, IP, user-agent and revocation events for every retrieval. We emit a parallel audit stream (immutable, append-only) so the bank's compliance team can demonstrate Section 1033 alignment, GLBA safeguards and FFIEC examination readiness without rebuilding observability.

Consent / token exchange (OAuth-style, FDX-aligned)

POST /api/v1/myfgb/oauth/token
Content-Type: application/x-www-form-urlencoded

grant_type=authorization_code
&code=<CONSENT_CODE>
&client_id=<PARTNER_ID>
&client_secret=<PARTNER_SECRET>
&redirect_uri=https://partner.example/cb
&scope=read:accounts%20read:transactions%20write:transfer

Response (200):
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rt_...",
  "expires_in": 1800,
  "token_type": "Bearer",
  "scope": "read:accounts read:transactions write:transfer",
  "consent_id": "con_8af2b9"
}

Transaction history (FDX shape)

GET /api/v1/myfgb/accounts/{accountId}/transactions
  ?fromDate=2026-04-01&toDate=2026-04-30&type=DEBIT&page=1
Authorization: Bearer <ACCESS_TOKEN>
X-Consent-Id: con_8af2b9

Response (200):
{
  "transactions": [
    {
      "transactionId": "tx_01HZ9...",
      "postedTimestamp": "2026-04-12T16:23:00Z",
      "amount": "-84.50",
      "currency": "USD",
      "description": "BILL PAY - ENTERGY LA",
      "category": "Utilities",
      "status": "POSTED",
      "type": "DEBIT"
    }
  ],
  "page": 1,
  "totalPages": 14,
  "nextCursor": "cur_4f..."
}

Transfer initiation + webhook

POST /api/v1/myfgb/transfers
Authorization: Bearer <ACCESS_TOKEN>
Idempotency-Key: 8f1c-...-b30a

{
  "fromAccountId": "acc_chk_001",
  "toAccountId":   "acc_sav_002",
  "amount":        "250.00",
  "currency":      "USD",
  "memo":          "Monthly sweep"
}

Webhook: POST https://partner.example/hooks/myfgb
{
  "event": "transfer.completed",
  "transferId": "trf_01HZB...",
  "status": "POSTED",
  "occurredAt": "2026-04-12T16:25:01Z"
}

US regulatory alignment

MyFGB integrations are scoped to US financial-services rules. We follow the CFPB Personal Financial Data Rights rule (Section 1033 of Dodd-Frank), the FDX field-naming and security recommendations recognized by the CFPB in January 2025, and apply the GLBA Safeguards Rule and FFIEC Authentication and Access guidance to every data flow. FDIC Certificate 14028 identifies First Guaranty Bank as a federally insured institution, which sets the baseline for our data-handling assumptions.

Privacy & minimization

Every endpoint carries a scope and a consent ID. PAN-style values are masked at the gateway, statement PDFs are signed and short-lived, and access tokens default to 30 minutes with refresh. We never bypass MyFGB's multifactor or device-binding logic; instead, partner apps surface the bank's own challenge. Audit logs are retained on the bank side and replicated to the partner only as redacted metadata.

PNC Mobile Banking

PNC's app holds checking, savings, Virtual Wallet and bill-pay data across a large US footprint. Customers who bank with both FGB and PNC frequently want a single feed combining both institutions' transactions and balances.

Chase Mobile

Chase Mobile stores card, mortgage, auto-loan and Zelle transfer history. Where FGB serves community-bank customers, Chase often shows up as the secondary household account, so a normalized PFM feed has to ingest both.

Bank of America Mobile Banking

BofA's app exposes deep merchant-cleaned transaction descriptions and Erica-driven insights. Pairing FGB data with BofA data in a single FDX feed is a typical request from regional accountants serving cross-bank clients.

Capital One Mobile

Capital One's app is strong on credit-card statements and 360 checking. A unified export across FGB checking and Capital One cards gives a more honest cash-flow picture for SMB owners.

Wells Fargo Mobile

Wells Fargo's app holds deposit, brokerage and bill-pay records. Integration teams often align FGB transfer events with Wells Fargo ACH receive events to reconcile B2B payouts.

Hancock Whitney Mobile

Hancock Whitney is another Gulf-South community bank with similar deposit and SMB products. Joint analytics across Hancock Whitney and FGB is common for Louisiana-based bookkeepers.

Regions Mobile Banking

Regions Bank operates across many of the same states (LA, TX, KY) as FGB. A combined transaction-history view across Regions and FGB is frequently requested by treasury teams managing multi-location SMBs.

Truist Mobile

Truist holds retail and small-business data across the Southeast. Onboarding flows that aggregate FGB plus Truist accounts via FDX endpoints surface in many mortgage and lending applications.

Red River Bank Mobile

Red River Bank is a Louisiana community bank with overlapping customer geography. Migration utilities that pull statements from one and push them into a unified ledger format are a recurring scenario.

Frost Bank Mobile

Frost serves Texas customers heavily, and the Texas overlap with FGB means joint deposit, transfer and bill-pay datasets are commonly federated into a single OpenFinance feed.

Deliverables checklist

• OpenAPI / Swagger spec aligned with FDX v6.5 field names
• Protocol and auth-flow report (OAuth, token refresh, device-binding notes)
• Runnable source for login, balances, transactions and statement endpoints (Python and Node.js)
• Webhook samples for transfer.* and deposit.* events
• Automated tests, Postman collection and Markdown reference docs
• Compliance guidance covering GLBA Safeguards, FFIEC IAM and CFPB Section 1033

Engagement workflow

1. Scope confirmation: identify which MyFGB surfaces matter (balances, statements, bill pay).
2. Protocol analysis and API design (2–5 business days)
3. Build and internal validation against sandbox or authorized data (3–8 business days)
4. Docs, sample apps and test cases (1–2 business days)
5. Typical first delivery: 5–15 business days; third-party processor approvals can extend timelines.

About us

OpenFinance Lab is an independent studio focused on OpenData, OpenFinance and OpenBanking integrations. Our engineers come from US community banks, payment processors, mobile-app protocol-analysis backgrounds and cloud platforms, so we understand both the regulatory reality of FFIEC-examined institutions and the engineering reality of FDX-shaped APIs.

• Community-bank, regional-bank and credit-union OpenBanking integrations
• Enterprise API gateways, scope-aware consent, audit-grade logging
• Custom Python, Node.js and Go SDKs plus end-to-end test harnesses
• Full pipeline: protocol analysis → build → validation → compliance handoff
• Source code delivery from $300 — runnable API source code plus documentation; pay after delivery upon satisfaction
• Pay-per-call API billing — hosted endpoints, billed only on actual calls, with no upfront cost

Contact

To request a quote or submit your target app and requirements, open our contact page:

Contact page