Mercuryo review

Mercuryo is a managed crypto payment service that businesses integrate into their own apps and platforms. It sits between an end user’s fiat payment method, a crypto purchase or sale, and the wallet or platform where that transaction is used. The product is aimed at wallets, exchanges, fintech apps and other Web3 businesses that want to offer crypto transactions without building their own payment system.

The service covers on-ramps for buying crypto and off-ramps for selling it. Its homepage also describes virtual co-branded Spend cards, which let users spend crypto from a connected wallet. Businesses can embed Mercuryo using a widget or iFrame, or integrate through an SDK or API. The vendor says it supports more than 70 cryptocurrencies and 150+ countries. Mercuryo was founded in 2018; its homepage says it has processed $2 billion in volume and onboarded 12 million people to Web3.

The homepage names four integration surfaces: a crypto widget, iFrame, SDK and API. It describes the iFrame option as an embedded Webview and says businesses can integrate payments natively or embed them. That gives teams a choice between a more contained checkout and a closer in-app integration, but the homepage does not name an API protocol or SDK languages. Ask Mercuryo to confirm supported languages, API conventions, authentication, webhooks and versioning before estimating implementation work.

The homepage does not name a CLI or language-specific SDKs, so confirm SDK support in Mercuryo’s developer docs before committing to one. It says a dedicated support manager helps with integration and that Mercuryo provides onboarding, compliance support and recommendations. The vendor also points builders to its Ecosystem Program for developer support. Check the documentation for transaction states, error handling, test environments and how failed or pending payments are surfaced to your app.

The pricing page lists transaction-based fees, not monthly or annual subscription billing, and no free plan. Card, mobile-pay and alternative-payment buys cost up to 5.5% or €1 minimum. Bank-transfer buys cost up to 3% or €2 minimum. Sells cost up to 3.95% or €4 minimum, though some support documentation says the minimum is €3. Wallet receives and withdrawals are listed as free.

Budget for additional charges: non-EUR fiat conversion adds 0.25%–1%; the infrastructure fee is typically 0%–2%, capped at 5%; and Fast Track can add up to 5%. These are transaction costs, so the bill rises with payment volume and the methods customers choose. The listed amounts are fees, not a monthly starting price. Before launch, ask Mercuryo which infrastructure fee applies to your integration, whether it is charged on top of the payment-method fee, and how failed, reversed or refunded transactions are treated. Model the fee mix against your expected countries, currencies and payment methods.

Mercuryo is presented as an integrated payment service, not as a library or self-hosted server. The vendor doesn’t publish a source license, self-hosting option or data-export process on its homepage. Treat the integration as dependent on Mercuryo’s service unless the vendor confirms otherwise in writing.

That creates ordinary payment-provider lock-in: your checkout flow, payment status handling and support process may rely on Mercuryo’s APIs or embedded components. Keep your own records of orders, transaction IDs and customer-visible states, and avoid making Mercuryo-specific response fields part of your internal payment model. Before signing, ask about transaction history exports, retention, wallet and customer data portability, contract termination, and how to migrate pending transactions. A second provider may reduce dependency, but requires routing, reconciliation and compliance work.

The homepage advertises support in 150+ countries, more than 10 payment methods and 24/7 customer care. It does not state API rate limits or an uptime commitment, so confirm capacity, incident escalation and service-level terms before routing production traffic. Ask how KYC, payment failures, refunds, chargebacks and pending crypto transfers appear in the integration, and verify which countries and payment methods apply to your users.

Reddit reports are mixed and anecdotal. One thread describes a transfer remaining pending; commenters report delays of up to five days, funds returned to a Mercuryo wallet, and a case where a withdrawal fee appeared after a failed transfer. Other commenters say support helped resolve issues, though one described waiting in a chat queue. These reports do not establish typical performance, but they make clear status visibility and escalation paths matter. The homepage mentions onboarding and compliance support, but ask the vendor for the specific controls and commitments your product requires.