How to Choose a Crypto Payment Gateway: A Merchant’s…

Today, merchants can choose from a wide range of solutions for accepting cryptocurrency payments. Many gateways offer similar core features on the surface, from checkout tools and API integrations to automatic conversion and payouts.Yet, merchants may pay less attention to the less visible parts of the payment flow, including custody structure, fee calculation, compliance processes, settlement mechanics, and refund handling. These factors can directly affect risk, cost, and day-to-day payment operations. This guide provides a five-part framework for how to choose a crypto payment gateway by comparing criteria that merchants can verify before integration, rather than ranking individual providers.

1. Custody Model: Custodial vs Non-Custodial

When evaluating the custody model, the first factor to consider is where funds are held between receipt and payout. In a custodial model, the payment provider may hold or control assets for part of the transaction flow before the merchant withdraws, converts, or settles them. This can simplify treasury management because the provider handles more of the wallet infrastructure, address management, conversion, and payout process. The tradeoff is that the merchant takes counterparty risk during the period in which funds are held within the provider’s system.A non-custodial crypto payment gateway has a different structure. In it, funds can move directly to a wallet controlled by the merchant, which reduces reliance on the provider as a custodian. This model can be attractive for companies that want direct control of assets, even though it can shift more responsibility to the merchant for wallet security, key management, reconciliation, and conversion.When comparing custodial vs non-custodial crypto payment gateway models, merchants should map the entire payment path. It includes who controls the private keys, whether funds are pooled or segregated, when the merchant gains control, and what happens if a withdrawal is delayed.If a provider describes custody only in broad terms such as “secure storage” or “instant access,” merchants should ask for a precise flow from customer payment to merchant payout. So, the answer should identify where funds are held at each stage and who controls them.

2. Fee Transparency: Look Past the Headline Rate

Crypto payment gateway fees rarely consist of one number. A provider may advertise a low flat fee or merchant fee while other charges appear during conversion, withdrawal, or blockchain transfer. The most useful comparison is therefore the all-in cost for the merchant’s actual payment flow.Start with the processing margin or merchant fee charged when a payment is accepted. Then check the conversion spread if incoming cryptocurrency is automatically exchanged into a stablecoin or fiat currency. A small difference between the quoted market rate and the executed rate can matter more than the headline rate for merchants processing larger volumes. Next, review any withdrawal fee charged when funds leave the platform and the network or gas fee required for the blockchain transaction itself.These layers should be compared using a realistic transaction example. For instance, a merchant that accepts BTC but settles in USDT should ask what happens to a $1,000 payment from receipt through conversion and withdrawal. The provider should be able to show the processing fee, conversion rate or spread, withdrawal charge, and network fee separately.A headline rate is useful only if merchants know what it includes. If the provider cannot explain the difference between its advertised rate and the final amount received, the merchant cannot reliably estimate payment margins or compare providers on equal terms.

3. Compliance and Licensing: Verify Specific Claims

Crypto payment gateway compliance should be assessed through specific, verifiable information rather than broad statements about security or regulatory standards. The first step is to identify the legal entity providing the service and check whether it publishes the relevant MSB or VASP registration number where such registration applies.Registration should also be understood correctly. An MSB or VASP registration is not the same as a banking license, nor does it automatically authorize every service in every country. Merchants should confirm what the registration covers, which entity holds it, and whether the intended payment and settlement flow is available for their jurisdiction and business model.The product itself should also support compliance workflows. Relevant controls can include KYC or KYB during onboarding, AML procedures, sanctions screening, and on-chain transaction screening. For merchants evaluating MSB compliance for crypto payments, these controls matter because provider registration and transaction-level compliance are separate questions.Providers should be able to explain when screening occurs, what information a merchant must submit, and what can cause a transaction or account to require additional review. Statements such as “license pending” or “we follow best practices” do not provide sufficient information on their own. A merchant should request the legal entity name, registration details, applicable policies, and a description of the compliance process before integration.

4. Settlement Speed and Stablecoins

Settlement should be evaluated by the currency the merchant ultimately wants to hold. A business can keep the original token it receives, use auto-conversion into a stablecoin, or use a fiat off-ramp and receive funds in a bank account. Each route changes the merchant’s exposure to volatility, conversion cost, and payout timing.Keeping the original asset avoids an immediate conversion but leaves the merchant exposed to its price movement. Auto-conversion into USDT, USDC, or another supported stablecoin can make the received value easier to account for and reuse for crypto-denominated expenses. Stablecoin settlement in B2B flows can also be practical when suppliers, affiliates, or contractors already accept the same asset. Fiat settlement may fit companies whose accounting and treasury functions remain bank-based, although the off-ramp introduces another conversion and payout step.Merchants should distinguish payment detection from final settlement. A gateway may identify an incoming transaction within seconds, while final blockchain settlement depends on the asset, network, required confirmations, and network conditions. The same distinction applies to payouts: an “instant” internal conversion does not necessarily mean that fiat has reached a bank account. The settlement cycle should therefore be measured from customer payment through to the point at which the merchant can actually use or withdraw the funds.Blockchain payment and stablecoin rails can support 24/7 settlement for crypto-to-crypto flows, reducing dependence on bank opening hours. Fiat payouts, however, can still be affected by banking schedules and local payment rails.For example, PassimPay supports automatic conversion, processing fees starting at 0.5%, and transaction processing averaging about five seconds, while final settlement still depends on the selected flow and network. Merchants comparing settlement providers should ask for timings for the entire route they plan to use, rather than only the first transaction-status update.

5. Refund Handling

Blockchain payments generally do not include the built-in card-style chargeback mechanism merchants are familiar with from card acquiring. This is sometimes described as “no chargebacks,” but merchants still need a practical way to manage legitimate returns, cancellations, duplicate payments, or service issues. A crypto payment gateway for merchants should therefore provide a merchant-controlled refund flow.The merchant should remain in control of whether a refund is issued, while the provider should make the process clear. That means identifying the original payment, confirming the destination details, specifying the refund asset and network, and recording the transaction for reconciliation.Stablecoins can be useful here. If a customer paid an asset that later moved sharply in price, returning the same nominal crypto amount can create an unintended gain or loss for either side. A merchant using a USDT payment gateway may instead structure eligible refunds around a stablecoin amount, helping reduce volatility between payment and refund. The exact approach should be defined in the merchant’s refund policy before transactions begin.

Conclusion

A crypto payment gateway should be always evaluated as part of the merchant’s payment and treasury infrastructure. Custody determines where the counterparty risk is, fee transparency shows the real economics of the platform, while compliance and licensing establish which entity provides the service and what controls support the payment flow.Settlement currency, auto-conversion, fiat off-ramp options, and 24/7 stablecoin settlement affect treasury predictability, while merchant-controlled refund handling determines how exceptions are managed. So, before integration, merchants should ask providers for concrete, verifiable answers in each of these five areas rather than rely on broad claims or headline features.

Frequently Asked Questions

What is the difference between a custodial and a non-custodial crypto payment gateway?

In a custodial model the provider may hold or control assets for part of the flow before the merchant withdraws, converts or settles them, which simplifies treasury work but leaves the merchant carrying counterparty risk while funds sit with the provider. A non-custodial gateway moves funds directly to a merchant-controlled wallet, reducing that reliance but shifting responsibility for wallet security, key management and reconciliation onto the merchant.

Which fees should merchants compare when choosing a crypto payment gateway?

Four layers rather than one headline rate. Start with the processing margin charged when a payment is accepted, then the conversion spread if incoming crypto is exchanged into a stablecoin or fiat, then any withdrawal fee when funds leave the platform, and finally the network or gas fee for the blockchain transaction itself. Compare them against a realistic example, such as a $1,000 payment received in BTC and settled in USDT.

Do crypto payments have chargebacks?

Blockchain payments generally do not include the built-in card-style chargeback mechanism familiar from card acquiring. Merchants still need a practical way to handle legitimate returns, cancellations, duplicate payments and service issues, so the gateway should offer a merchant-controlled refund flow that identifies the original payment, confirms destination details, specifies the refund asset and network, and records the transaction for reconciliation.