MugglePay

• Name: MugglePay
• URL: https://www.mugglepay.com/
• Category: hosted merchant processor / multi-chain checkout and settlement routing / optional self-managed forwarding
• Tags: bitcoin-ecosystem ethereum-ecosystem solana-ecosystem
• Summary: MugglePay is a managed merchant processor with a self-managed mode bolted on. The substance is order creation, hosted checkout, callback handling, and settlement routing across a lot of chains. Useful merchant plumbing, still mostly a processor rather than a distinctive payment rail.
• What it does:
  • Lets merchants create hosted crypto payment orders through a single order-creation API and redirect buyers to a MugglePay checkout page
  • Supports multi-chain stablecoin and crypto acceptance across networks like Arbitrum, Ethereum, Solana, TON, BNB Chain, Celo, and Base, with the official site also highlighting Bitcoin and Lightning support
  • Offers merchant operations through a portal for API keys, order history, callback testing, refunds, and transaction management
  • Exposes webhook-driven payment-status notifications so merchants can automate fulfillment, subscriptions, accounting, inventory updates, and other backend actions
  • Provides a self-managed non-custodial mode where merchants control the destination wallet while MugglePay still handles invoice and payment flow coordination
  • Ships plugins and prebuilt integration paths for ecommerce and billing platforms such as WooCommerce, Shopify, and WHMCS
• Key claims:
  • The homepage says MugglePay supports 20+ blockchains and tokens, has empowered 14K+ merchants, processed 2M+ transactions, reached 50+ countries, and offers 12+ plugins
  • The homepage also emphasizes direct non-custodial payout, stablecoin settlement, and payment from exchanges like Binance, Coinbase, and OKX without requiring a separate Web3 wallet setup
  • The docs overview says MugglePay is a pre-built payment page and checkout experience where merchants create an order, redirect the buyer to the payment page, and rely on payment callbacks for fulfillment
  • The Create Order docs say POST https://api.mugglepay.com/v1/orders is the primary API, describe it as the only API needed for core integration, and document callback_url, success_url, cancel_url, and merchant-defined validation tokens
  • The webhook docs say callbacks are the primary backend mechanism for order-state tracking, document token-based validation and exponential retries, and position webhook handling as the way to automate post-payment operations
  • The self-managed page says the non-custodial mode is globally available outside OFAC-sanctioned nations, gives merchants control of their crypto balance, and advertises 0% transaction fees for that mode
  • The merchant FAQ says self-managed invoices on EVM-compatible chains like Arbitrum, Base, and BNB Chain use non-custodial smart contracts to forward payments on the merchant’s behalf rather than simply reusing the merchant wallet address as the invoice destination
  • The merchant FAQ also explicitly distinguishes Web3-wallet registration for self-custodial mode from email registration for a simpler one-stop multi-token, multi-chain setup
  • The public GitHub repo README and repo metadata frame MugglePay as a crypto-native payment gateway for merchants and AI agents, while the repo README also highlights BTC, Lightning, ETH, USDT, BCH, LTC, and EOS support plus merchant API and plugin surfaces
• Whitepaper: No canonical standalone MugglePay whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site, docs portal, self-managed account docs, merchant FAQ, webhook docs, and public GitHub repo; see ../whitepapers/mugglepay-primary-sources-2026-05-05.md.
• Sources:
  • https://www.mugglepay.com/
  • https://docs.mugglepay.com/readme.md
  • https://docs.mugglepay.com/faq/overview.md
  • https://docs.mugglepay.com/order/createorder.md
  • https://docs.mugglepay.com/order/paymentcallback.md
  • https://docs.mugglepay.com/self-managed-non-custodian.md
  • https://docs.mugglepay.com/faq/merchantfaq.md
  • https://github.com/MugglePay/MugglePay

Internal linkages

• btcpay-server — stronger merchant-control anchor if the operator wants to own more of the stack
• opennode — cleaner hosted checkout and settlement comparison without the extra self-managed framing
• coinflow — stronger contrast once the interesting part is stablecoin business-payments operations rather than generic crypto checkout breadth

Control surface

• Power sits in merchant onboarding, order creation, hosted checkout behavior, callback validation, supported-asset and chain policy, and the terms of its self-managed forwarding mode.

• Read it as multi-chain processor software, not as a neutral settlement primitive.

• Last reviewed: 2026-06-01 UTC