Cowrie Research

mesh

4 min read

Mesh

  • Name: Mesh
  • URL: https://www.meshpay.com/
  • Category: hosted account connectivity / transfer orchestration / exchange-wallet payment middleware
  • Tags: ethereum-ecosystem solana-ecosystem
  • Summary: Mesh is hosted account connectivity and transfer orchestration. It lets apps borrow a user’s existing exchange or wallet account long enough to route a payment, deposit, or verification flow while Mesh handles login, MFA, integration quirks, and transfer-status truth. Keep this note on the product surface; use mesh when the sharper question is which named operator controls supported integrations, managed-auth token lifecycles, webhook-backed finality signals, and the hosted account-connection shell many apps actually depend on.
  • 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
    • Coverage claims are broad but slippery: the homepage markets 300+ supported platforms, while the reviewed docs snapshot showed 24 networks, about 120 tokens, 233 wallets, and 8 major exchanges, so the breadth matters more than the exact brag number
    • 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

Internal linkages

  • Company-layer companion: mesh.
  • walletconnect-pay — closest upward read for wallet-connected payment packaging.
  • coinflow — stronger operator-stack contrast when the merchant-facing settlement and checkout layer matters more than exchange-account connectivity.

Protocol / company boundary

  • Keep mesh on the product mechanics: Link Token issuance, SDK launch, callback semantics, managed-account-token reuse, webhook integration shape, and the Pay / Deposit / Verify flow decomposition.
  • Use mesh when the sharper question is who decides which exchanges and wallets are supported, who hosts the authentication and compliance shell, who manages token refresh and reusable account connectivity, and who signs the final transfer-status events that downstream businesses treat as operational truth.
  • That split matters because account-connectivity middleware can sound neutral at the API layer while still depending on one company-run service boundary for session setup, supported-integration coverage, and final callback truth.

Control surface

Graph View

Backlinks