Plug Quail Creek Bank Mobile data into your accounting, ERP, or fintech back office
Quail Creek Bank, N.A. is a community bank headquartered in Oklahoma City. Its retail mobile app is built on the Apiture Xpress Mobile platform (Android package com.apiture.xpressmobile.qcbocok.sub) and acts as the customer-facing surface for checking and savings accounts, Bill Pay, internal transfers, Zelle P2P, and remote check deposit. Each of those screens is a structured data source we can expose through an integration layer.
Data available for integration
The table below maps each in-app surface to the structured records that an integration layer can expose. We do not enumerate fields we cannot legitimately reach — each entry corresponds to a screen or capability documented in the public app description or in the Apiture Xpress Mobile feature list.
| Data type | Source (screen / feature) | Granularity | Typical downstream use |
|---|---|---|---|
| Account balance | Accounts tab — current and available balance per account | Per account, near-real-time on refresh | Cash-position dashboards, treasury sweeps |
| Transaction history | Account detail — searchable by date, amount, check number | Per posting; deposits, debits, ACH, card, P2P | Accounting sync, reconciliation, expense tagging |
| Scheduled & recent Bill Pay | Bill Pay — recent and scheduled payments view | Per payment: payee, amount, send date, status | AP forecasting, double-payment guards |
| Payees | Manage Payees — add / remove from the mobile app | Per payee record | Vendor master sync, payee whitelist enforcement |
| Internal transfers | Transfers — between same-customer accounts | Per transfer event | Liquidity moves, automated sweeps |
| Mobile check deposits (RDC) | Deposits — camera capture of paper checks | Per item: amount, capture timestamp, status | Receivables matching, fraud screening |
| Zelle P2P | Person-to-Person payments via Zelle | Per send/receive event | Customer-payment automation |
| Real-time payment events | FedNow / RTP credits and Request-for-Payment | ISO 20022 message per event | Instant treasury notifications, webhook fan-out |
| Card controls | SecurLOCK Equip — card on/off, alert rules | Per card | Risk control, lost-card automation |
Typical integration scenarios
1. QuickBooks / NetSuite reconciliation for a Quail Creek Bank business customer
An Oklahoma City small business uses Quail Creek Bank as its operating account and NetSuite as its general ledger. We expose GET /accounts/{id}/transactions?from=&to= on top of the Apiture Xpress session and run a nightly sync job that posts journal lines into NetSuite, matching the same date / amount / check-number search that the in-app Accounts tab supports. The OpenFinance angle is straightforward: a CFPB Section 1033 personal-financial-data style read endpoint, scoped to the customer's own data.
2. Bill Pay automation from an AP workflow
A property-management firm pushes vendor bills from its internal AP tool into Quail Creek Bank Mobile Bill Pay. We wrap the "Manage Payees" and "Make a payment" flows behind POST /bill-pay/payees and POST /bill-pay/payments. Each scheduled payment is mirrored back into the AP tool with an idempotency key so the same invoice cannot be paid twice. This is the OpenBanking "payment initiation" pattern adapted to a US community-bank context.
3. FedNow / RTP webhook fan-out for treasury
Quail Creek Bank is a FedNow and RTP participant. We subscribe to incoming-credit and Request-for-Payment events on the bank's behalf via the Apiture event surface, normalise them into ISO 20022 pacs.008 / pain.013 shapes, and fan them out as signed webhooks to your treasury platform. Settlement happens in seconds rather than the next business day, which is the whole point of the Federal Reserve's instant rail.
4. Remote deposit capture pipeline
A rental-business customer receives paper checks. Their staff captures images in the Quail Creek Bank Mobile Deposits screen; we pull deposit status and amount back via GET /rdc/items and post a "received" event into the property-management system, including the captured image hash for audit. This avoids manual reconciliation between paper receipts and the ledger.
5. Card-control automation for fraud response
SecurLOCK Equip card controls are exposed through Quail Creek Bank's digital-banking stack. We wrap "card on/off" and alert thresholds in a PATCH /cards/{id}/controls endpoint your fraud platform can call within milliseconds of a suspicious authorization — closing the loop between detection and containment without a human in the chain.
Technical implementation
We deliver a thin gateway service in Python (FastAPI) or Node.js (Express/Fastify) that fronts the Apiture Xpress session, normalises responses into OpenAPI-typed shapes, and handles token refresh, retries, and idempotency. Below are illustrative request/response shapes — the actual contract is finalised in the spec phase against your sandbox.
1. OAuth-style session bind
POST /api/v1/qcb/session
Content-Type: application/json
{
"username": "<customer-online-banking-id>",
"password": "<customer-credential>",
"mfa": {"channel": "biometric", "token": "<device-bound-token>"}
}
200 OK
{
"access_token": "eyJhbGciOi...",
"refresh_token": "rft_...",
"expires_in": 1800,
"scope": ["accounts:read","billpay:write","rdc:read"]
}
2. Transaction statement export
GET /api/v1/qcb/accounts/{accountId}/transactions
?from=2026-04-01&to=2026-04-30
&type=ACH,UPC,CHECK&limit=200
Authorization: Bearer <access_token>
200 OK
{
"account_id": "acc_8021",
"items": [
{
"txn_id": "txn_91f2",
"posted_at": "2026-04-12T14:08:00Z",
"amount": -128.43,
"currency": "USD",
"channel": "DEBIT_CARD",
"description": "OKC METRO TRANSIT",
"check_number": null,
"status": "POSTED"
}
],
"next_cursor": "Y3Vyc29yOjIw"
}
3. FedNow / RTP credit webhook
POST https://your-treasury.example.com/hooks/qcb
X-OFL-Signature: t=1715430000,v1=<hmac-sha256>
Content-Type: application/json
{
"event": "rtp.credit.received",
"rail": "FEDNOW", // or "TCH_RTP"
"account_id": "acc_8021",
"amount": 4250.00,
"currency": "USD",
"iso20022": {
"msg_id": "M-2026-05-11-001",
"end_to_end_id": "INV-9921",
"instr_id": "FN-7720"
},
"received_at": "2026-05-11T09:00:12Z"
}
// Verify HMAC, ack with 2xx within 5s,
// otherwise we retry with exponential backoff.
4. Error model
409 Conflict
{
"error": "idempotency_replay",
"request_id": "req_5e2c",
"hint": "Same Idempotency-Key already accepted; safe to ignore."
}
401 Unauthorized
{
"error": "session_expired",
"request_id": "req_5e2c",
"hint": "Call POST /session/refresh with refresh_token."
}
Compliance & privacy
Quail Creek Bank Mobile is a US community-bank app, so the integration plays inside a specific regulatory frame. We document the consent and retention model under the Gramm-Leach-Bliley Act (GLBA) Safeguards Rule and align with FFIEC cybersecurity guidance for authentication and logging. Personal-financial-data reads follow the CFPB Personal Financial Data Rights rule (Section 1033), while real-time payments are encoded in ISO 20022 to match the FedNow Service messaging standard. ACH legs follow current NACHA Operating Rules.
Data flow / architecture
The pipeline is intentionally narrow: Quail Creek Bank Mobile session (Apiture Xpress) → OpenFinance Lab gateway → normalisation & consent ledger → your store + webhook fan-out. Each hop logs a request ID; PII is encrypted at rest with a customer-scoped key. The gateway holds only what is needed to keep the session alive — refresh tokens, not raw passwords — and exposes a kill switch so a user can revoke access at any time without a code change on your side.
Market positioning & user profile
Quail Creek Bank, N.A. is a single-state community bank in the Oklahoma City metro, serving local consumers and small-to-mid-sized businesses in personal banking, treasury services, and SBA-style commercial lending. The mobile app is Android + iOS only, distributed under Apiture's Xpress Mobile platform that powers many community banks and credit unions across the US. The integration audience is therefore practical: local businesses that want their Quail Creek Bank operating account to feed accounting, AP, treasury, or fraud systems — not a global B2C audience.
Screenshots
Visual reference of the live app surfaces our integration wraps. Click any thumbnail to enlarge.
Similar apps & integration landscape
Customers who connect Quail Creek Bank Mobile to their stack frequently hold accounts at one or more of the apps below. We treat them as part of the same ecosystem — a unified read across them is often the real goal.
- Arvest Bank — A regional bank with a heavy footprint across Oklahoma, Arkansas, and Missouri; its mobile app holds the same balance/transaction/Bill Pay shape, so customers often want a unified transaction export across Arvest and Quail Creek.
- Bank of Oklahoma (BOKF) Mobile — The mobile front-end of BOK Financial; its data includes treasury-management and commercial cash-management views that pair well with a multi-account dashboard alongside Quail Creek Bank.
- BancFirst Mobile Banking — Oklahoma's largest state-chartered bank app, with similar consumer/business banking surfaces; a common dual-bank integration target.
- Gateway First Bank — Jenks-headquartered bank app with mortgage-origination data on top of standard checking/savings; useful when a customer's payments and home-loan servicing live in different apps.
- First National Bank of Oklahoma — Community-bank app covering Oklahoma City, Ponca City, Tonkawa, and Tulsa; the customer profile and integration footprint overlap heavily with Quail Creek's.
- First Fidelity Bank — Operates Quail Creek branch locations and offers its own mobile banking app; a natural near-neighbour in the same Oklahoma City market.
- Chickasha Bank and Trust Co. — Another Oklahoma community bank with a mobile app that exposes balances, transfers, and Bill Pay; sits in the same integration class as Quail Creek Bank Mobile.
- Zelle — The P2P rail surfaced inside many US bank apps, including Quail Creek Bank Mobile; treating Zelle events as a unified data source across banks unlocks cleaner P2P reconciliation.
- Chime — A neobank app whose users frequently also keep a community-bank operating account; pairing a Chime read with Quail Creek Bank data gives a fuller personal-cash picture.
- Plaid Link integrations — Apps built on Plaid (budgeting, lending, payroll) routinely ask end users to connect Quail Creek Bank; an authorised gateway like ours is the more direct alternative for high-volume use cases.
What we deliver
Deliverables checklist
- OpenAPI 3.1 spec for every endpoint we expose (Accounts, Transactions, Bill Pay, RDC, Card Controls)
- Protocol & auth report covering the Apiture Xpress session lifecycle, MFA, and biometric handshake
- Runnable Python (FastAPI) or Node.js (Fastify) source — login, statement, Bill Pay, and webhook receivers
- Webhook signer/verifier samples for FedNow / RTP credit events
- Postman collection plus pytest / vitest integration tests against a recorded sandbox
- Compliance pack: GLBA, FFIEC, CFPB §1033, NACHA, ISO 20022 mapping notes
About us
OpenFinance Lab is an independent engineering studio focused on protocol analysis, OpenData read APIs, and authorised payment integrations for mobile banking and fintech apps. The team has shipped integrations across community-bank platforms, neobanks, and payment rails (FedNow, RTP, ACH, UPI, SEPA), and is comfortable working inside US, EU, and APAC compliance frames. We treat every engagement as a contract bound by what the end user has actually authorised — no scraping that violates terms, no resale of secrets, no shadow data flows.
- Source code delivery from $300 — runnable API source and full documentation; pay after delivery upon satisfaction.
- Pay-per-call API billing — access our hosted endpoints and pay only per call, no upfront fee; suitable for teams that prefer usage-based pricing.
Contact
For quotes, scoping calls, or to submit your target app and the exact data fields you need, open our contact page:
Engagement workflow
- Scope confirmation — name the surfaces (Accounts, Bill Pay, RDC, FedNow, etc.) and acceptance criteria.
- Protocol analysis & API design (2–5 business days against a sandbox or recorded session).
- Build & internal validation (3–8 business days, including idempotency and retry semantics).
- Docs, samples, OpenAPI spec, and tests (1–2 business days).
- First delivery typically lands in 5–15 business days; multi-bank or real-time webhook stacks may extend.
FAQ
Do you need direct access to Quail Creek Bank Mobile credentials?
Which Quail Creek Bank Mobile features can be exposed via API?
How long does a first delivery take?
How do you handle compliance for US community-bank integrations?
📱 Original app overview (appendix)
Quail Creek Bank Mobile is the official mobile-banking app of Quail Creek Bank, N.A., a community bank headquartered in Oklahoma City, Oklahoma. The Android build (com.apiture.xpressmobile.qcbocok.sub) runs on the Apiture Xpress Mobile platform — Apiture is a US digital-banking vendor founded in 2017 as a joint venture between First Data and Live Oak Bank, and in October 2025 became part of CSI. The mobile app is intended for existing Quail Creek Bank online-banking customers.
Available features per the app description and the bank's Digital Banking page:
- Accounts — Check your latest account balance and search recent transactions by date, amount, or check number.
- Transfers — Easily transfer cash between your accounts.
- Bill Pay — Make payments and view recent and scheduled payments.
- Manage Payees — Add new payees, manage existing payees, or delete payees directly from the mobile app.
- Deposits — Submit check deposits using your device's camera (mobile RDC).
- Biometrics — Secure sign-on using fingerprint or facial recognition.
- Zelle — Person-to-person payments using email or US mobile number, delivered to the recipient's account in minutes.
- SecurLOCK Equip — Card controls: turn the card on/off, set per-transaction alerts, and restrict by location or dollar amount.
- FedNow & RTP — Quail Creek Bank participates in the Federal Reserve's FedNow service and The Clearing House's RTP rail, enabling instant credits 24/7.
Quail Creek Bank Mobile is a sample app used here to illustrate API integration positioning. All trademarks belong to their respective owners.