Frontend-led.
No financial backend to build.
You connect to MonCore at the frontend layer. Depending on your delivery model, you deploy a fully white-label app, adapt and embed the Shell, or use a custom frontend — with minimal-to-no financial backend infrastructure of your own.
Deploy white-label
Ship the fully white-labelled MonCore application under your brand and domain.
Adapt & embed the Shell
Compose and embed the MonCore Shell inside your product surface.
Custom frontend
Use a custom frontend created for your product, connecting to the same platform.
Your side stays thin. MonCore holds the operating layer.
The regulated financial backend is not something you assemble, host or maintain. Your product connects at the frontend, and MonCore governs everything below it.
On your side
- Frontend experience & brand
- Configuration & product presentation
- Session handoff into your app
Operated by MonCore
- Ledger, payments, cards, funding, FX
- Identity, compliance & reconciliation
- Regulated-rail connections & audit
The integration concepts that matter
MonCore is not another list of banking APIs to stitch together. Frontend integration is defined by a small, deliberate set of concepts.
Authentication & session handoff
Establishing a trusted session and passing it cleanly into your product surface.
Configuration
Branding, modules, journeys and product behaviour, expressed as configuration.
Events
Reacting to what happens inside the kernel through a governed event model.
Extension points
The defined places where your product shapes or extends the experience.
Environments
Sandbox and production designed to share one model — validate what you deploy.
Security boundaries
A clear separation between your frontend surface and the governed financial core.
You deploy your product. MonCore runs everything underneath.
Access to integration environments is currently private while issuer integration is underway.