Platform ›MonCore Shell ›White Label ›Custom Products ›Integration ›Developers ›Trust & Security ›Company ›Developer login ›Request early access
Documentation preview · developer access is private

Serious integration,
designed frontend-first.

This is a preview of how building on MonCore is designed to work. Public developer access and live documentation are not yet open — this page explains the concepts, not a live endpoint catalogue.

Platform architecture

A governed financial kernel with a thin, frontend-led integration surface — not an API marketplace.

Shell composition

How the MonCore Shell is composed from modules, and where your product extends it.

Auth & session handoff

Establishing a trusted session and passing it cleanly into your frontend.

Configuration

Branding, journeys and product behaviour expressed as configuration, not code assembly.

Events

A governed model for reacting to what happens inside the kernel.

Environments & boundaries

Sandbox/production parity and a clear separation between your surface and the core.

Illustrative — not a live interface

You configure a product. You don’t assemble a backend.

The shape below is illustrative of MonCore’s frontend-led model: describe the product experience and the platform operates the regulated layer beneath it. Package names, fields and endpoints are not published while access is private.

When you join the developer preview, you receive the real configuration model, environment details and integration guidance directly.

product.config · illustrative
// Conceptual — describes experience, not infrastructure
product = {
  brand:    { name: "Your Brand", theme: "custom" },
  model:    "shell",        // shell · white-label · custom
  modules:  ["wallets", "cards", "funding", "fx"],
  identity: { flow: "kyc", provider: "configurable" },
  session:  { handoff: "trusted" },
  events:   ["account.opened", "card.funded"]
};
// MonCore operates ledger, compliance, rails underneath.
Integration lifecycle

From access request to a controlled deployment

01

Request access

Tell us what you want to build. Developer access is granted as part of design-partner onboarding.

02

Scoping

We align on delivery model, modules and the shape of your product experience.

03

Sandbox environment

Work against a sandbox designed to mirror production — the same governed paths, without live rails.

04

Configure & compose

Brand, adapt the Shell or connect your custom frontend through defined extension points.

05

Validate against parity

Confirm behaviour in sandbox, knowing the same model runs in production.

06

Controlled production

Move to a controlled production deployment behind regulated rails, as part of onboarding.

Honest by design

No live endpoints, credentials or SDKs are published yet

We won’t pretend a public developer platform exists before it does. What you see here is the integration model we’re building. When the developer preview opens to you, the real details follow.

Request developer access →