moonpay-commerce

MoonPay Commerce (formerly Helio)

• Name: MoonPay Commerce (formerly Helio)
• URL: https://www.hel.io/
• Category: hosted merchant checkout / deposit-address and subscription middleware
• Tags: ethereum-ecosystem solana-ecosystem bitcoin-ecosystem
• Summary: MoonPay Commerce is hosted checkout and reusable deposit-address plumbing inside MoonPay’s operator stack. The real surface is merchant-account issuance, deposit-customer state, signed webhooks, and subscription handling. Useful operator software, not a rail.
• What it does:
  • Lets merchants create pay links, one-off charges, and embedded checkout flows for crypto payments
  • Supports deposit flows that generate reusable customer-specific deposit addresses across SVM, EVM, and Bitcoin networks
  • Offers subscription billing with renewal reminders, grace periods, webhook events, and charge-based renewals
  • Exposes headless payment APIs for end-to-end no-UI payment flows, currently documented for Solana
  • Provides dashboard and API management for wallets, transactions, webhooks, merchant accounts, and selected partner/platform use cases
  • Bridges merchant checkout with MoonPay’s broader fiat onramp stack through optional “Add Money” deposit flows and KYB-gated ramp integrations
• Key claims:
  • The product splits cleanly into Pay Links and Deposits. That is more useful than the generic checkout copy.
  • The deposit flow is the real reason to keep the note: MoonPay Commerce creates reusable depositCustomers and associated deposit addresses across SVM, EVM, and Bitcoin networks.
  • Webhook handling is part of the product, not an afterthought. Retries, manual replay, bearer-token plus HMAC verification, and event logs make this a real merchant-ops surface.
  • Subscription tooling broadens the shell, but it still does not turn MoonPay Commerce into a payment rail.
  • The B2B platform-embedding angle matters mainly as operator distribution. It is still MoonPay-controlled merchant middleware.
• Whitepaper: No canonical MoonPay Commerce or Helio whitepaper/litepaper surfaced in this pass. The clearest current source of truth is the official homepage plus the docs corpus on docs.hel.io, especially llms.txt, developer, deposits, subscriptions, headless-payments, platform, and webhook pages; see ../whitepapers/moonpay-commerce-primary-sources-2026-05-01.md.
• Sources:
  • https://www.hel.io/
  • https://docs.hel.io/llms.txt
  • https://docs.hel.io/docs/introduction.md
  • https://docs.hel.io/docs/for-developers.md
  • https://docs.hel.io/docs/deposits.md
  • https://docs.hel.io/docs/subscriptions.md
  • https://docs.hel.io/docs/headless-payments.md
  • https://docs.hel.io/docs/webhooks.md
  • https://docs.hel.io/reference/platform/overview.md

Internal linkages

• Parent company boundary: moonpay.
• Best adjacent product reads: walletconnect-pay and coinflow.

Product / company boundary

• Keep this note on the merchant-product surface: pay links, embedded checkout, reusable depositCustomers, deposit-address lifecycle, subscriptions, webhook behavior, and the headless or platform-facing payment flows integrators directly wire into their product.
• Use moonpay for the named-operator layer around merchant admission, KYB-gated ramp enablement, payment-method and geography policy, dashboard and account authority, support workflow, and the broader company-run legal and settlement shell around Commerce.
• That split matters because how do MoonPay Commerce deposits, checkout flows, and webhooks behave? and which company decides who gets access, what rails stay enabled, and how the surrounding merchant workflow is governed? are related but not identical questions.

Control surface

• Practical authority at the product layer sits in merchant-account issuance, deposit-customer creation, deposit-address lifecycle, webhook truth, subscription state, supported chain and asset coverage, and the KYB-gated fiat-assisted paths MoonPay Commerce decides to expose.

• The broader operator dependency sits one layer up in moonpay: merchant admission, geography and payment-method policy, KYB-gated ramp enablement, dashboard authority, support workflow, and the wider company-run settlement shell.

• Read it as merchant checkout and deposit ops inside the broader MoonPay operator stack, not as a payment standard.

• Last reviewed: 2026-08-13 UTC