Mercuryo review

Mercuryo is crypto payment infrastructure for businesses, not simply a retail exchange. Founded in 2018, it helps apps and websites add ways for customers to buy or sell crypto, transfer funds, and use related payment services. The business can integrate Mercuryo through a widget, iFrame, SDK, or API.

On the customer side, Mercuryo supports purchases using cards, Apple Pay, Google Pay, bank transfers, SEPA, and local payment methods. It says it supports more than 70 cryptocurrencies and offers both on-ramps (buying crypto) and off-ramps (selling crypto). It also offers virtual co-branded spend cards connected to a wallet.

That makes Mercuryo most relevant to a company that wants crypto payment options inside its own product. It is less straightforward to assess as a standalone exchange: the published product information focuses on business integrations, and does not spell out a consumer account’s full feature set.

Mercuryo’s main advantage is breadth of integration options. Businesses can choose a widget or iFrame rather than building a full integration, or use an SDK or API. The listed payment methods cover cards, mobile wallets, bank transfers, SEPA, and local methods, while support for more than 70 cryptocurrencies gives customers a broad stated selection. The platform also covers both buying and selling crypto, rather than only handling purchases.

There are a few useful details for teams comparing payment costs. The pricing information lists no fees for wallet receives and withdrawals. It also describes transaction-based fees rather than a monthly or annual subscription price, so the listed cost model is tied to payment activity, not a stated software seat fee. Businesses can also offer virtual co-branded spend cards connected to a wallet, if that fits their product.

For a web3 business that wants payment rails inside its app, these features make Mercuryo worth evaluating. The value is less clear for an individual buyer: the available information does not publish a subscription plan or give a single all-in transaction price.

Fees can add up, and the pricing is not especially simple. According to the pricing information checked November 6, 2026, card, mobile-pay, and alternative-payment buys cost up to 5.5% or a €1 minimum; bank-transfer buys cost up to 3% or €2 minimum. Sells are listed at up to 3.95% or €4 minimum, although some support documentation reportedly says the minimum is €3. Non-EUR fiat conversion adds 0.25%–1%. An infrastructure fee is typically 0%–2%, but can reach 5%; Fast Track can add up to another 5%. These are transaction costs, not a published monthly plan price.

User reports on Reddit are mixed and should be treated as anecdotes, not proof of a general pattern. One thread describes a pending transfer and later an unexpected withdrawal fee; commenters in another report delays, including funds taking days to arrive. A separate post alleges unauthorized bank withdrawals. The reports do not establish how common these problems are, but they do make settlement timing, destination-network requirements, and support response worth checking before routing meaningful volume through Mercuryo.

Mercuryo’s published pricing information lists transaction fees, not monthly or annual plans. There’s no published tier ladder or tier jump to compare, and no free plan; a free trial is not published. Your cost depends on the transaction type.

• Card, mobile-pay and alternative-payment buys: up to 5.5%, or €1 minimum.
• Bank-transfer buys: up to 3%, or €2 minimum.
• Sells: up to 3.95%, with a €4 minimum in the pricing summary. Some support documentation lists a €3 minimum, so confirm the applicable fee before launch.
• Wallet receives and withdrawals: no fees listed.

Other charges can change the bill: 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%. The pricing information does not explain how these fees combine on a particular transaction. Treat the figures as variable transaction costs, not a fixed quote.

Mercuryo offers a widget, iFrame, SDK and API, so the migration work depends on how your app embeds its payment flow. Switching to Mercuryo means choosing an integration method and connecting the relevant buy, sell or transfer journeys. Switching away likely means replacing those flows and updating the app’s integration; the published material does not detail migration tools or a standard timeline.

Lock-in terms and data-export options are not published on the vendor's site. Before committing, ask what transaction and customer data you can export, and how you can retrieve it if you leave.

The review brief flags uneven user reports and transfer delays as concerns, but it includes no Reddit posts or specific examples. We can’t identify a recurring Reddit-reported reason for leaving from the available sources. For a team that needs predictable costs or wants documented transfer and exit procedures, get those details in writing before switching.