Banking, payments, and open banking on Sentin8 - a core ledger with double-entry postings, ISO 20022 payment orchestration, and FDX v6.5 data exchange.
Every service this vertical ships, each owning its own data and API surface - click any card for its full dossier: use cases, architecture, business rules.
The core ledger: accounts, products, double-entry postings, balances, schedules, and the full configuration library - the system of record for money positions.
Payment orchestration: instructions, ISO 20022 scheme flows, cards, mandates, rules - money movement over every rail, never shadow-writing the ledger.
FDX v6.5 open banking: consent-checked data sharing between institutions, notifications, recipient registry - the consent authority for every provider call.
Regulatory reporting: jurisdiction registry, filing calendar, generation/packaging (XBRL/CSV), submission/amendment - the vertical's single filing executor.
Prudential risk: exposures, capital (Basel), liquidity (LCR/NSFR), IFRS 9 ECL, limit monitoring with breach events, stress scenarios.
AML/CTF: KYC/CDD, beneficial ownership, PEP, sanctions screening, transaction monitoring, alert/case lifecycle - detection only, filing via Reporting.
User- and staff-facing applications, thin by design - tokens never reach the client.
The retail customer app: account opening, balances, transfers, statements, notifications - and the customer side of FDX consent review and revocation.
Explore →The FDX recipient app: a fintech consuming consented bank data through the open-banking flows.
Explore →The staff terminal: teller operations, customer search, account servicing - behind the same Shield authorization as every app.
Explore →The staff dashboard: instance overview, product activation, FDX provider administration - RFW-rendered in Sentin8:Dash.
Explore →Typed facades over every service API - the only supported integration surface.
Bank8 inherits the Sentin8 security model by construction - every service runs behind the platform's authorization pipeline, tenant isolation, and post-quantum TLS.
Posting batches are balance-validated per denomination before any write; balances, transactions, postings, audit, and outbox commit atomically.
Every FDX provider call passes the consent middleware (valid, unexpired, scope-covered) plus CSDF data minimization - no exceptions.
Postings and payment instructions are idempotent per key; retries are safe by construction, terminal states never regress.
Compliance detects (KYC, screening, monitoring); Reporting is the single filing executor - separation of duty is structural.
Every table FORCE-RLS'd on env_id; customer-held records add holder scoping. The bank8 database is the vertical's own - the platform never queries it.
Bank8 contains no platform infrastructure of its own - identity, events, storage, scheduling, and supervision come from the platform services.
17 services: identity, events, storage, workflows, scheduling - everything bank8 doesn't rebuild.
Visit site →Delegates payments to Bank8:Payments for its property commerce.
Visit site →Delegates payments to Bank8:Payments for billing settlement.
Visit site →