mercuryo-primary-sources-2026-04-27

Mercuryo primary-source snapshot

Last reviewed: 2026-04-27 UTC

Project status snapshot

• Official site: https://www.mercuryo.io/
• GitHub org: https://github.com/mercuryoio
• BAAS/API repo: https://github.com/mercuryoio/BAAS-API
• Mobile SDK docs README: https://raw.githubusercontent.com/mercuryoio/Mobile-SDK-Docs/master/README.md
• iOS SDK README: https://raw.githubusercontent.com/mercuryoio/iOS-SDK/main/README.md
• iOS widget wrapper README: https://raw.githubusercontent.com/mercuryoio/Mercuryo-Widget-Wrapper-iOS/master/README.md
• Android widget wrapper README: https://raw.githubusercontent.com/mercuryoio/Mercuryo-Widget-Wrapper-Android/master/README.md
• API migration notes: https://raw.githubusercontent.com/mercuryoio/api-migration-docs/master/README.md

What the official materials say

1) Homepage positioning

• URL: https://www.mercuryo.io/
• Key takeaways:
  • Mercuryo positions itself as “The payment engine behind top web3 business,” which is broader than a single consumer wallet or standalone widget brand
  • The homepage claims 500+ web3 partners, 150+ supported countries, 10+ payment methods, and 70+ supported cryptocurrencies
  • The visible product taxonomy includes both an On-Ramp product and a Spend product for virtual co-branded cards, which is a strong clue that Mercuryo should be cataloged as broader payment infrastructure rather than only as a buy-crypto tool

2) GitHub org and repo inventory

• URLs:
  • https://github.com/mercuryoio
  • https://github.com/mercuryoio/BAAS-API
• Key takeaways:
  • The public GitHub org is unusually informative and exposes BAAS/API materials, mobile SDK docs, pay docs, widget wrappers, and legacy integration repos
  • This repo inventory makes GitHub part of the first-class primary-source surface for understanding Mercuryo’s actual integration footprint
  • The BAAS/API repo content shows Mercuryo organizing around user wallets, fiat balances, partner monitoring, and structured transaction types rather than around a frontend-only checkout experience

3) BAAS/API surface

• URLs:
  • https://github.com/mercuryoio/BAAS-API
  • https://raw.githubusercontent.com/mercuryoio/api-migration-docs/master/README.md
• Key takeaways:
  • The BAAS/API docs say Mercuryo API gives users crypto and fiat balances and lets them exchange fiat to crypto and crypto to fiat, top up fiat balances, and withdraw funds
  • The docs explicitly describe flows for buy-with-card, buy-with-bank-transfer, buy-with-IBAN, top up IBAN, sell-to-card, and withdraw-from-IBAN operations
  • KYC and KYC2 language plus EU-only IBAN notes show that the platform includes compliance-gated banking-style surfaces, not just crypto checkout
  • The migration docs show versioned public endpoints for widget buy/sell rates and conversion paths, which indicates an API surface with operational lifecycle and backward-compatibility concerns

4) Mobile SDK and wallet/card surfaces

• URLs:
  • https://raw.githubusercontent.com/mercuryoio/Mobile-SDK-Docs/master/README.md
  • https://raw.githubusercontent.com/mercuryoio/iOS-SDK/main/README.md
• Key takeaways:
  • Mercuryo describes itself here as a multicurrency crypto wallet that also provides a platform for developers to build on top of its API
  • The mobile SDK docs split the feature surface into authentication, wallets, operations, and cards, which materially broadens the picture beyond an on-ramp-only product
  • The SDK materials imply Mercuryo is trying to serve as a reusable wallet-and-payments substrate inside partner mobile applications

5) Widget wrappers and embedded flows

• URLs:
  • https://raw.githubusercontent.com/mercuryoio/Mercuryo-Widget-Wrapper-iOS/master/README.md
  • https://raw.githubusercontent.com/mercuryoio/Mercuryo-Widget-Wrapper-Android/master/README.md
• Key takeaways:
  • Mercuryo publishes lightweight iOS and Android widget-wrapper libraries to embed its widget into mobile applications via WebView-style flows
  • The iOS wrapper docs explicitly discuss widget IDs, production vs sandbox environments, and host-app error handling, which is useful for understanding the operational integration model
  • These wrappers confirm Mercuryo supports embedded partner UX rather than only redirect-style checkout on the open web

Whitepaper / technical-doc status

• 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 and repo-level documentation.
• The developer surface appears fragmented across multiple repos and older doc formats, but the fragmentation is itself informative because it reveals Mercuryo’s breadth across widget, wallet, banking-style API, and card surfaces.

Research notes

• Best current category for the library: fiat-crypto on/off-ramp infrastructure / wallet-and-card payments platform / embedded widget and API control plane.
• Most important categorization clue: the BAAS/API and mobile SDK materials expose wallet, fiat-balance, card, and IBAN operations that go well beyond a simple on-ramp widget.
• Good future follow-up: check whether Mercuryo’s current hosted developer portal has a cleaner replacement for the GitHub-heavy documentation trail.