Table of contents

Fintech

Guide

Launching a stablecoin or crypto product on a new core? What Mambu, Thought Machine, 10x, Tuum and Temenos provide

Guillaume Rigal

0 min read

Launching a stablecoin or crypto product often means choosing a new core banking system. Here is what Mambu, Thought Machine, 10x, Tuum and Temenos give you to ship it, which of it is live today, and how the rest of the stack fits around the core.

Banks and fintechs rarely replace a core banking system (CBS) for its own sake. The question comes up when they want to launch something the current core was never built for, and in 2026 the clearest example is a stablecoin or crypto product: a new currency type on the ledger, fiat accounts next to wallets, and settlement that runs every day of the week.

The public record shows how new products usually reach the market. The new product gets a new core, and the new core runs next to the existing one. ABN AMRO took its youth bank BUUT to market on Mambu in twelve months. Intesa Sanpaolo launched Isybank on Thought Machine about sixteen months after signing. Questrade took Questbank live on Temenos SaaS in May 2026.

The pattern behind those launches is composability, and a crypto product takes it further than most. The core runs the fiat accounts, the ledger and the product rules. A custody provider holds the keys and signs on-chain. Blockchain analytics screens wallets, a travel rule provider carries the transfer data, and a KYC provider verifies customers. An operations layer joins all of them for the team that runs the product every day. Forest is that operations layer, and the last part of this guide shows how it sits next to each of these core banking systems.

This guide compares what five core banking systems give you to ship a stablecoin or crypto product: Mambu, Thought Machine, 10x Banking, Tuum and Temenos. For each capability it separates what customers run in production, what has been announced, and what so far appears only in marketing material.

Why fintechs choose a new core banking system to launch a crypto product

A crypto product asks things of the core that most cores were never designed for:

  • a currency type that is neither euro nor dollar, with its own rules;

  • fiat accounts and digital asset balances that customers see side by side;

  • postings and events in real time, every day of the week;

  • a clean mapping between internal accounts and external wallets.

Changing the main core to get them puts every existing customer at risk. Launching the crypto product on a second core puts only the new product at risk.

This is composability applied to the core itself, and the vendors sell exactly that route. Mambu calls it a dual-core strategy. Temenos launched composable deposit and lending modules in May 2026, designed to sit inside a bank's existing technology landscape. Tuum runs in parallel with Bank CenterCredit's legacy core to power a new offering.

So the useful question for a buyer is which core gets the crypto product live, and what it gives you for that specific project.

Mambu, Thought Machine, 10x, Tuum and Temenos compared for a stablecoin or crypto launch

In the rows on new brands, digital assets, custody and crypto clients, each cell opens with a status in bold:

  • Live: a named customer runs it in production.

  • Announced: launched or in limited release, with no named deployment.

  • Claimed: described on product pages, blogs or whitepapers only.

  • Not documented: nothing public found.


Mambu

Thought Machine

10x Banking

Tuum

Temenos

Deployment

SaaS only, shared or dedicated environment, on AWS, Google Cloud or Azure

Your own cloud, on premises, hybrid, or SaaS

Managed SaaS on AWS

SaaS, cloud-agnostic

On premises, private cloud, public cloud, or SaaS on Azure and AWS

How new products are defined

Configuration through the interface or as code

Smart contracts written in Python

Software development kit and APIs

No-code builder, low-code extensions

Product factory and product builder API

New brand on a second core

Live. ABN AMRO's BUUT, twelve months to market

Live. Intesa Sanpaolo's Isybank

Live. Chase UK; Old Mutual's OM Bank in South Africa

Live in parallel at Bank CenterCredit. maib's Romanian digital bank selected in 2025

Live. Questrade's Questbank, May 2026

Digital assets in the core

Not documented. Multi-currency accounts only

Claimed. Fiat and digital money on one platform, internal accounts mapped to external wallets

Not documented

Claimed. Stablecoins and tokenised deposits as native currency types, with KYC and AML rules per asset

Not documented in the core itself. Handled through the Taurus integration

Custody and wallet integration

Not documented

Claimed. Integrations with wallet and stablecoin-issuance providers, unnamed

Not documented

Not documented. No native blockchain integration

Live integration with Taurus for custody, settlement and wallet creation, since 2021. Fireblocks listed as a solution provider

Crypto businesses served

Not documented

Not documented

Not documented

Live. Januar, accounts and payments for crypto businesses

Not documented

Best fit for a crypto launch

The fiat side of a crypto product, accounts and lending, live within a year with nothing to host, with custody handled by a specialist

A product where your engineers define fiat and digital money in one ledger, in code, on your own infrastructure if needed

The fiat side of a large retail launch that needs every ledger event streamed to your own systems

A modular launch where stablecoin balances sit in the ledger as a currency type, next to a core you keep

A launch that wants custody already integrated, with broad functional coverage around it

One pattern runs down the digital asset rows: none of the five CBS providers names a customer running a stablecoin product on its core yet. The live pieces sit around the core, in custody integrations and in accounts for crypto businesses.

How long it takes to launch a new digital bank or fintech brand on each core

Launching a new brand on a second core is the one use case all five CBS providers have proven with named customers, and it is the route a crypto product takes.

  • Mambu. ABN AMRO's BUUT reached the market in twelve months. Leeds Building Society launched digital savings on Mambu during its own core modernisation (FinTech Futures).

  • Thought Machine. Intesa Sanpaolo signed in February 2022 and launched Isybank in June 2023, with part of its retail customer base moving over in stages.

  • 10x Banking. Chase UK launched as a new bank free of legacy infrastructure. Old Mutual built OM Bank as a new regulated entity and opened it to the public in September 2025 (Moonstone).

  • Tuum. Bank CenterCredit runs Tuum in parallel with its existing core, hosted inside its own data centre. maib selected Tuum in June 2025 for a greenfield digital bank in Romania.

  • Temenos. Questrade took Questbank live on Temenos SaaS in May 2026.

Fintechs follow the same pattern at their own scale. Defacto runs B2B lending on Mambu, Lunar runs on Thought Machine, Multitude Bank has run on Tuum since 2020, and Moneycorp chose Temenos SaaS for core banking and payments in 2025.

Twelve to sixteen months from signature to launch is the documented range for a new brand on the core. That timeline covers the ledger and the products. Getting the operations around the new product ready is a separate project, covered further down.

What each CBS provider gives you to launch a stablecoin or crypto product

Many fintechs want to launch a stablecoin or crypto product, and few cores have shipped the capability yet, so check each status before you plan around it.

Temenos has the longest-standing piece: Taurus, a digital asset infrastructure provider, joined its marketplace in 2021, and the core links to Taurus for custody, settlement and wallet creation. Fireblocks is also listed as a Temenos solution provider, without integration details.

Thought Machine describes fiat and digital money on one platform, with internal accounts mapped to external wallets and integrations with wallet and stablecoin-issuance providers, published as a product page and a whitepaper without named customers.

Tuum states that its platform supports stablecoins and tokenised deposits as native currency types, configured per asset with their own KYC and AML rules. Tuum is not built on a blockchain, so custody and on-chain settlement come from a partner. It already serves crypto businesses on the fiat side: Januar runs accounts and payments for crypto companies on Tuum.

Mambu and 10x document no digital asset capability. Both remain options for the fiat side of a crypto product, with digital assets handled entirely by specialists.

The composable stack for a crypto launch: which provider does what

A stablecoin or crypto product runs on six components, and the core is only one of them.

  • Core banking system. Fiat accounts, the ledger, product rules and, where the core supports it, stablecoin balances as a currency type.

  • Custody and wallet provider. Key management, wallets, transaction signing and on-chain settlement. Taurus and Fireblocks are examples.

  • Blockchain analytics. Screening of wallets and on-chain transactions before funds move. Chainalysis and TRM Labs are examples.

  • Travel rule provider. Originator and beneficiary data attached to every crypto transfer, required in the EU under the Transfer of Funds Regulation since 30 December 2024.

  • KYC and KYB provider. Customer verification, often with rules that differ by asset.

  • Operations layer. The case your team works across all of the above, with the actions, approvals and audit trail that tie them together.

In the EU, MiCA's transitional period for crypto-asset service providers ended on 1 July 2026, so the controls this stack carries are licensing conditions from the first transaction.

The fintech backoffice a crypto product needs on launch day

Every core banking system above gives your engineers a ledger, a product engine and an API. None of these core banking systems gives the crypto product's operations team what it needs on its first morning.

A crypto product goes live with work already waiting for that team:

  • wallet screening alerts to review before funds move;

  • transfers held because travel rule data is missing or incomplete;

  • onboarding cases blocked until a KYC or KYB result comes back;

  • withdrawals above a threshold waiting for approval before the custodian signs;

  • customer questions on a Saturday, because stablecoins settle every day of the week.

The tooling the vendors ship covers the core's own records: Mambu's single interface for account servicing and daily operations, Temenos Explorer for branch and middle-office staff, Tuum's back-office interface, Thought Machine's separate servicing and orchestration products, and 10x's bank manager interface. Tooling also changes over a product's life: Mambu has announced that its process orchestration product, Mambu Process Orchestrator, will be fully decommissioned, without a published date.

That is the trade-off of a composable stack. Each component does its own job well, and the case your operations team works spans all of them: the core, the custody provider, the analytics tool, the travel rule provider, the KYC provider and your own database. DORA adds that every ICT service supporting a critical function sits in your register of information with an exit plan, so the layer your operations run on is part of that picture too.

We covered how to design that layer in How to build a compliant fintech backoffice in 2026: a unified data layer, workflow orchestration, role-based access with separation of duties, and an audit trail on every action. That guide was written for exactly this moment, a team standing up the operations for a new product. Use it alongside your core shortlist.

How Forest runs a crypto product's operations next to Mambu, Thought Machine, 10x, Tuum or Temenos

Forest is the operations layer of a composable stack, the part teams put next to the core when they launch.

  • One case across systems. Forest connects to your core as a datasource, and to your custody provider, analytics tool, travel rule provider, KYC provider and own database the same way. Your team works one case with every record attached.

  • Actions your team runs from the record. Approve a withdrawal, request missing travel rule data, freeze an account. Your developers write each one once; your operators run it without a ticket to engineering.

  • Approval before the custodian signs. Four-eyes approval on withdrawals above your threshold happens in Forest. Signing stays with the custodian, and the regulated ledger stays with the core.

  • Permissions and a full audit trail. Record-level access by role, and a record of who did what, on which record, with which inputs.

  • Internal AI agents under the same rules. Forest exposes your operations as an MCP server. An agent that triages screening alerts or chases missing travel rule data connects with a scoped role, acts only within that scope, exactly like a person on your team, and stops at the same approval steps.

This complements your core banking system and your custody provider. The core keeps the ledger, the custodian keeps the keys, and Forest keeps the case, the decision and the proof across both.

It runs on your own infrastructure, reading through your credentials, and it connects to both cores while the old and the new run side by side. Our engineers build the first workspace with your team, on the core you chose.

Common questions about choosing a core banking system for a crypto product

Can I launch a crypto or stablecoin product on Mambu, Thought Machine, 10x, Tuum or Temenos?

Yes, by composing it. The core keeps the fiat accounts and the ledger, and a digital asset specialist runs custody and wallets. Temenos has offered that model with Taurus since 2021, Thought Machine describes integrations with wallet and stablecoin-issuance providers, and Tuum lets you define a stablecoin as a currency type with its own KYC rules. What sets your launch date is the operation around it: wallet screening, travel rule data and a queue that runs on weekends. Design that layer in the same month you choose the core.

Do I need a crypto-native core banking system?

For most fintechs, no. Custody, signing and on-chain settlement belong with a specialist custody provider. What you need from the core is a clean fiat ledger, real-time events and, ideally, a way to represent the new asset next to fiat balances. Choose the core for the fiat side and the launch timeline, and the custody provider for the crypto side.

Which core banking systems integrate with crypto custody providers?

On the public record, Temenos, through its Taurus integration live since 2021, with Fireblocks also listed as a solution provider. Thought Machine describes integrations with wallet and stablecoin-issuance providers without naming them. Mambu, 10x and Tuum document no custody integration, so custody connects through your own stack.

How long does it take to launch a new bank brand on a new core?

Twelve to sixteen months for the core on the fastest documented launches: BUUT on Mambu in twelve, Isybank on Thought Machine in about sixteen. Building a full bank from scratch, as Chase UK did on 10x, takes longer. The first customer arrives on launch day with an onboarding case, a screening alert and a withdrawal to approve, so build the operations layer at the same time as the core.

What does a crypto product need beyond the core?

An operations layer you own. A crypto stack keeps changing: you add a custody provider, replace an analytics tool, open a market, and one day you may move the core itself. Case management, actions, approvals before signing, the audit trail and the rules your internal agents follow should stay put through those changes. Our backoffice guide sets out how to build it.

Get your crypto product's operations ready for launch day

Your core shortlist decides how fast the ledger is ready. The operations decide whether the product can take its first customer. If you are scoping a stablecoin or crypto product on Mambu, Thought Machine, 10x, Tuum or Temenos, book a demo and one of our engineers will map your launch-day operations to a Forest workspace.

Forest is the operational layer for regulated fintechs. Connect your core banking, payment and compliance providers as datasources, build the actions and workflows your team runs every day, and keep permissions and a full audit trail on every call. Runs on your own infrastructure.

LEVEL UP YOUR OPS GAME

Every action traced, for every human, AI agent, BPO, LLM, and workflow.

LEVEL UP YOUR OPS GAME

Every action traced, for every human, AI agent, BPO, LLM, and workflow.

LEVEL UP YOUR OPS GAME

Every action traced, for every human, AI agent, BPO, LLM, and workflow.

The operational infrastructure regulated companies grow on

Copyright ยฉ 2026 Forest

Design by Alasta & Built by Reiya Studio