MoonPay

• Name: MoonPay
• URL: https://www.moonpay.com/
• Category: crypto payments / fiat on-off-ramp / wallet and virtual-account infrastructure
• Tags: ethereum-ecosystem solana-ecosystem bitcoin-ecosystem
• Summary: MoonPay at the project layer is the ramp and signed-integration surface inside a larger MoonPay company shell. The useful product cut is the hosted buy/sell and wallet-ops stack around signed embeds, virtual accounts, and partner-gated money movement; the broader operator boundary now lives in moonpay.
• What it does:
  • Lets users buy and sell crypto using cards, bank transfers, Apple Pay, Google Pay, PayPal, Venmo, and other regional payment methods
  • Exposes developer integrations for embedded buy/sell widgets and SDK-based checkout experiences that require signed server-side request or URL flows
  • Offers Virtual Accounts APIs for programmatic auto-on-ramp and auto-off-ramp flows, with RSA-SHA256 request signing and transaction retrieval endpoints
  • Maintains public demo integrations and signing-server examples that clarify how the hosted ramp products are actually embedded into applications
  • Operates a public GitHub org and MoonPay Skills repo that frame the company increasingly as wallet, payments, swaps, deposits, and agentic money-movement infrastructure rather than only as a retail checkout widget
• Key claims:
  • The homepage presents MoonPay as “Your passport to crypto” and says users can buy, sell, and use crypto globally, with 35,000,000+ verified accounts across 180 countries
  • The developer docs describe MoonPay as payment infrastructure for crypto, but the analytically useful read is a hosted operator stack for checkout embeds, compliance packaging, and partner distribution rather than a new rail
  • The docs emphasize broad payment-method support, global coverage, security/compliance positioning, and straightforward API integration as core reasons developers should integrate MoonPay
  • The API reference shows MoonPay has moved beyond simple widgets into signed operational APIs such as Virtual Accounts, including authenticated retrieval of virtual-account details and transaction data for auto-on-ramp and auto-off-ramp flows
  • The demo-integrations repo shows the real integration posture plainly: MoonPay expects signed server-side or URL-level request handling rather than a loose frontend-only widget drop-in
  • The verified GitHub organization and MoonPay Skills repo show an expanding product surface around wallets, swaps, deposits, virtual accounts, x402 payments, and AI-agent integrations, but that breadth is still one operator stack rather than neutral infrastructure
• Whitepaper: No classic standalone whitepaper or litepaper was found during this pass. The strongest primary materials were MoonPay’s official site, developer docs, API reference, demo integration repos, and public GitHub organization; see ../whitepapers/moonpay-primary-sources-2026-04-26.md.
• Sources:
  • https://www.moonpay.com/
  • https://dev.moonpay.com/docs
  • https://dev.moonpay.com/reference/api-reference
  • https://github.com/moonpay
  • https://raw.githubusercontent.com/moonpay/moonpay-demo-integrations/master/README.md
  • https://raw.githubusercontent.com/moonpay/skills/main/README.md

Internal linkages

• Company boundary for the broader operator shell: moonpay.
• Merchant-facing branch under the same company surface: moonpay-commerce.
• Closest embedded-ramp peer once the question is signed checkout, coverage, and compliance packaging: transak.

Protocol / company boundary

• Keep this note on the product shell: hosted buy/sell flow shape, widget and SDK integration, signed request handling, virtual-account APIs, and the wallet / checkout surfaces downstream apps directly embed.
• Use moonpay for the named-operator layer around merchant and partner admission, signed-integration approval, geography and payment-method policy, compliance workflow, payout and settlement packaging, and the wider company-run legal and support perimeter.
• That split matters because how do MoonPay integrations and product objects behave? and which company controls access, compliance, payout wiring, and production trust assumptions? are related but not identical questions.

Control surface

• At the product layer, authority sits in signed embed and request policy, virtual-account lifecycle, partner-gated ramp access, and which wallet or checkout flows MoonPay exposes behind its SDKs and hosted surfaces.

• For the wider settlement, compliance, and multi-product operator boundary, read moonpay.

• Last reviewed: 2026-08-10 UTC