Meso

  • Name: Meso
  • URL: https://meso.network/
  • Category: fiat-to-crypto on-ramp / bank-to-wallet payments infrastructure / embedded transfer SDK
  • Tags: ethereum-ecosystem solana-ecosystem
  • Summary: Meso is a narrower bank-to-wallet ramp operator than the bigger embedded-checkout vendors. The useful layer is the partner-account model, wallet-verification handshakes, hosted transfer flow, and lifecycle events that let apps outsource ACH-style crypto funding without pretending this is a new payment rail.
  • What it does:
    • Offers a browser SDK that launches a hosted Meso transfer flow inside a web app or dapp
    • Handles onboarding steps such as KYC checks, identity verification, bank-account debits, and crypto delivery to a specified wallet address
    • Uses a partner-account model with origin allowlisting and partner-specific IDs rather than an open anonymous widget flow
    • Exposes lifecycle events and multiple wallet-authentication modes, including signed, headless, and bypassed wallet verification paths
    • Publishes a WebView-based iOS reference implementation instead of a separate official iOS SDK
  • Key claims:
    • The official site and GitHub materials both position Meso as payments infrastructure for moving money between banks and wallets
    • The public SDK docs say Meso handles KYC, identity verification, bank debits, and crypto transfers to the requested wallet address
    • The partner-ID and origin-registration requirements make clear this is embedded infrastructure, not a generic public widget
    • The wallet-verification modes are the interesting operational detail because they show where Meso inserts itself into app-controlled versus wallet-controlled flows
    • Public examples cover assets and networks including ETH, SOL, and USDC across Ethereum, Solana, and Polygon mainnet contexts
  • Whitepaper: No canonical Meso whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official site plus the verified GitHub organization, the meso-js SDK docs, and the iOS reference implementation collected in ../whitepapers/meso-primary-sources-2026-04-27.md.
  • Sources:

Internal linkages

Control surface

  • Authority sits in partner admission, origin allowlisting, wallet-verification policy, bank-debit handling, supported asset/network scope, and event delivery reliability.

  • Useful note, but this is still a narrower embedded-ramp operator than the stronger category anchors.

  • Last reviewed: 2026-06-03 UTC