Mural Pay

• Name: Mural Pay
• URL: https://muralpay.com/
• Category: Stablecoin payments / global accounts / treasury infrastructure
• Summary: Mural Pay is cross-border money-movement infrastructure with stablecoins in the stack, not a protocol worth romanticizing. The useful cut is operational: accounts, custody mode, payins, payouts, FX, approvals, and compliance workflow for platforms that want one API surface for treasury and settlement ops.
• What it does:
  • Provides API-driven account infrastructure for receiving, holding, converting, and moving money across fiat rails and stablecoin networks
  • Offers dedicated accounts, wallet flows, payins/onramps, payouts/offramps, counterparty management, webhook events, and transaction-status tooling for developer teams
  • Supports multiple custody models, including Mural custody, developer custody, and end-user custody paths documented in its API materials
  • Exposes operational/compliance surfaces such as KYB/KYC reviews, attestation upload flows, IP allowlisting, idempotency, validation rules, payout-fee tables, delivery-time references, and webhook signature validation
  • Publishes AI-facing integration materials including llms.txt, an OpenAPI spec, and a remote MCP server for AI-assisted development against the Mural API
• Key claims:
  • Homepage and developer pages position Mural Pay as infrastructure for launching global accounts, wallets, payments, and treasury workflows with real-time settlement and built-in compliance
  • API overview says Mural helps platforms, fintechs, and financial institutions create accounts that can receive, hold, convert, and move money in fiat or stablecoins across borders and payment networks
  • Public docs and llms.txt reveal unusually broad operational scope: compliance reviews, custody models, payins, payouts, developer fees, event/webhook systems, sandboxing, and extensive account/counterparty APIs
  • Knowledge-base materials show Mural documenting concrete approval and security workflows such as passkey-based approver migration and detailed business/beneficial-owner verification requirements
  • Public fee and delivery documentation makes Mural legible as an execution rail, showing supported countries, payout timing, cut-off windows, FX fees, local rails, and how stablecoin transactions differ from bank transfers
• Whitepaper: No classic whitepaper or litepaper was found during this pass. The strongest primary materials were the homepage, developer landing page, API overview, AI/MCP documentation, llms.txt documentation index, knowledge-base compliance articles, fee/delivery documentation, and public GitHub repositories; see ../whitepapers/mural-pay-primary-sources-2026-04-25.md.
• Sources:
  • https://muralpay.com/
  • https://muralpay.com/developers
  • https://muralpay.com/about
  • https://developers.muralpay.com/docs/getting-started
  • https://developers.muralpay.com/docs/ai-developer-resources
  • https://developers.muralpay.com/docs/mcp
  • https://developers.muralpay.com/llms.txt
  • https://docs.muralpay.com/articles/9213189885-wallet-to-passkey-migration
  • https://docs.muralpay.com/articles/2962171586-business-identity-verification
  • https://docs.muralpay.com/articles/1779974491-understanding-fees-transaction-processing-times-and-cut-off-times
  • https://github.com/muralpay

Internal linkages

• Best reads: bridge-xyz for the broader stablecoin operating-stack comparison, open-payments for the lower-level account-and-grant split, and fireblocks for the custody-and-policy layer many treasury stacks still depend on.

• Last reviewed: 2026-05-27 UTC