Jack Mallers exits Twenty One as Strike steps away from Tether-backed merger

Twenty One Capital has named Raphael Zagury as chief executive after Jack Mallers left the company, while Strike is exiting the Tether-backed three-way bitcoin merger, according to The Block. For anyone building in crypto payments, the headline is less about personalities and more about operating model. Leadership changes at the top of a treasury-heavy or payments-adjacent business usually force a reset on governance, execution, and product focus.

That matters because crypto businesses do not just need a token strategy. They need dependable infrastructure for payment acceptance, settlement, conversion, and reporting. When a company spans bitcoin, stablecoins, and fiat rails, the operational questions quickly become more important than the branding. Who controls treasury policy? How are balances reconciled? Which assets are held, converted, or paid out? Which teams own the workflows between customer payments and downstream settlement?

The Twenty One update also reflects a broader pattern in digital asset companies. Mergers, restructurings, and executive changes often happen alongside a shift from narrative-led growth to infrastructure-led execution. That is especially true for businesses that want to serve merchants, platforms, and internet-native operators rather than only traders. Once the business model depends on recurring payment flows, payout schedules, and treasury movement, the platform has to behave more like financial operations software and less like a campaign around a single asset.

For merchants and platforms, the practical lesson is straightforward. If your business accepts crypto, pays contractors or creators, or moves funds across stablecoins and fiat, you need tools that keep those flows visible and controllable. A payments stack should support checkout, invoicing, subscriptions, links, and payouts without forcing finance teams to stitch together separate systems for every step. Radom is built around that operating need, with crypto payments, billing, invoices, payment links, payouts, and conversion workflows in one platform. See crypto payments for the core payment flow.

That kind of setup becomes more valuable when markets are noisy or leadership is changing. Businesses still have to collect funds, manage settlement preferences, and reconcile across currencies. If a team wants to accept crypto and settle in fiat, or hold part of receipts in digital assets while converting the rest, the workflow has to be clear enough for finance, operations, and engineering to trust it. The same is true for platforms that need to pay out globally to vendors, affiliates, or creators without creating manual work every time volume changes.

There is also a developer angle. When a company’s strategy shifts, product teams often need to move faster on integrations, webhooks, and payment logic. API-first payment infrastructure helps reduce the amount of custom work required when business rules change. That is one reason many operators prefer a single platform that can handle acceptance, settlement, and payout logic rather than a patchwork of point tools.

For readers watching this merger closely, the signal is not that crypto payments are slowing down. It is that the category is maturing. Businesses are being judged on operational discipline, not just asset exposure. The companies that last are usually the ones that can handle treasury, compliance, and payment operations with enough clarity to support real customers at scale.

If your team is building around crypto acceptance or payout workflows, the next step is usually to map the money movement first and the branding second. That includes where funds land, when they are converted, how they are settled, and who needs reporting access. Radom’s product set is designed for those flows, from acceptance to conversion to payout.

Learn more about Radom’s approach to crypto payments or speak with the team if your business needs a more tailored setup.