A control plane,
not a “stack”.
One financial ledger, one workflow engine, one identity layer, one payments backbone — wrapped in operator tools, real-time monitoring and a journaled AI layer. Every transaction is reconciled. Every decision is logged. Every flow is auditable.
Each module ships with its own contract, its own metrics,
and its own incident runbook.
Core Banking & Ledger
Hierarchical accounts, customer subaccounts, double-entry postings, balance history, blocked amounts, currency & rates. Audit-grade by default.
Wallet & Mobile Backend
Transaction feed, balances, virtual cards, IBAN, SEPA, add-money, card-to-card, internal transfers, QR. Telco-aware identity.
Payment Orchestration
Provider gateways: card issuer, payment acquirer, ACH / Open Banking provider, custody, schemes, SEPA. One contract, swap providers without touching the ledger.
BPM & Workflows
Stateful process engine. Onboarding, KYC step-up, withdrawal approval, AML cases, card issuance, dispute handling.
KYC / KYT / AML
OCR, liveness, sanctions, PEP, KYT on crypto in/out via specialist provider. Tiered KYC, manual review, regulator evidence pack.
AI Orchestrator
Bounded-authority AI for ops: suggestions, not decisions. Human gates, replay, journaled actions, checkpointed state.
IAM & SSO
OAuth-based IAM. RBAC + ABAC, OAuth clients per tenant, role separation between Fin / BPM / Accounting / KYC / Treasury.
Observability & Audit
Replayable event log on AWS SQS/SNS. Decision journals, immutable audit trail, regulator evidence on demand.
Operator Workspace
One UI for payment ops, compliance, treasury. Cases, queues, journals, escalations. The cockpit your team actually opens.
One card auth, every hop, real timing.
Real production numbers from a Wave-1 Coreal deployment. Every hop is journaled with a reason code; the same trace is what an analyst sees when investigating any single transaction in the operator workspace.
Every named technology, with a reason.
No marketing names, no abstraction. The senior architect on the other side of the table needs to know what we run, what version, and why we picked it over the obvious alternative. Here it is.
Seven products, in production.
Each system below runs on the same control plane — same ledger, same BPM, same KYC perimeter, same operator surface. Each one with a live ledger, audit trail and incident history we can show under NDA.
Neobank Super Wallet
Consumer mobile wallet on a double-entry ledger. IBAN issuance, Visa card issuing, multi-chain custody, fiat/crypto switching, SEPA rails and full KYC/KYT.
Core Banking Platform
Multi-tenant banking infrastructure. Fincore backend, accounting, treasury, BPM workflows for money movement, sponsor-bank controls and on/off-ramp rails. White-label-ready.
Multi-Chain Trading Terminal
Unified crypto execution surface across Solana and EVM chains. Wallet import, limit orders, watchlists, copy trading, anti-MEV runtime guards and embedded payment cards.
AI Consensus Hedge Fund
Multi-exchange consensus with minimum-consensus order gate, ML scoring and anomaly detection. HWM performance fee, automated risk budget, trailing stops — investor-visible P&L with audit trail.
Neobroker
Multi-asset retail investment app with broker integration, bank linking, fractional shares, auto-invest, MiFID II best-execution reporting and regulated onboarding.
KYC / KYT Platform
Graph-based transaction monitoring with wallet risk scoring, real-time alerts, tiered verification, OCR + FaceID, ML + rule-engine AML, PEP/sanctions screening and SAR filing.
Roboadviser 4.0
Values-aligned advisory with SEC-registered flows, curated collections, broker integration, mean-variance and Black-Litterman allocation, suitability-gated positions and goal-based planning.
Your system, on the same rails.
Each of these started as a four-hour discovery brief. Map your perimeter — postings, providers, controls — and we'll show you what's already built and what's bespoke.
Book a working session →One incident.
One box.
Each licensed entity — primary telecom OpCo, regional telecom OpCo, EU EMI and a CASP perimeter — does not share tokens, secrets, environments or audit logs. Crypto risk cannot leak into telco wallet posture. Period.
What Coreal touches.
What it never touches.
A CTO signing off on this integration needs one thing to be true: Coreal has read access to the signals it needs, write access only to the ledger it owns, and zero access to BSS billing balances, OCS quotas or subscriber records outside of consent scope. That is the contract. Here is exactly what it looks like.
No BSS writes
Coreal never writes to the telecom BSS or OCS. Billing and subscriber record ownership stays with the operator. The integration is read + event, never mutate.
Consent-gated signals
SIM data, recharge velocity and device signals are accessed under explicit subscriber consent, scoped to the fintech product. Consent is revocable, logged and auditable.
One-day integration
The integration surface is designed to land in a single sprint. Standard OAuth OIDC for identity, webhook subscription for billing events, REST for ledger queries. No mainframe work required.
One of three models.
Zero BSS changes.
The single most common CTO question: “does this replace our billing system?” The answer is no — not for any of the three models. Mode 1 (billing-adjacent) is explicitly read-only on the operator stack. Modes 2 and 3 are fully separate legal and technical perimeters. Your billing runs as it always has.
Billing-adjacent
Coreal subscribes to the billing event bus. It reads charging triggers, recharge events and plan-tier changes — and responds by posting to its own ledger. The BSS/OCS is never touched on the write path. Integration lands in a single sprint.
Partner-led JV
A separate legal entity — operator-named — holds the financial product. Coreal contributes the regulated entity, ledger infrastructure and tech ops. The operator holds the majority stake and brand. Standard governance: operator CFO has board seat.
White-label EMI
Coreal issues wallets, IBANs and cards under its own EU EMI licence — branded end-to-end as the operator. No separate legal entity required. Fastest path to a compliant EU wallet product without licence acquisition.
Coreal subscribes to billing events. It does not post to them. No write path touches the BSS, OCS or subscriber record store. The integration can be reverted in a single config change — there is no schema migration, no stored procedure, no mainframe patch. If the operator wants to disconnect, they remove the event subscription. Coreal stops receiving data. The billing system is untouched.
What this platform ships.
Eight production fintech verticals run on the same control plane. The architecture above is not abstract — it shows up as these concrete products.
Onboarding + risk gates + MiFID II pre-trade log + execution routing + audit replay.
minctrl.com →Order management + execution routing + risk overlays + operator recovery.
minctrl.com →OCR + liveness + sanctions + ongoing monitoring. 38s median, 80%+ auto-approve.
minctrl.com →DID-based agentic KYC + stablecoin rails + EU AI Act compliance pack.
minctrl.com →IBAN + cards + crypto + SEPA + telco-aware risk.
minctrl.com →Read-only on Temenos T24 / Mambu / Profile. Wave-1 KYC, Wave-2 card-to-card.
minctrl.com →Wave-1 wallet + corridor + virtual card on partner-bank EMI passport.
minctrl.com →Sponsor-bank passport via Coreal EMI. Single MSA, multiple BINs.
minctrl.com →