Cowrie Research

mugglepay-primary-sources-2026-05-05

4 min read

MugglePay primary sources — 2026-05-05

Project status in this pass

  • No canonical standalone MugglePay whitepaper or litepaper surfaced.
  • The clearest current sources of truth were the official site, the official docs portal, the self-managed account page, the merchant FAQ, the webhook docs, and the public GitHub repo.
  • The combination of hosted checkout flows, portal operations, and self-managed wallet routing makes MugglePay look broader than a simple crypto pay button.

Primary-source snapshots

1) Main site overview

  • URL: https://www.mugglepay.com/
  • Key excerpt:
    • The homepage says MugglePay supports 20+ blockchains and tokens, 14K+ merchants, 2M+ transactions, 50+ countries, and 12+ plugins.
    • It also says merchants can get paid directly in a non-custodial way, avoid price volatility through stablecoin settlement, and accept payments from exchanges like Binance, Coinbase, and OKX.
    • This page is the clearest top-level signal that MugglePay is trying to be an operational merchant acceptance layer rather than only a plugin.

2) Docs portal readme and API overview

  • URL: https://docs.mugglepay.com/readme.md
  • URL: https://docs.mugglepay.com/faq/overview.md
  • Key excerpt:
    • The docs readme describes MugglePay as a comprehensive cryptocurrency payment solution and points merchants to the Merchant Portal for API keys and order management.
    • The API overview says the core flow is create order → redirect to payment page → handle payment callback.
    • It explicitly frames MugglePay as a pre-built checkout experience that evolves behind a single merchant integration.

3) Create Order API

  • URL: https://docs.mugglepay.com/order/createorder.md
  • Key excerpt:
    • The Create Order docs say POST https://api.mugglepay.com/v1/orders is the primary API and even call it the only API needed for core payment integration.
    • The page documents hosted payment_url generation, merchant-defined order identifiers, webhook callback URLs, redirect URLs, and per-order validation tokens.
    • It also exposes a network-and-token matrix spanning Arbitrum, Ethereum, Solana, TON, BNB Chain, Celo, and Base, which supports the multi-chain control-plane reading.

4) Payment Callback docs

  • URL: https://docs.mugglepay.com/order/paymentcallback.md
  • Key excerpt:
    • The callback docs say webhooks are the primary backend mechanism for tracking order status and automating fulfillment.
    • They document payload fields, token-based validation using the merchant-provided token, and exponential retries that can continue for up to three days.
    • This matters because it shows MugglePay is not just rendering invoices; it is also packaging the merchant-side eventing and operational workflow.

5) Self-managed non-custodial mode

  • URL: https://docs.mugglepay.com/self-managed-non-custodian.md
  • Key excerpt:
    • The self-managed page says merchants hold the private key, have full control over their crypto balance, and pay 0% transaction fees in this mode.
    • It says the mode is globally available except in OFAC-sanctioned nations and currently supports major stablecoins on Ethereum, Arbitrum, BNB Chain, and Celo.
    • This page is the clearest evidence that MugglePay offers a distinct non-custodial merchant mode rather than only a hosted custodial gateway.

6) Merchant FAQ and operational nuance

  • URL: https://docs.mugglepay.com/faq/merchantfaq.md
  • Key excerpt:
    • The merchant FAQ explains that in self-managed mode on EVM-compatible chains like Arbitrum, Base, and BNB Chain, MugglePay uses non-custodial smart contracts to receive and forward payments rather than simply assigning the merchant’s wallet address as the invoice address.
    • It also explicitly distinguishes Web3-wallet registration for self-custodial mode from email registration for a simpler multi-token, multi-chain merchant setup.
    • That distinction is useful because it shows MugglePay is packaging two different operational models inside one merchant stack.

7) Public GitHub repo

  • URL: https://github.com/MugglePay/MugglePay
  • Key excerpt:
    • The public repo README presents MugglePay as a crypto-native payment gateway, highlights support for BTC, Lightning, ETH, USDT, BCH, LTC, and EOS, and links out to merchant APIs plus Shopify and WHMCS integration paths.
    • Current GitHub metadata shows an actively maintained public repo (MugglePay/MugglePay) with the description “MugglePay makes merchants and AI agents accept crypto and sell more with it.”
    • The repo is not the whole product, but it reinforces the view that MugglePay is a real integration surface rather than a marketing-only checkout page.

Working conclusion

MugglePay is best cataloged as a crypto merchant-payments control plane. The deciding evidence in this pass was the combination of hosted checkout orchestration, portal-based merchant operations, webhook-first backend state handling, documented multi-chain settlement options, plugin surfaces, and a distinct self-managed non-custodial mode that still relies on MugglePay’s invoice and routing layer. That mix makes the product look materially broader than a simple crypto checkout widget or one-off ecommerce plugin.

Graph View