Customisable blueprint
Codex NeoBank Suite
A customisable blueprint for a digital banking experience: onboarding, accounts, cards and an admin console, assembled around your licence and partners.
Overview
What this product is for
Codex NeoBank Suite is a blueprint, not a licensed bank. It is the architecture Codex Thrill uses when a team needs customer onboarding, account views, card status, transfers and an operations console, wired to the banking, KYC and card partners they have actually contracted. Screens, ledger boundaries and approval rules are adapted per engagement. Nothing here is a promise that Codex Thrill holds a banking licence.
FinTech founders and product teams who have, or are contracting, a sponsor bank, KYC vendor and card issuer, and need the customer and operations software around them.
At a glance
Capabilities
What is included
- Customer onboarding flow with a documented KYC handoff
- Account, balance and transaction views
- Card status and basic controls
- Transfer request flow with step-up checks
- Operations console for reviews, holds and support notes
- Audit log of who approved what
- Partner adapters kept at the edge, not inside the UI
Stack
Technology
Questions
Questions before a project conversation
Is Codex NeoBank Suite a bank?
No. It is software architecture and interface patterns. Banking activity stays with the licensed institution the client contracts.
Can the blueprint be changed?
Yes. That is the point. Onboarding steps, product types, limits and the operations console are adapted to the sponsor bank and the market.
Does it include a core banking ledger?
The blueprint defines the boundary. Whether balances live in a partner core or a ledger you operate is a decision made in discovery, not a default claim.