MugglePay

• Name: MugglePay
• URL: https://www.mugglepay.com/
• Category: hosted merchant processor / multi-chain checkout and settlement routing / self-managed forwarding option
• Tags: bitcoin-ecosystem ethereum-ecosystem solana-ecosystem
• Summary: MugglePay is hosted checkout with a self-managed forwarding mode bolted on. Keep this note on the merchant-facing product surface: order creation, callbacks, settlement routing, and the practical difference between hosted settlement and self-managed forwarding across a long chain menu. The broader operator boundary around Merchant Portal access, API-token issuance, withdrawal workflow, support mediation, and lifecycle publication now lives in mugglepay.
• 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 useful surface is simple: create an order, hand off to hosted checkout, then trust callbacks for fulfillment.
  • POST https://api.mugglepay.com/v1/orders is the center of the integration, with callback, success, cancel, and merchant-validation fields doing most of the real work.
  • Callback handling matters more than the marketing numbers. MugglePay documents retries, validation tokens, and webhook-first backend automation because that is the operating surface merchants actually depend on.
  • The self-managed mode is real, but it is still MugglePay-shaped coordination around forwarding and settlement rather than a clean self-hosted merchant stack.
  • The long asset and chain menu broadens appeal, not strategic importance. This is still processor software with a lot of routing options attached.
• 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

• Company / operator boundary for Merchant Portal access, API-token issuance, withdrawal workflow, support mediation, and webhook-backed lifecycle truth: mugglepay.
• Best hosted-processor upward reads: coingate and opennode.

Protocol / company boundary

• Keep this note on the merchant-facing product layer: hosted order creation, checkout redirects, callback payloads, supported plugin paths, and the practical difference between the hosted settlement path and self-managed forwarding.
• Use mugglepay for the named-operator layer around Merchant Portal accounts, API-token issuance, rate-limit policy, support and account-manager workflow, withdrawal confirmation, and the broader live company shell merchants depend on when something breaks.
• That split matters because how does MugglePay checkout behave? and which company controls the account, credential, and lifecycle shell around that checkout? are related but not identical questions.

Control surface

• At the product layer, power sits in order creation, hosted checkout behavior, callback validation, supported-asset and chain exposure, and the terms of the self-managed forwarding mode.

• The broader operational dependency now points upward to mugglepay because Merchant Portal access, API-token issuance, withdrawals, support workflow, and payment-state publication are the company-shaped control surfaces merchants actually inherit.

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

• Last reviewed: 2026-08-10 UTC