Jack Mallers exits Twenty One Capital as Tether merger plan collapses
A failed merger and a leadership change at Twenty One Capital underline how quickly bitcoin strategy can shift, even for firms built around the asset itself.

Jack Mallers has stepped down from Twenty One Capital as Tether’s plan to combine three bitcoin firms falls apart, according to Decrypt. The report said XXI stock dropped nearly 18% after the co-founder exited and the merger was officially abandoned.
For payment and treasury teams, the headline is less about one company’s boardroom change and more about how fast digital asset strategies can be reworked when capital, governance, and operating plans no longer align. In crypto, the same asset can sit inside payments, treasury, settlement, and speculation. Companies that use it for commerce need systems that can keep those functions separate.
That is why operators tend to value infrastructure that does more than hold coins. They need clear payment status, settlement choices, and a way to move funds between assets without rebuilding workflows every time the market changes. Radom’s crypto payments stack is built for businesses that want to accept digital assets through checkout, payment links, invoices, subscriptions, and APIs, then manage what happens next from one platform.
The Decrypt report also shows how closely crypto firms are still tied to market sentiment. A merger announcement, a leadership change, and a stock move can all land in the same trading session. For businesses that accept crypto from customers, the lesson is practical: the payment layer should be dependable even when the wider industry is not.
That means thinking about settlement and conversion as operational tools, not afterthoughts. Radom’s product set includes conversion workflows for businesses that need to move between supported digital assets and settle in the asset they want to hold. As the company puts it, "Move between cryptocurrencies and settle in the asset your business needs." Crypto Convert can be useful when a team wants to reduce manual treasury work or standardize how payments are handled after checkout.
For developers, the broader point is API design. When a platform changes direction, the teams integrating it still need stable payment logic, predictable webhooks, and a clean path from customer payment to reconciliation. That is especially true for SaaS, marketplaces, gaming platforms, and other businesses where payments are part of a larger operating system rather than a one-off transaction.
Radom’s pricing and product pages position the platform as one place for payments, billing, conversion, and settlement, with per-transaction pricing and no setup or monthly fees listed on the site. For teams evaluating crypto payment infrastructure, that combination matters because it keeps the commercial model tied to usage, not fixed overhead.
There is also a compliance angle. Leadership changes and failed deal structures are reminders that crypto businesses do not operate in a vacuum. Finance teams need payment rails that support reporting, reconciliation, and controls, especially when funds may move across crypto and fiat workflows. The right setup is not just about accepting payment. It is about knowing where the funds are, what asset they are in, and how they will be used next.
For businesses reviewing their own stack after a market event like this, the practical question is whether the payment layer can support both growth and volatility. If the answer is no, the next step is usually to simplify. That can mean consolidating checkout, billing, invoices, payouts, and conversion into one system, or at least ensuring the payment provider can support those flows without extra engineering overhead.
Readers looking at crypto acceptance or settlement workflows can review Radom’s crypto payments page for product details, or speak with sales if they need a setup for higher-volume payment operations.
Exploring how this affects your payment flow?
