Which crypto payment processor should your business use?

No processor is best for everyone; the right one for you follows from which coins your customers pay with, what you want to hold afterwards, what you pay in total, and how payments get into your site. If customers pay in USDT and you want a balance that keeps its dollar value without running a server, look for a hosted processor that converts payments to USDT and charges around 1%. If you need dollars or euros in a bank account, or want nobody holding your money at all, the shortlist changes.

What a crypto payment processor does for you

A crypto payment processor is a service that stands between your customer's wallet and your shop. Many of them call themselves payment gateways; for a seller, the two words mean the same thing.

When a customer pays, the processor does four jobs:

• Shows the bill. The customer sees the amount, the coin and the address to send it to.
• Watches the blockchain. The processor waits until the transfer arrives and the network confirms it.
• Tells your site. The order is marked as paid without anyone checking a wallet by hand.
• Credits your balance. The money waits there until you withdraw it.

You could post your own wallet address and skip the processor. Then those jobs are yours, and so are the awkward cases:

• Matching. Each incoming transfer has to be tied to the right order by hand.
• Short payments. A customer sends 99 USDT instead of 100, and you decide whether the order ships.
• Price moves. A coin you received yesterday can be worth less today, and selling it is your job.

A processor is what you pay to stop doing that by hand. If this is your first crypto checkout, start with how a business starts taking payments through a crypto gateway.

What separates one processor from another

Feature pages look alike from one processor to the next: many coins, fast payments, simple setup. In practice the choice comes down to a few questions, and the answers differ a lot more than the feature pages do.

Which coins and networks will your customers pay with?

A list of 300 coins looks reassuring, but what matters is whether the processor accepts the coins your customers already hold. Look at what customers ask to pay with, or ask them directly. A processor that takes the one coin they have beats one that takes a hundred they don't.

If the answer is USDT, a token built to hold the value of one US dollar, the next question is the network. USDT runs on several blockchains, called networks: TRON, Ethereum, BNB Chain and others. They differ in transfer fees and in how fast a payment arrives.

A customer who sends USDT on a network the invoice does not accept may find the payment stuck, and getting it back is not guaranteed. Check that the processor accepts the networks your customers use, and decide which USDT network to accept as a merchant before you go live.

What do you want to hold after the customer pays?

Depending on the processor and its settings, a payment leaves you with one of three things:

• The coin the customer sent. If it was bitcoin, your revenue moves with the bitcoin price until you sell: a $500 order can be worth $460 a week later, or $540.
• A stablecoin such as USDT. The balance keeps its dollar value, and you can pay suppliers or move it to an exchange when it suits you.
• Money in a bank account. The processor sells the crypto and sends dollars or euros to your bank. Accounting gets simpler, but you pay for the conversion, and the list narrows to processors that pay out to banks in your country.

If you set prices in dollars and pay your costs in dollars, keeping the volatile coin means betting part of your revenue on its price. Converting at the moment of payment removes that bet in one step. It is not the only way to protect crypto revenue from price swings.

Who holds the money between payment and withdrawal?

There are two set-ups, and they trade convenience for control:

• Hosted processor. The payment lands on the processor's balance, and you withdraw it to your wallet or bank. The processor handles conversion, refunds and reports; in return, it holds your money until you take it out.
• Self-hosted software. You run the payment software on your own server, and payments go straight to your own wallet. Nobody else holds your money, but the updates, the server bills and any conversion are on you.

With a hosted processor, the withdrawal terms decide how much the holding matters. Ask three things:

• How often you can withdraw. At any time, daily, or on a fixed schedule such as once a week.
• Whether there is a minimum. A minimum withdrawal keeps small amounts stuck on the balance until enough builds up.
• Whether withdrawals can run automatically. Then money leaves the balance for your wallet without anyone logging in.

For a seller without a developer, a hosted processor is the practical choice. Self-hosting suits a team that has someone to keep a server running and wants no third party between the customer and the wallet.

How does the processor check you and the money coming in?

Find out how the processor verifies who you are, and at what point: before your first payment or before your first withdrawal. What it asks for varies: some services accept an ID document, others want a full set of company papers.

The incoming money gets checked too. Crypto can arrive from a wallet tied to theft, fraud or sanctions, and a careful processor screens each payment against such addresses; this is called AML screening, from "anti-money laundering".

Ask what happens to a payment the screening flags: is it held before it reaches your balance, and how do you get it reviewed? Before you compare the answers, it helps to know the wider set of AML, KYC and wallet-screening controls for crypto payments.

Crypto payment processors worth comparing

The processors below are operating as of October 2026. Between them they cover every case above, from a USDT balance to dollars in a bank account to software you run yourself:

• CryptumPay. A hosted processor for sellers who want their balance in USDT: incoming payments are converted to USDT as soon as they are credited, so the balance never sits in a volatile coin. The price is 1% per successful payment, down to 0.5% at higher volumes, and the seller can pass the fee on to the customer. Withdrawals work at any time, with no minimum, by hand or automatically, to an address the seller sets. Suspicious funds are caught and held before they reach the balance. Every merchant passes an identity check before withdrawing, and an ID check may be enough without a pack of company documents.
• NOWPayments. A hosted processor with one of the longest coin lists: more than 300 cryptocurrencies. Pricing starts at 1%, with lower rates as monthly volume grows, and blockchain network fees come on top. If you already use it and are weighing a move, see which NOWPayments alternative to switch to.
• CoinGate. A hosted processor charging 1% per transaction on its standard plan, with custom rates for larger businesses. Automatic settlement runs weekly on the standard plan, withdrawals in crypto or to a SEPA bank account (the euro bank-transfer system) are free, and a manual conversion on the platform costs 1%.
• BitPay. A hosted processor built around bank settlement: daily payouts in US dollars, euros, pounds and four other currencies, or in crypto. The fee depends on monthly volume: 2% plus 25¢ per payment under $500,000, 1.5% plus 25¢ up to $1 million, 1% plus 25¢ above that, and more for high-risk industries.
• Stripe. A regular Stripe account can accept stablecoins as one more payment method. Customers pay in USDC, a dollar stablecoin, on networks such as Ethereum, Solana, Polygon and Base, and the seller receives local currency in the Stripe balance for 1.5% per payment. It is open to businesses in the US and, in private preview, in the European Union, Hong Kong, Mexico and Switzerland; USDT is not accepted, and one payment is capped at $10,000.
• BTCPay Server. Free open-source software that you run yourself or on a shared server. It charges 0%, payments go straight to your own wallet, and it is built around bitcoin.
• Exchange payment buttons. Binance Pay, Crypto.com Pay and Bybit Pay are run by crypto exchanges and built around their own apps, so they suit shops whose customers already keep money there. Before adding one, check what a merchant actually gets from Binance Pay, Crypto.com Pay or Bybit Pay.

Read against those questions, the list sorts itself:

• A USDT balance and no server to run: CryptumPay, which converts every payment to USDT on arrival.
• Many different coins: NOWPayments, with the longest coin list here.
• Euros or dollars in a bank account: CoinGate for free SEPA withdrawals, BitPay for daily bank payouts, Stripe if you are in a supported country and your customers hold USDC.
• Nobody holding your money: BTCPay Server, if someone on your team can keep the server running.

What a crypto payment processor really costs

The rate on the pricing page is one of up to four charges:

• Service fee. A percentage of each payment, sometimes with a fixed amount on top. This is the number processors advertise.
• Network fee. What the blockchain charges to move coins, paid by whoever sends them.
• Conversion. Turning the customer's coin into a stablecoin or into dollars costs a fee or a spread, the gap between the buying and the selling price. Some processors include it, others charge it separately.
• Withdrawal. Taking money out to your wallet or bank can be free, carry a fee, or require a minimum amount.

That is why the lowest rate does not always make the lowest bill. A 0.5% service fee followed by a paid conversion and a paid withdrawal can cost more than 1% with both included. Each part is laid out in how network fees, gateway fees and conversion costs add up.

What a month of sales costs at each processor

Take a shop that sells $10,000 a month in 200 orders of $50, and count the service fee alone:

• CryptumPay: 1%, or $100, and the seller can move that fee onto the customer's bill instead.
• NOWPayments: from 1%, or from $100, with network fees on top.
• CoinGate: 1%, or $100, plus 1% on any manual conversion made on the platform.
• Stripe: 1.5%, or $150, with conversion to local currency included.
• BitPay: 2% plus 25¢ per payment, or $200 + $50 = $250.
• BTCPay Server: $0 in fees, while the server and the time to run it are on you.

The fixed part of a fee weighs most on small orders. On a $10 order, 25¢ is already 2.5% before the percentage is added.

How a processor connects to your website

There are four ways to put a processor on a site, from no code to a full integration:

• Payment link or QR invoice. You create a bill in the processor's dashboard and send the link in a chat or an email. No code, and it fits invoices and small catalogues.
• Widget. You paste a short snippet into a page, and a pay button opens the processor's checkout.
• Plugin. If your store platform has a ready plugin for the processor, you install it and enter your keys.
• API. Your developer creates bills from your own code, and the processor sends your server a message when each one is paid.

The choice depends on who will do the work, not on the size of the shop. Without a developer, you can accept USDT through payment links and QR invoices without a full integration.

A plugin is the middle road, and it is only as good as its upkeep. Check that it supports the current version of your platform, and that it marks an order as paid only after the network confirms the transfer, not when the customer clicks "I've paid".

With a developer, the API decides how much trouble the integration will be. Four things to look for before you commit:

• A test environment. Your developer can run fake payments end to end before any real money moves.
• Signed notifications. The message that says "paid" carries a signature, so nobody can fake it to your server.
• Separate statuses for odd cases. Underpaid, overpaid and late payments come back as their own statuses, not as one silent "failed", so your site can tell the customer what to do next.
• Documentation a developer can follow. Every request and response is described, with examples.

Those four are the start. Refunds, limits and repeated notifications need checking too, and your developer can go through them in the full checklist for a crypto payment API before you integrate it.

How to switch from the processor you use now

Sometimes the comparison starts because your current processor stopped fitting. Whichever one you move to, the order of the move is the same:

1. Open and verify the new account first. Verification can take time, and the old checkout should stay on until the new one can pay out.
2. Run a real test payment. Send a small amount from an ordinary wallet and follow it to your balance and out to your own wallet.
3. Switch the checkout. Replace the links, the widget or the API keys, and keep the old account open for payments that arrive late.
4. Withdraw and export. Take out what is left on the old balance and download your transaction history for your accountant.

The short version

Start from your customers' coins and from what you want to hold afterwards; those two answers cut the list in half. Then compare the full cost of a month of sales, not the headline rate, and pick the way of connecting that your team can actually maintain.

Questions people ask next

Is there a crypto payment processor that's completely free?

Yes, in the sense that nobody takes a cut. Self-hosted software charges 0%, and so does taking payments straight to your own wallet address. The costs move elsewhere: a server, updates, matching payments to orders by hand and converting coins yourself.

Which processor makes sense when I take a lot of payments?

Look at how the price falls with volume and how withdrawals work at scale:

• CryptumPay. The price goes from 1% down to 0.5% at higher volumes, and withdrawals can run automatically with no minimum.
• BitPay. The fee drops to 1% plus 25¢ per payment once monthly volume reaches $1 million.
• CoinGate. Larger businesses get custom rates instead of the standard 1%.

Bring your real monthly figure to each, so the quote is for your volume and not the starting rate.

Will my customers pay extra when they pay in crypto?

Your customer's wallet pays the network fee for their own transfer. If they pay from an exchange account, the exchange may also take a withdrawal fee, which is how 99 USDT sometimes arrives instead of 100. At CryptumPay the seller can also pass the 1% service fee on to the customer, so it shows up on the customer's bill.