Crypto.com Pay review

Why a zero transaction fee is not a zero cost#

The provider states that payments carry no transaction fee and that the merchant receives the full fiat amount of the sale. What it charges instead is a settlement fee of 0.5% when the balance is paid out, plus whatever the banking intermediaries take on a fiat transfer. For a merchant settling in crypto to a Crypto.com account, the 0.5% is effectively the whole cost.

That structure is unusual and worth understanding before comparing the headline with a 1% competitor. The comparison is honest only once both are expressed as a share of settled value, and on that basis this card is among the cheapest in the index that also offers fiat. The figures come from the merchant page and the developer documentation, checked on the date shown.

Who the closed-loop side is for#

A large share of the value here is the app's own user base: a customer already holding a balance in the Crypto.com app pays with a scan, without gas fees and without waiting for confirmations. For a merchant whose customers overlap with that base, conversion at checkout is materially better than an on-chain flow.

The same property is the limitation. A customer without the app pays on chain from a wallet, and that path supports fewer assets and behaves like any other gateway. Ask what share of your customers already hold an account before treating the frictionless case as the typical one.

What the settlement rules actually say#

Fiat payouts are available in USD, EUR and AUD, with EUR limited to SEPA countries, and the documentation publishes minimum payout amounts for each: 100 USD, 130 EUR, 150 AUD. Crypto settlement is available in BTC, ETH, CRO and USDC with their own minimums. Small merchants should read those floors carefully, because a slow month can leave a balance sitting below the threshold.

GBP settlement was announced separately for eligible merchants and is not listed in the general documentation, so treat it as something to confirm in writing rather than assume. Transmittance fees on the bank leg are explicitly outside the provider's control, which is the one component of the cost that cannot be read off the page.

Integration surface#

Plugins are published for Shopify, WooCommerce, PrestaShop, Magento 2, Ecwid and OpenCart, and the API covers payments, refunds, customers, products, subscriptions and invoices with webhook events for each. Refunds are supported in full and in part, which matters more than it sounds: several providers in this index treat a refund as a manual outbound payment.

Subscriptions are handled as a documented flow with automatic billing attempts and failure events. That does not change the underlying constraint of crypto billing, where a customer with an empty balance cannot be charged, but it does mean the retry and notification logic exists rather than being yours to build.

What is not published#

Merchant verification is referred to as compliance approval and nothing more. There is no public list of documents, no stated processing time and no statement of which verticals are declined. For a regulated entity in Malta the process is unlikely to be light, and the absence of detail is the reason onboarding scores where it does here.

Mass payouts and white label are not mentioned on the public pages at all, and the founding date of the payments product is not stated. Each of those is recorded as not disclosed rather than assumed, and each is a fair question to put to the provider in writing before signing.

Who should not choose this#

A business that needs settlement in a currency outside the three listed, or in a country the SEPA restriction excludes for euro. The rate is attractive and irrelevant if the money cannot reach your bank in the form you need.

A merchant serving a customer base that does not use the app and pays exclusively from external wallets. The frictionless path is the reason to pick this provider, and without it the offer narrows to a competent but ordinary custodial gateway with a small asset list.

How this card scores where it does#

Cost scores well because two of the three cost components are published as numbers and the third is explicitly attributed to banks rather than hidden. Integrations score well on the breadth of plugins and the depth of the API. Coverage is held back by the short settlement list and the three networks named publicly.

Onboarding is the weakest verifiable line, for the reason above: a regulated provider that publishes nothing about its process forces every merchant to discover it by applying. The methodology page lets you reweight that if your business has already been through a similar process elsewhere.

Where Crypto.com Pay sits in the index#

The short version: the cheapest published route to fiat settlement in this index for a merchant whose customers already use the app, and an ordinary custodial gateway for everyone else. Every figure above was read from the merchant page and the developer documentation on 2026-09-06.

If you disagree with the position, the criterion to move is coverage. Widen its weight and the short settlement list costs more; narrow it and the published cost lifts this card toward the top. The comparison with Coinbase Commerce is the natural next read.