Cowrie Research

mural-pay-company-primary-sources-2026-08-08

5 min read

Mural Pay company primary-source snapshot

Fetched: 2026-08-08 UTC

1) Mural Pay homepage

Source: https://muralpay.com/

Selected excerpts from the official site:

Global Accounts. Realtime Payments. One API.

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

Mural Pay automates compliance checks and regulatory reporting so you can focus on growing your business.

Additional signals from the source:

  • Mural is selling a bundled operating shell, not one narrow checkout widget.
  • The homepage groups storage, send, receive, convert, earn, and comply inside one company-run product story.
  • The useful analytical question is therefore not just what API call exists? but which named operator controls the combined account, payout, FX, and compliance workflow?

2) Developer page

Source: https://muralpay.com/developers

Selected excerpts from the official site:

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. Our team includes forward deployed engineers who embed directly with your team to accelerate integration.

Additional signals from the source:

  • Mural presents the integration as a services-heavy company relationship, not only as a neutral standard.
  • The page keeps treasury, payouts, marketplace payments, and white-label account issuance under one operator-run shell.
  • This supports a company/entity split because operational dependence on Mural personnel and packaged workflow is part of the real control surface.

3) Docs overview

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

Selected excerpts from the official docs:

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 source:

  • The docs describe a broad account-and-money-movement shell rather than one narrow rail.
  • The note belongs in companies/ because the practical question is who runs this account infrastructure and decides how it is packaged.

4) Docs index (llms.txt)

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

Selected notable entries from the official docs index:

Generate API Keys

Set IP Allowlist

Compliance Reviews

End-User Custodial Resources

Custody Models

Set settlement strategy for an Account

Additional signals from the source:

  • The docs index alone makes the operator boundary legible: credentials, allowlists, compliance, custody mode, settlement strategy, and webhook validation all sit inside one commercial API shell.
  • This is strong evidence that Mural is not just a passive transport layer.

5) Compliance Reviews docs

Source: https://developers.muralpay.com/docs/compliance-reviews

Selected excerpts from the official docs:

Before an Organization can transact, it must complete at least one Compliance Review to establish a verified identity Tier.

Business Organizations that report transmittingCustomerFunds: true on the businessOperations attestation will see businessFlowOfFundsDocument added to requiredAttestations after that upload.

FULL … Unlocks Mural’s international offramp providers in addition to everything US_STANDARD enables.

Additional signals from the source:

  • Mural controls a tiered onboarding gate that directly changes which payment rails become available.
  • The company is therefore not only relaying transactions; it is deciding the compliance and documentation boundary for money movement.

6) Custody Models docs

Source: https://developers.muralpay.com/docs/custody-models

Selected excerpt from the official docs:

The Mural Pay API supports integration models that accommodate both client custodial and end-user custodial payments.

As the Developer, it is your responsibility to choose the integration model that aligns with your regulatory requirements and compliance posture

Additional signals from the source:

  • Custody posture is an explicit part of the integration design, not an invisible implementation detail.
  • That makes Mural a real compliance-and-liability boundary even when funds are not always held under one identical model.

7) Webhooks docs

Source: https://developers.muralpay.com/docs/mural-webhooks

Selected excerpts from the official docs:

This will return a public key in PEM format that you can use to verify webhook event signatures coming from Mural.

Events are delivered in the order they occur per Webhook-category pair

Failed deliveries (non 200 http responses) are attempted a total of 3 times with exponential backoff for up to 6 minutes.

Additional signals from the source:

  • Mural operates a signed event-publication surface that downstream systems may treat as transaction-state truth.
  • Webhook design, retry behavior, and signature verification are part of the real operator boundary.

8) Platform Terms of Service

Source: https://muralpay.com/legal/platform-terms-of-service

Selected excerpts from the official terms:

Mural Networks, Inc., a Delaware corporation … and Mural Technologies, Inc., a Delaware corporation … (each of them being individually defined as “Mural”, as applicable)

Mural may suspend or terminate Customer’s and any Authorized User’s access to any portion or all of the Mural Services

Mural further reserves the right to refuse to process, or to cancel, correct, clawback, or reverse, any Transaction in its sole discretion

Additional signals from the source:

  • The legal entity shell is explicit and operationally important.
  • Mural reserves strong intervention powers around service access and transaction processing.
  • This is the clearest reason the note belongs in companies/: the named operator, not a neutral protocol, is the live control plane.

Notes

  • Mural Pay belongs in the companies/ layer because the useful question is not only what account and payout API exists? but which named operator controls onboarding, compliance tiers, custody posture, credentials, settlement policy, and transaction reversibility around that API?
  • The cleanest nearby boundary map is currently: Mural Pay for the product and integration surface, Mural Pay company note for the legal and operating shell, and adjacent operator comparisons such as Bridge, OpenPayd, and MoonPay.

Graph View