Mural Pay

• Name: Mural Pay
• URL: https://muralpay.com/
• Tags: ethereum-ecosystem
• Category: Stablecoin payments / global accounts / treasury infrastructure
• Summary: Mural Pay at the project layer is the API and account surface inside a broader Mural company shell. Keep this note on the product mechanics — accounts, payins, payouts, counterparties, webhook integration, and settlement-strategy controls — while the named operator boundary around onboarding, compliance tiers, custody posture, and transaction-policy authority now lives in mural-pay.
• 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 a broad product surface: organizations, accounts, payins, payouts, counterparties, transactions, developer fees, settlement strategies, event/webhook systems, sandboxing, and multiple custody-model branches
  • The docs show Mural exposing reusable objects and workflows — organizations, accounts, counterparties, payout methods, payout requests, webhook subscriptions, and settlement strategies — rather than only one checkout or remittance endpoint
  • The product layer stays analytically useful because it shows how developers actually integrate treasury and payout workflow, even though the legal/compliance shell above it belongs in mural-pay
• Whitepaper: No classic standalone whitepaper or litepaper is the point here. The strongest product-layer primary materials remain the homepage, developer landing page, docs overview, docs index, and API materials, now complemented by the company-side source capture in ../whitepapers/mural-pay-company-primary-sources-2026-08-08.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

• Company / operator boundary for onboarding, compliance tiers, custody posture, and transaction-policy authority: mural-pay.
• Strongest adjacent company comparisons: bridge-xyz, openpayd, and moonpay.

Protocol / company boundary

• Keep this note on the product surface: account objects, payins, payouts, counterparty and payout-method management, webhook integration, developer-fee settings, and settlement-strategy controls.
• Use mural-pay for the named operator boundary around terms acceptance, compliance reviews, attestation workflow, custody-model selection, API-key and IP-allowlist control, and the broader legal right to suspend or reverse transaction activity.
• That split matters because how do I integrate the Mural account stack? and which company controls admission, tiers, custody posture, and transaction policy around that stack? are related but not identical questions.

Control surface

• At the product layer, authority sits in the account model, payin and payout workflow, counterparty objects, payout-method validation, developer-fee and settlement-strategy settings, and the signed webhook/event surface downstream systems may treat as lifecycle truth.

• The thicker onboarding, compliance, and legal shell now points upward to mural-pay.

• Read this note as regulated money-movement middleware rather than an open payment standard.

• Last reviewed: 2026-08-08 UTC