Mesh
- Name: Mesh
- URL: https://www.meshpay.com/
- Category: Crypto payments network / exchange-wallet connectivity / embedded transfer infrastructure
- Summary: Mesh is hosted account-connectivity and transfer orchestration, not a new payment rail. It lets apps wrap pay, deposit, and verify flows around accounts users already hold elsewhere while Mesh handles the annoying parts: login and MFA flow, integration discovery, session setup, transfer tracking, and webhook truth.
- What it does:
- Provides Mesh Link SDKs for web, iOS, Android, React Native, and Flutter so apps can embed exchange and wallet connection flows inside their own product
- Starts each user session with a short-lived, single-use Link Token created server-side, which encodes transfer type, destination, asset/network constraints, and other session parameters
- Supports three main flows: Pay, Deposit, and Verify
- Exposes backend APIs for supported integrations, supported networks and tokens, balances or portfolios, and managed transfer initiation or tracking
- Lets integrators save managed-account tokens for return-user flows so later sessions can skip full re-authentication
- Uses webhooks rather than client callbacks as the final source of truth for transfer completion
- Key claims:
- Mesh markets itself as the
first global crypto payments network, but the docs read more concretely as a hosted connectivity and transfer-orchestration layer spanning wallets, exchanges, and merchant-facing payment flows - The docs’ integration model is explicit: server creates a Link Token, client launches the SDK, callbacks report user-side events, and signed webhooks carry final transfer state for backend settlement logic
- Link Tokens are short-lived and single-use, which makes session configuration and transfer policy a real operator surface rather than just a UI detail
- The current support matrix is broad but specific: the marketing site says 300+ supported platforms, while the support reference currently lists 24 networks, 18 stablecoins, 225 wallet integrations, and 7 major exchange integrations
- Mesh Managed Tokens matter because they turn a one-time account connection into reusable offchain authorization state for later one-tap or two-tap flows
- SmartFunding is one of the more important product wrinkles: it lets a user complete a payment from assets they already hold, even when the merchant wants settlement in a different token
- Mesh markets itself as the
Internal linkages
- walletconnect-pay — closest upward read for wallet-connected payment packaging
- open-payments — stronger protocol contrast when account addressing and payment authorization are kept separate from hosted connectivity
Control surface
-
Power sits in integration admission, Link Token policy, managed-account-token reuse, and webhook-confirmed transfer status.
-
Read it as hosted connectivity and routing middleware, not as a neutral payment rail.
-
Whitepaper: No classic whitepaper or litepaper was found during this pass. The main primary materials were the official site, docs portal, API reference, and sandbox documentation; see
../whitepapers/mesh-primary-sources-2026-04-22.md. -
Sources:
- https://www.meshpay.com/
- https://docs.meshconnect.com/overview
- https://docs.meshconnect.com/manual
- https://docs.meshconnect.com/supported-tokens
- https://docs.meshconnect.com/api-reference/managed-account-authentication/retrieve-the-list-of-all-available-integrations
- https://docs.meshconnect.com/api-reference/managed-transfers/get-supported-tokens-list
- https://docs.meshconnect.com/testing/sandbox
- https://docs.meshconnect.com/llms.txt
-
Last reviewed: 2026-06-04 UTC