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 at the project layer is the bank-to-wallet transfer SDK surface inside a broader Meso company shell. The useful product cut is the hosted transfer launch, wallet-verification handshake, supported network and asset configuration, and lifecycle events apps wire into their own UX. The broader operator boundary now lives in meso, which is the cleaner place to reason about partner admission, origin registration, private-beta access, partnerId issuance, KYC and identity workflow, bank-debit origination, and company-run transfer-state truth.
• 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:
  • https://meso.network/
  • https://github.com/meso-network
  • https://github.com/meso-network/meso-js
  • https://raw.githubusercontent.com/meso-network/meso-js/main/README.md
  • https://raw.githubusercontent.com/meso-network/meso-js/main/packages/meso-js/README.md
  • https://github.com/meso-network/meso-ios-example
  • https://raw.githubusercontent.com/meso-network/meso-ios-example/main/README.md

Internal linkages

• Company boundary for partner admission, origin registration, private-beta access, partnerId issuance, KYC flow, bank-debit origination, and transfer-state publication: meso.
• Useful adjacent company reads where the operator shell is thicker than the narrow transfer SDK: transak and ramp-network.
• Best routing-layer contrast above any single provider shell: onramper.

Protocol / company boundary

• Keep this note on the product surface: hosted transfer launch, wallet-verification callbacks, supported network and asset configuration, event lifecycle, and the host-app wiring needed to embed Meso cleanly.
• Use meso for the named-operator layer around partner admission, origin approval, private-beta access, partnerId issuance, KYC and identity workflow, bank-debit handling, and the company-run truth surfaces when transfer state is disputed.
• That split matters because how does the Meso SDK behave? and which company controls onboarding, debit origination, and transfer-state authority? are related but not identical questions.

Control surface

• At the product layer, authority sits in SDK launch shape, wallet-verification mode, event delivery, supported network and asset selection, and how tightly the host app couples its funding UX to Meso-specific callbacks and transfer states.

• The broader operator dependency sits one layer up in meso: partner admission, approved origins, partnerId issuance, KYC and identity workflow, bank-debit origination, and company-run lifecycle truth.

• Useful note, but the more durable lock-in story is the company boundary above it.

• Last reviewed: 2026-08-11 UTC