Crypto Payment Gateway Due Diligence: The Questions Most Merchants Never Ask

Why the Usual Comparison Table Falls Short

Walk into any search for guidance on selecting a crypto payment processor and you will encounter the same formula repeated dozens of times: a shortlist of eight or so vendors, a grid comparing licensing scope, settlement mechanics, supported tokens, integration paths, and headline fees. Frequently, the article is authored by one of the very companies it evaluates.

None of those criteria is wrong. They are simply the dimensions that are straightforward to research, which is exactly why every writer covers them. The provisions that generate support queues, reconciliation headaches, and the occasional frozen payout are buried in policy documents that rarely appear on a pricing page. Most merchants do not think to request those documents until they are three months into a live relationship and the pain is already visible.

For traders and merchants entering the space, the educational takeaway is clear: the comparison table gets you to a shortlist. What separates the finalists is operational policy, and that policy only surfaces if you request it in writing while you are still a prospect. Once you become a customer, you inherit whatever the vendor's default was.

The Real Cost Behind the Advertised Rate

Headline processing fees in this sector typically fall between 0.4% and 1.5%. Vendors promote that figure because it is easy to benchmark and it looks attractive in a pitch deck. In practice, it is rarely the number that hits your ledger.

The true cost accumulates across four additional layers, and understanding each one is essential for anyone building a business case around crypto settlement.

Conversion spread. When you settle in fiat, a counterparty converts your digital asset at a rate that is not the mid-market price. An extra 0.3% to 1% on top of the processing fee is standard industry practice, and it is almost never itemised publicly. A well-informed merchant should request the reference rate and the spread, expressed in basis points, in a written document.

Payout costs. Crypto network fees on token payouts, SEPA or SWIFT charges on fiat transfers, and in some cases a flat per-payout fee all add up. Choosing a daily settlement cadence rather than a weekly one multiplies these charges roughly five-fold.

Minimum settlement thresholds. Certain providers will hold your funds until a minimum balance threshold is reached. For a merchant whose volume is lumpy or seasonal, this functions as a working-capital squeeze dressed up as a policy clause.

Rolling reserves. Borrowed from the card-acquiring world, this mechanism withholds 5% to 10% of processed volume for 30 to 180 days, particularly for merchants in higher-risk verticals. It is negotiable, but it tends to surface only after the underwriting stage, by which time you have already presented a go-ahead to your board.

Stack all four layers on top of a 1% headline fee and the all-in cost approaches 2.5%. That figure may still undercut card-network rates on cross-border volume, which is the comparison that genuinely matters. The educational point: you need the fully loaded number before you build your financial model, not after you have committed.

Operational Policies That Shape Daily Operations

Several policy choices determine whether your checkout flows smoothly or generates a stream of support tickets. Each one deserves a written answer from the vendor before signature.

Short-pay handling. A customer settles a 100-USDT invoice from an exchange account. The exchange deducts its withdrawal fee from the outgoing amount rather than adding it on top, so 99.2 USDT arrives. From that point, the outcome is purely a matter of provider policy. Some vendors settle anything within a tolerance band and absorb the shortfall. Others flag the invoice as partially paid and stop, triggering a support ticket, a manual review, and a customer who reasonably suspects fraud. At a few thousand transactions per month, the difference between those two approaches is a staffing decision. Ask what the tolerance band is, whether it is configurable, and who bears the shortfall inside it.

Multi-chain asset routing. USDT is issued on Ethereum, Tron, BNB Chain, Solana, Polygon, Arbitrum, and several other networks. Customers select whichever chain their wallet defaults to or whichever is cheapest that week. If an ERC-20 token is sent to an address the gateway generated for a different chain, the funds are effectively lost unless the provider controls keys on both networks and is willing to perform a manual recovery. The questions to pose: Is recovery offered at all? What does it cost? How long does it take? Which chains are explicitly out of scope?

Rate-lock windows. Most providers freeze the exchange rate at invoice creation, typically for 10 to 20 minutes. Bitcoin can move 2% within that window. If the payment confirms after expiry, one of three outcomes occurs: the invoice re-quotes (leaving the customer structurally underpaid), the provider settles at the new rate and you absorb the delta, or the transaction goes into manual review. At volume, this is a line item on your P&L. Find out which scenario applies.

Confirmation times. This quietly governs your checkout conversion rate. Waiting for three Bitcoin confirmations can hold a customer for roughly thirty minutes. Three confirmations on Tron take under ten seconds. If you sell digital goods, credit an account balance, or operate any model where the customer expects immediate delivery, the per-chain confirmation table is a product decision, not a technical footnote. Request it as a table.

Regulatory Shifts and Exit Planning

Two recent developments make it worthwhile to re-audit any shortlist.

MiCA's transitional window closed on 1 July 2026. Grandfathering under Article 143(3) has expired across all 30 EEA member states, and ESMA confirmed in April that no extension would be granted. Any provider still operating in the EU on a legacy national registration is doing so outside the law. Verifying compliance takes roughly two minutes and should be done against the ESMA register directly, rather than relying on the provider's own website, where the word "licensed" does a great deal of quiet rhetorical work.

The second shift concerns transfer-of-funds reporting. Under Regulation 2023/1113, transfers between regulated crypto firms now carry originator and beneficiary data, and transfers involving self-custody wallets above the applicable threshold require verification of wallet ownership. For a merchant, this manifests as customers paying from personal wallets being held for additional checks. That is not a reason to stop accepting crypto; it is a reason to understand the policy before your customers discover it the hard way.

Closely related and more consequential on a day-to-day basis: every serious provider screens incoming deposits against blockchain-analytics tools. A payment arriving from an address with exposure to a sanctioned entity or a mixing service gets frozen. The critical questions are who carries that loss, what the appeal path looks like, and what risk score triggers a hold. Most contracts assign the loss to the merchant by default. That clause is negotiable, and remarkably few merchants attempt to negotiate it.

The exit scenario. Coinbase Commerce shut down for merchants outside the United States and Singapore on 31 March 2026, with no extension offered. Affected businesses had to export their transaction history, move funds off the platform, and rebuild their checkout on a deadline they had no part in setting. Rather than assuming that scenario cannot happen to you, run three concrete checks: Can you export complete transaction history, including cost basis at the moment of receipt, in a format your accounting system actually ingests? Is your integration abstracted well enough that swapping providers is a configuration change rather than a ground-up rebuild? If the provider holds funds, are client assets segregated from operating capital, and can you verify that segregation independently? Running two providers in parallel is overkill for most merchants; keeping the system integration portable is not.

Matching the Provider to Your Business Vertical

Most mainstream crypto payment providers maintain prohibited-business lists covering gambling, forex, adult content, and a long tail of adjacent categories. Merchants typically discover this restriction several weeks into the underwriting process, after the relationship has been built around an assumption that proved false.

For iGaming operators, forex brokers, and other high-frequency businesses, the relevant vendor pool is considerably narrower, and the evaluation criteria shift accordingly. Throughput, payout automation, and deposit-withdrawal cycle handling matter far more than checkout polish. Specialists in this segment — CoinsPaid in Europe, or a crypto payment processor such as 0xProcessing, which works with gaming and trading platforms — underwrite and price these flows on different assumptions than a mainstream e-commerce gateway. Their systems are built around recurring deposits and withdrawals rather than one-off purchases.

The practical, if unglamorous, advice for any merchant entering this space: qualify providers on vertical acceptance first, before evaluating fees, integration depth, or supported assets. Phrase your due-diligence questions so the answers are directly comparable across vendors. A provider worth signing with will answer every question without significant resistance. The ones that deflect have, for free, told you something useful about where their limitations lie.

The comparison tables are not wrong; they answer the question that is easy to answer and will get you to a shortlist of three or four candidates perfectly well. What separates those finalists is operational policy, and operational policy only becomes visible if you ask for it in writing while you are still a prospect rather than a customer. After that, you are stuck with whatever the default was.