Cowrie Research

mural-pay-primary-sources-2026-04-25

5 min read

Mural Pay primary-source snapshot

Fetched: 2026-04-25 UTC

1) Official homepage

Source: https://muralpay.com/

Selected excerpts from the official site:

Global Accounts. Realtime Payments. One API.

Financial infrastructure for platforms, fintechs, and banks building the future of money.

Deploy enterprise-grade stablecoin infrastructure with Mural Pay—launch accounts, wallets, and payments in weeks.

Additional signals from the homepage:

  • The site frames Mural as infrastructure for operational money movement, not a consumer wallet or token project
  • Product surfaces are organized around Store / Send / Receive / Convert / Earn / Comply rather than around a single protocol primitive

2) Developer landing page

Source: https://muralpay.com/developers

Selected excerpts from the official site:

Build the next generation of financial products

Stablecoin infrastructure that turns financial operations into a competitive advantage—launch accounts, move money globally, and manage treasury with real-time settlement and compliance built in.

We are not just an API provider—we are your engineering partner.

Additional signals from the developer page:

  • The page positions Mural as a programmable finance layer for embedded finance, marketplaces, contractor payouts, and treasury operations
  • Example API requests show payin flows parameterized by destination token and fiat rail details, reinforcing that the core product is operational payments infrastructure

3) API overview

Source: https://developers.muralpay.com/docs/getting-started

Selected excerpts from the docs:

Welcome to Mural API documentation! Mural provides platforms, fintechs, and financial institutions with stablecoin account infrastructure to build and manage global money movement.

Our APIs make it easy to create accounts that can receive, hold, convert, and move money — in fiat or stablecoins — across borders and payment networks.

Additional signals from the docs:

  • The API docs are a stronger source of truth than the marketing homepage for determining actual product scope
  • The docs explicitly target platforms, fintechs, and financial institutions rather than purely crypto-native protocols

4) AI developer resources / MCP surfaces

Source: https://developers.muralpay.com/docs/ai-developer-resources Source: https://developers.muralpay.com/docs/mcp

Selected excerpts from the docs:

Connect AI tools to Mural Pay’s documentation using the Model Context Protocol for an enhanced development assistance.

You can download our generated OpenAPI spec here …

The Mural Pay API Model Context Protocol (MCP) server enables AI-powered code editors like Cursor and Windsurf, plus general-purpose tools like Claude Code, to interact directly with the Mural Pay API and documentation.

Additional signals from the docs:

  • Mural is unusually explicit about AI-native developer enablement, exposing MCP, OpenAPI, and llms.txt artifacts as first-class documentation outputs
  • This is a strong indicator that the company expects developers to integrate and reason about its payments stack through tooling, not just dashboard usage

5) llms.txt documentation index

Source: https://developers.muralpay.com/llms.txt

Selected excerpts/signals from the docs index:

Custody Models

Mural Custody

End-User Custody (Non-Custodial)

Webhooks

Signature Validation

Sandbox Environment

Additional signals from the docs index:

  • The public docs index exposes a broad operational footprint: custody models, compliance reviews, accounts, counterparties, payins, payouts, fees, validations, event types, webhooks, and sandbox support
  • This broad surface suggests Mural is best understood as a money-movement control plane rather than just an on/offramp widget

6) Knowledge-base security / approval workflow

Source: https://docs.muralpay.com/articles/9213189885-wallet-to-passkey-migration

Selected excerpts from the knowledge base:

For Accounts managed by your external wallet as an Approver, you can migrate to a passkey-based approval …

Mural will automatically generate a change request to add your passkey-based digital signature as an Approver on the Account.

Additional signals from the knowledge base:

  • Mural documents account-approval and signature-management workflows in detail, which is useful for understanding operational custody boundaries
  • The passkey migration flow shows Mural supporting both wallet-linked and passkey-based approval patterns rather than assuming a single custody model

7) Knowledge-base compliance requirements

Source: https://docs.muralpay.com/articles/2962171586-business-identity-verification

Selected excerpts from the knowledge base:

To comply with international regulations and secure your account, Mural Pay is required to collect and verify information about the business and its ownership.

Required if you are … An API Customer / Developer

Mural is required to confirm all individual ultimate beneficial owners who own 25% or more of the underlying entity.

Additional signals from the knowledge base:

  • Compliance review is a core product component, not a side note: the docs detail business formation documents, ownership attestations, AML/program questions, licensing disclosures, and flow-of-funds diagrams
  • The enhanced onboarding requirements for API customers are especially important because they show Mural operating inside a regulated payments/compliance stack rather than merely exposing software rails

8) Fee / delivery documentation

Source: https://docs.muralpay.com/articles/1779974491-understanding-fees-transaction-processing-times-and-cut-off-times

Selected excerpts from the knowledge base:

This article provides a comprehensive overview of Mural Pay’s fee structure, transaction processing times, and cut-off times for both Deposits (pay-ins or onramps) and Withdrawals (payouts or offramps).

Crypto transactions (USDC, USDT) are processed instantly and have no cut-off time.

Additional signals from the knowledge base:

  • Public payout and payin timing tables reveal supported geographies, local rails, FX charges, and operational cut-off windows in a way many crypto/payment vendors do not publish openly
  • This makes Mural legible as actual execution infrastructure rather than purely a front-end integration layer

9) Public GitHub organization

Source: https://github.com/muralpay

Selected excerpts/signals from the public org page:

An example server that can listen to mural api webhooks

A simple demo using the mural-browser-sdk and the Mural API to facilitate End-user custodial payouts

A collection of resources useful for developers

Additional signals from the GitHub org:

  • Even with a small public footprint, the org exposes webhook demos and custodial payout examples that support the API/docs claims
  • The public repositories reinforce that Mural ships real developer-facing implementation material rather than keeping all integration knowledge behind sales channels

Notes

  • This pass did not locate a classic whitepaper or litepaper from official Mural sources.
  • The strongest primary materials were the homepage, developer landing page, API overview, AI/MCP docs, llms.txt, knowledge-base articles, fee/delivery tables, and public GitHub repositories.
  • Mural appears best categorized as stablecoin payments / global accounts / treasury infrastructure with strong compliance and developer-tooling surfaces.

Graph View