MoonPay

• Name: MoonPay
• URL: https://www.moonpay.com/business
• Category: payments and stablecoin platform / fiat on-off-ramp / merchant checkout / wallet and treasury middleware company
• Tags: ethereum-ecosystem solana-ecosystem bitcoin-ecosystem
• Summary: MoonPay belongs as an entity note, not just a product note. The useful cut is that one named company operates a broad money-movement stack spanning ramps, merchant checkout, trade routing, stablecoin payout and treasury packaging, virtual-account flows, and the compliance shell around them. The practical leverage is not only buy crypto; it is who decides partner admission, KYC/KYB and fraud workflow, geography and payment-method coverage, settlement options, webhook and API truth, and which conversion or payout paths downstream apps inherit by default.
• What it does:
  • Operates MoonPay Ramps for buy, sell, and withdrawal flows through hosted widgets and headless or SDK-based integrations
  • Runs MoonPay Commerce, the former Helio merchant product, for pay links, deposits, reusable customer deposit addresses, subscriptions, headless checkout flows, and webhook-driven merchant operations
  • Markets MoonPay Trade as a routing and execution layer for crosschain trading and swap-like order flow exposed through APIs and contracts
  • Packages stablecoin-oriented business flows including cross-border payouts, treasury movement, fiat-in and fiat-out conversion, and white-label stablecoin issuance claims inside the same business shell
  • Exposes signed API surfaces such as virtual accounts, partner integrations, and business-facing payment workflows where MoonPay controls authentication requirements, compliance gating, supported geographies, and settlement policy
  • Sells one-company integration breadth to wallets, exchanges, marketplaces, gaming apps, fintechs, payroll platforms, and payment-service providers, which makes the company boundary analytically stronger than any single product page
• Key claims:
  • The business site frames MoonPay as a unified payments platform that connects traditional money and crypto through a single integration so customers can buy, sell, send, trade, and pay without leaving the integrating product
  • The same business materials advertise 10B+ volume, 35M+ verified accounts, 500+ ecosystem partners, 180+ countries, and 170+ payment methods; those are useful vendor scale signals rather than independently verified measurements
  • The MoonPay docs still describe the company as payment infrastructure for cryptocurrencies and emphasize broad payment-method support, global coverage, compliance posture, and easy integration for Web3 developers
  • The business page now groups the stack into Ramps, Commerce, Trade, and Stablecoins, which is exactly why the entity note matters: several different operator surfaces sit under one company-run policy and settlement shell
  • MoonPay says it handles conversion, identity checks, fraud, and settlement behind the scenes for ramps, while Commerce materials show reusable merchant objects, signed webhooks, and optional ramp handoff inside the same broader stack
  • The API reference’s virtual-accounts surface and signed-request requirements remain good evidence that MoonPay is operating a real payment and settlement control plane rather than a loose frontend widget vendor
• Whitepaper: No classic standalone company whitepaper is the point here. The clearest primary materials are MoonPay’s business site, consumer homepage, developer docs, API reference, and the earlier primary-source captures for MoonPay and MoonPay Commerce in ../whitepapers/.
• Sources:
  • https://www.moonpay.com/business
  • https://www.moonpay.com/
  • https://dev.moonpay.com/docs
  • https://dev.moonpay.com/reference/api-reference
  • https://docs.hel.io/llms.txt
  • https://docs.hel.io/docs/deposits.md
  • https://docs.hel.io/docs/webhooks.md
  • https://github.com/moonpay

Internal linkages

• Project-layer product notes: moonpay for the ramp and signed-integration surface, and moonpay-commerce for the merchant checkout and deposit-address branch.
• Useful adjacent company reads: bvnk, crossmint, and lightspark.
• Cleaner contrast where the note should stay at product or network layer rather than company shell: walletconnect-pay.

Protocol / company boundary

• There is no especially useful standalone MoonPay protocol doing the analytical work here.
• The important surface is the company-run operating shell that packages ramps, merchant checkout, conversion, payouts, settlement options, compliance workflow, and partner distribution behind one commercial API and dashboard boundary.
• That is why MoonPay belongs in companies/: the practical questions are about who can admit partners, gate geographies, define KYC/KYB and fraud flow, choose routing and settlement defaults, and package several money-movement products into one inherited dependency.

Control surface

• Practical leverage sits in partner onboarding, identity and compliance gating, payment-method and jurisdiction coverage, conversion and payout routing, merchant-account issuance, virtual-account lifecycle, webhook and transaction-state truth, and which product branches MoonPay chooses to expose or bundle together.

• The sticky dependency is operational memory: once a wallet, merchant, exchange, or fintech hardens around MoonPay-managed KYC, settlement, virtual accounts, subscriptions, deposit addresses, and payout workflows, the dependency is on the company-run workflow graph more than on any one API endpoint.

• Treat MoonPay as a company-operated money-movement control plane first. The consumer brand is distribution; the real authority sits in the integration, compliance, and settlement shell behind it.

• Last reviewed: 2026-08-06 UTC