Crypto payments just got a meaningful consolidation. Helio, the checkout and subscription platform used by 6,000+ businesses, has been acquired by MoonPay and rebranded as MoonPay Commerce. The product is live. The team has moved. And for engineering leaders building or evaluating crypto payment rails, this changes the calculus significantly. This is not a vanity acquisition. MoonPay is absorbing Helio's merchant-facing checkout and recurring billing engine into its existing on-ramp, KYC, and compliance infrastructure. The result is a vertically integrated crypto commerce stack that, for the first time, puts subscriptions, one-time checkout, and instant settlement under the same roof as fiat on-ramping at scale. That combination is rare in this space, and it matters.

MoonPay Commerce packages Helio's core capabilities, namely crypto checkout, subscription billing, and instant settlement with optional auto-conversion to fiat, on top of MoonPay's global infrastructure. MoonPay's partner ecosystem claims reach to 500M+ consumers and supports thousands of cryptocurrencies across all major blockchains. The practical effect: a SaaS product, creator platform, or marketplace that previously had to stitch together a wallet integration layer, a subscription billing adapter, a settlement provider, and a KYC/compliance wrapper can now, in theory, get that from a single vendor. What's new about this isn't any single feature. It's the integration of two previously separate layers. Helio handled the merchant side. MoonPay handled the consumer on-ramp side. Combined, MoonPay Commerce spans the full transaction lifecycle, from a consumer funding a crypto wallet to a merchant receiving settled payment, with recurring billing baked in.

The 500M+ reach figure and the 6,000+ merchant base are the numbers that will dominate coverage. They shouldn't be the numbers that dominate your analysis. The more important shift is structural. Subscriptions plus crypto checkout creates something the market has never had at scale: a path to recurring revenue on a historically volatile, settlement-unpredictable payment rail. Crypto as a payment method has always had bespoke-integration energy. Your engineering team builds custom webhook logic, monitors for chain congestion, hedges FX exposure separately, and prays the user's wallet is funded when the renewal fires. MoonPay Commerce is making a direct bet that it can abstract all of that away, that engineering teams should eventually be able to treat crypto as just another adapter in their billing system, not a special-case integration requiring its own monitoring runbook. If they deliver on that abstraction, the addressable market expands dramatically beyond crypto-native businesses into mainstream SaaS and commerce. That is a significant product thesis. It is also one that remains unproven at scale in 2026. But the architecture to test it now exists in a single product.

Most analysis will frame MoonPay Commerce as a crypto payments product competing with Coinbase Commerce, BitPay, and NOWPayments. That framing is too narrow. By absorbing Helio's subscription and checkout rails, MoonPay is quietly repositioning itself closer to Stripe and Adyen than to pure-play crypto gateways. The features that define a modern PSP, recurring billing, merchant dashboards, settlement abstraction, multi-currency support, are now part of MoonPay's stack. The differentiators MoonPay Commerce claims, no chargebacks, broader asset coverage, and lower fees versus card networks, are not arguments you make against BitPay. They are arguments you make against Stripe. This repositioning has strategic implications beyond product. Regulators treat on-ramp infrastructure providers very differently than they treat recurring billing platforms. MoonPay's regulatory surface area has just expanded. Consumer protection obligations, refund handling, and recurring billing disclosure requirements vary significantly by jurisdiction, and a company that previously focused on one-time on-ramp flows now operates subscription infrastructure. Engineering and compliance teams evaluating MoonPay Commerce should factor in that the regulatory picture around this product is still being written. Here is how MoonPay Commerce stacks up against the primary alternatives on the dimensions that matter to technical decision-makers:

The subscription row is where MoonPay Commerce wins outright among crypto-native providers. No other crypto-focused gateway at comparable scale ships recurring billing natively. That gap is why this acquisition is strategically sound.

If you are an engineering leader at a SaaS product, marketplace, or creator platform, here is a practical framework for evaluating MoonPay Commerce in 2026.

Your first question should be whether your current integration handles subscriptions or only one-time payments. Most custom crypto integrations do not handle subscriptions well because the tooling has not existed. MoonPay Commerce changes that. Evaluate whether consolidating to MoonPay Commerce reduces your maintenance surface and eliminates bespoke settlement monitoring logic. Specifically:

MoonPay Commerce is a more credible entry point than anything that existed before this consolidation. The combination of KYC, compliance, checkout, and subscription billing in one SDK lowers the integration cost substantially.

That said, do not treat "lower integration cost" as equivalent to "low business risk." Crypto demand varies dramatically by product category and geography. Before building, instrument a simple demand signal: a crypto payment option on your checkout page that captures intent but explains the capability is coming soon. Measure click-through rate for two to four weeks. If you see meaningful signal, prototype MoonPay Commerce in a low-risk market. If you do not, you have saved your team months of integration work.

The deeper question for technical decision-makers is whether crypto payment infrastructure is a core differentiator for your product or a commodity. For the vast majority of SaaS and marketplace businesses, it is commodity infrastructure. The same logic that pushed teams to Stripe instead of building card payment rails applies here. MoonPay Commerce is betting that crypto payment infrastructure should be bought, not built. For most teams, that bet is correct. The engineering cost of maintaining bespoke chain integrations, FX hedging, wallet monitoring, and compliance checks dwarfs the cost of a vendor relationship for all but the highest-volume, crypto-native platforms.

Intellectual honesty requires naming what is not yet known. Settlement behavior at scale is unproven under the combined product. Helio's 6,000 merchants are a meaningful sample, but MoonPay Commerce now operates under MoonPay's infrastructure. Any architectural changes in the migration could introduce latency or reliability regressions that only surface under load. The regulatory trajectory is genuinely uncertain. A recurring billing platform operating across jurisdictions faces a different compliance burden than a one-time on-ramp. How MoonPay Commerce handles refunds, disputes, and consumer protection obligations in regulated markets like the EU and UK will determine whether this product is viable for enterprise adoption or remains in the crypto-native segment. Finally, the fee structure relative to card networks is claimed but not independently verified at scale. The no-chargeback argument is real and structural, but the total cost of ownership comparison requires teams to model their specific transaction mix, average order values, and FX exposure before assuming crypto rails are cheaper.

MoonPay Commerce is the most serious attempt yet to make crypto payments boring in the best possible sense. Boring means: standard billing adapter, predictable settlement, no bespoke monitoring, vendor-managed compliance. The crypto payment tools that existed before this consolidation were not boring. They were interesting engineering projects that required interesting engineering effort to maintain. Whether MoonPay Commerce delivers on the boring promise will depend on execution over the next 12 to 18 months. But the architecture is now in place for engineering teams to stop treating crypto as a special case and start treating it as a first-class payment source. For engineering leaders building payment infrastructure in 2026, the practical move is to put MoonPay Commerce on your evaluation roadmap now, prototype it in a constrained scope by Q3, and make a build-versus-buy decision with real conversion data before end of year. The consolidation that makes that evaluation worthwhile just happened. The question is whether your team acts on it before your competitors do.