Mercuryo

• Name: Mercuryo
• URL: https://www.mercuryo.io/
• Category: fiat-crypto on/off-ramp infrastructure / wallet-and-card payments platform / embedded widget and API control plane
• Summary: Mercuryo is broader than a buy-crypto widget. The useful cut is embedded ramp plus card-and-wallet operations: wallet creation, fiat balances, buy/sell and withdrawal flows, virtual-card spend, and partner-facing wrappers that let apps outsource that messy operator layer.
• What it does:
  • Offers fiat-to-crypto and crypto-to-fiat flows that partners can embed through widgets, wrappers, and API integrations
  • Markets both an on-ramp product and a Spend product centered on virtual co-branded cards linked to crypto balances
  • Publishes mobile-SDK materials covering authentication, wallet management, buy/sell/withdraw flows, and card usage
  • Exposes BAAS/API materials for Mercuryo wallets, fiat balances, transaction monitoring, and bank-transfer or IBAN-linked operations
  • Maintains widget-wrapper repos for iOS and Android, confirming an embedded mobile integration surface rather than a web-only checkout path
• Key claims:
  • Mercuryo calls itself the payment engine behind web3 businesses and markets both On-Ramp and Spend as first-class product families
  • The BAAS/API docs describe crypto and fiat balances, top-ups, withdrawals, and exchange flows rather than a thin referral widget
  • Public materials explicitly cover buy-with-card, bank-transfer and IBAN flows, sell-to-card, fiat deposits, and fiat withdrawals
  • The mobile SDK docs frame Mercuryo as a multicurrency wallet and integration platform, which makes the wallet-and-payments control-plane angle clearer than the homepage alone
  • The GitHub surface shows the product is operational middleware with wrappers, SDK docs, and migration docs, not just checkout UX
• Whitepaper: No canonical Mercuryo whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official site plus Mercuryo’s GitHub organization, especially the BAAS/API materials, mobile SDK docs, widget-wrapper repos, and API migration notes collected in ../whitepapers/mercuryo-primary-sources-2026-04-27.md.
• Sources:
  • https://www.mercuryo.io/
  • https://github.com/mercuryoio
  • https://github.com/mercuryoio/BAAS-API
  • https://raw.githubusercontent.com/mercuryoio/Mobile-SDK-Docs/master/README.md
  • https://raw.githubusercontent.com/mercuryoio/iOS-SDK/main/README.md
  • https://raw.githubusercontent.com/mercuryoio/Mercuryo-Widget-Wrapper-iOS/master/README.md
  • https://raw.githubusercontent.com/mercuryoio/Mercuryo-Widget-Wrapper-Android/master/README.md
  • https://raw.githubusercontent.com/mercuryoio/api-migration-docs/master/README.md

Internal linkages

• Strongest upward reads: transak, ramp-network, and openpayd.

Control surface

• Power sits in KYC and geography policy, bank-and-card rail admission, wallet and balance custody assumptions, payout defaults, and which partner flows Mercuryo makes operationally easy.

• Broad operator stack, but still not a category anchor.

• Last reviewed: 2026-06-03 UTC