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.
Canadian open banking (FDX v6.x, consumer-driven banking): the provider and recipient surfaces over the shared kernel - consent-checked data sharing, money-movement initiation, notifications, certification metrics.
US open banking (FDX v6.x): the identical surface over the same kernel with US identity - independent version cadence, independent enablement.
UK open banking (OBL Read/Write API v3.1.x): the ASPSP adapter - FAPI 1 Advanced ceremony, intent-based consents, JWS signing, OB Directory trust. In design (OBARCH-5).
Typed facades over every service API - the only supported integration surface.
OpenFin8 inherits the Sentin8 security model by construction - the consent ledger, the recipient registry, and every jurisdiction adapter run behind the platform's authorization pipeline, tenant isolation, and post-quantum TLS.
Every provider route passes the consent middleware (valid, unexpired, scope-covered) on top of row-level security; revocation stops serving on the very next call - structurally, no bypass exists.
The provider's grant ledger and the recipient's consent registry live in separate tenants; no cross-tenant SQL ever. Either institution may run any technology - the only contract is standards-based OAuth.
Responses are projected to the granted CSDF clusters before serialization - narrowed by scope, product category, and requested fields. Unknown scopes grant nothing.
The entire implementation lives in openfin8-core, shared byte-for-byte. Each country adapter contributes its Profile and registration data - adding a market is configuration, not a port.
The FDX API specification is licensed and never committed; each adapter's published spec carries OpenFin8-owned routes only, enforced by a CI drift guard. Customers supply their licensed copy.
OpenFin8 contains no platform infrastructure of its own - identity, events, storage, workflows, and scheduling come from the platform services.