Coingate

Accept crypto with CoinGate

Accept crypto with confidence using everything you need in one platform.

Crypto Payments

Crypto Payment Gateway Fees: What You Actually Pay

This post walks through the five events where crypto payment gateway fees land, gives our published rates, and works through a realistic month so you can copy the arithmetic.
Crypto Payment Gateway Fees: What You Actually Pay
Last updated: September 2, 2026 13 min read
VB
Vilius Barbaravičius

A provider quotes one percent. Six weeks later your finance lead asks why the number that landed in the bank does not match the number on the order.

Nothing was hidden. There are simply several different fees that apply at several different moments, and “one percent” only describes the first of them. Some of the others may not apply to you at all, which is exactly why nobody mentions them upfront.

This post walks through the five events where crypto payment gateway fees land, gives our published rates, and works through a realistic month so you can copy the arithmetic.


Want to model your own numbers? Our rates are published, and you can open an account and run a month through it.


The five places a fee can appear

Whatever provider you use, the cost of accepting crypto shows up in five distinct events:

  • Processing, when your customer pays.
  • Conversion, when the crypto becomes something else.
  • Payout or withdrawal, when money leaves the platform.
  • Refund, when money goes back.
  • Network, charged by the blockchain rather than by anyone you have a contract with.

Take them one at a time and the mismatch your finance lead spotted usually explains itself in about ten minutes.

1. Processing, when the customer pays

This is the headline number and the one every provider leads with. It is a percentage of the order value, taken when the payment confirms.

On our Standard plan it is 1% per transaction, with no monthly fee. Enterprise pricing is custom and based on volume, so if you are doing serious numbers the published rate is a ceiling rather than a price.

One thing about processing fees is worth understanding regardless of who you use. The percentage is calculated on the order amount you set, not on what happens to the money afterwards. Whether you hold the crypto, convert it, or withdraw it next Tuesday changes your other lines, not this one.

2. Conversion, when crypto becomes something else

Your customer pays in Bitcoin. You want euros. Something has to happen in between, and where that something sits in the fee stack varies by provider.

On our side there are two different situations and they are priced differently.

Automatic conversion at checkout is what happens when you have set a receive currency and orders arrive in it. The rate is locked at the moment of payment, which is the whole point of it, and our 1% currency exchange fee does not apply to it.

Manual conversion is when you already hold a balance in one currency and decide to move it into another. That is where the 1% currency exchange fee applies. Our pricing page is explicit about the split: the 1% applies to manual conversions on the platform, and automatic checkout conversions are excluded from it.

The practical lesson is to set your receive currency correctly at the start rather than accumulating crypto and converting it in batches later. Most of our merchants have landed there already. In the first half of 2026, 75.4% of orders were settled to fiat and only 24.6% in crypto, with EUR the leading settlement currency at 66.2%. The full numbers are in our H1 2026 crypto payments data report.

Our guide to instant crypto-to-fiat conversion covers what actually happens in that step. And settlement versus payout versus withdrawal is worth reading if those three words currently mean the same thing to you. They do not, and the fees differ.

3. Payouts and withdrawals, when money leaves

Here is where most fee models get more detailed, and where “one percent” stops covering it.

There is a real distinction between withdrawing your own balance and sending a payout to someone else, and they are priced separately. On our Standard plan:

What you are doingStandard rateMinimum
Crypto withdrawalFree50 EUR minimum withdrawal amount
SEPA withdrawalFree50 EUR minimum withdrawal amount
SWIFT withdrawal0.50%50 EUR minimum fee
Crypto payout0.50 EUR + 0.5%
Crypto payout with conversion0.50 EUR + 1.5%
DepositsFree

Read the minimum column carefully, because those two “50 EUR” entries mean opposite things. On crypto and SEPA withdrawals, 50 EUR is the smallest amount you are allowed to withdraw. On SWIFT it is the smallest fee you will be charged, so the 0.50% only starts to bite above 10,000 EUR. Below that you pay 50 EUR whatever the transfer size.

Two observations that matter more than the numbers.

If you are a European business settling to EUR, your withdrawal cost is zero. SEPA withdrawals are free on Standard. That is the single biggest reason the total cost of accepting crypto is often lower than people expect when they first model it.

If you send money out to other people, look at the payout lines rather than the withdrawal lines. Paying affiliates, contractors, suppliers or sellers is a payout, and the percentage triples on the conversion variant while the flat 0.50 EUR stays the same. Our stablecoin payouts guide and the post on marketplace and platform payouts both cover the operational side of that.

4. Refunds, the line nobody models

Almost nobody includes refunds in their first cost estimate, and almost everybody issues some.

Ours are 0.25 EUR + 0.1% on Standard, and the 0.1% is conditional. Our pricing page attaches it to a currency mismatch: it applies only when the currency being refunded differs from the currency the refund is issued in. Refund in the same currency and you are paying 0.25 EUR.

The fee itself is small. What is worth planning for is the process, because a crypto refund does not work like a card refund. There is no original payment method to reverse into, so you need the customer’s wallet address and network before you can send anything. Our post on how crypto refunds actually work for merchants covers what that means for your support team.

Note also that when a customer’s payment arrives after the checkout page has expired, they are offered a refund of their own, and very small amounts cannot be returned at all. The floor is set per currency and per network rather than as one figure, because the cost of sending the transaction has to come out of the amount being returned. Below it there is nothing practical to send back.

5. Network fees, and who pays them

This is the one fee nobody in the transaction controls.

A blockchain charges for including a transaction, and that cost is paid by whoever sends it. When your customer pays you, your customer is the sender, so the network fee comes out of their wallet on top of the amount they are sending you. When you send a payout, you are the sender, so it lands on your side.

The size varies enormously by network, which is why the choice of which networks to enable is a cost decision as much as a coverage decision. A stablecoin transfer on a low-cost network and the same transfer on a congested one are not remotely comparable. Our post on mitigating high transaction fees with layer-2 solutions goes into that, and the current network options per currency are listed on our supported currencies page.

There is a second-order effect worth knowing. Because your customer pays the network fee out of their own wallet, a high fee makes them likelier to send slightly less than the invoiced amount. Which brings us to the setting most merchants have never opened.

The shortfall you agree to absorb

Crypto payments are pushed from the customer’s wallet, so the amount can arrive slightly short. You control how much of a shortfall you are willing to absorb, using a setting called Underpaid Cover. Its value can be set anywhere between 0% and 10%, and it is set for each merchant product separately, so your API integration, your payment button and your POS each carry their own threshold.

One condition is easy to miss. A short payment is only marked as paid automatically if it also arrives inside the payment window. Short and late is not covered, whatever your threshold says.

There is no correct number here. Size it against your average order value and against what a support ticket costs you to resolve. On a 20 EUR order a 3% tolerance is 60 cents and the ticket costs more than the shortfall. On a 2,000 EUR order the same percentage is 60 EUR and the arithmetic reverses. Set it per product and revisit it when your order mix changes.

Our published rates, as of 2 September 2026

FeeStandardEnterprise
Monthly feesNo monthly feesNo monthly fees
Payment processing fee1%Custom, volume-based
Crypto payouts0.50 EUR + 0.5%Custom, lower fees
Crypto payouts with conversion0.50 EUR + 1.5%Custom, lower fees
Withdrawals (crypto)Free, 50 EUR minimum withdrawal amountFree
Withdrawals (SEPA)Free, 50 EUR minimum withdrawal amountFree
Withdrawals (SWIFT)0.50%, 50 EUR minimum feeCustom, lower fees
Currency exchange1%, manual conversions onlyCustom, lower fees
Refunds0.25 EUR + 0.1%Custom, lower fees
DepositsFreeFree
Automatic settlementsWeeklyWeekly or on request

Two conditions travel with that table and are easy to lose when it gets copied into a spreadsheet. The 1% exchange fee applies to manual conversions on the platform and not to automatic checkout conversions. The 0.1% on refunds applies only when the refunded currency differs from the currency used to issue the refund. There are no setup or integration fees.

Rates as published on our pricing page on the date above. Pricing pages change, so treat that page as the source of truth rather than this table.

A worked month

Numbers in the abstract are easy to nod at and hard to use. So here is a hosting business, which is a segment we see a lot of.

The setup. 400 paid orders a month, average order value 60 EUR, so 24,000 EUR gross. Pricing in EUR, receiving EUR, withdrawing to a SEPA account. Two refunds in the month. Underpaid Cover set at 2%.

  • Processing. 1% of 24,000 EUR = 240.00 EUR.
  • Conversion. Nothing. Orders are settled into EUR automatically, and there are no manual conversions because no crypto balance is being held and moved later.
  • Withdrawal. Nothing. SEPA withdrawals are free on Standard, and 24,000 EUR is comfortably above the 50 EUR minimum.
  • Refunds. Two refunds of 60 EUR each, going back to the customer in crypto rather than in the EUR the order was priced in. Per refund, 0.25 EUR + 0.1% of 60 EUR = 0.31 EUR. Two of them = 0.62 EUR.
  • Payouts. None. This business is not paying anyone out, it is only receiving.
  • Network fees. Nothing on your side. Every one of those 400 customers paid their own network fee when they sent the transaction.
  • Shortfall cover. Say eight of the 400 orders arrive around 1% short and are covered. Eight orders at 60 EUR, roughly 0.60 EUR each = 4.80 EUR absorbed. Not a fee anyone charges you, but money you agreed not to collect, so it belongs in the same column.

Total cost of accepting crypto that month: about 245.42 EUR on 24,000 EUR gross, or roughly 1.02%.

The headline rate was 1%. The real number came out at 1.02%, and the gap is refunds and covered shortfalls rather than anything unexpected. Change one variable, though, and the picture moves. Swap the SEPA withdrawal for SWIFT and you add 120 EUR, which takes the month to 1.52%. Add fifty affiliate payouts of 20 EUR each with conversion and you add 40 EUR. Hold the crypto for a quarter and convert it manually and you add 1% of whatever you convert.

That is the point. The model is not the rate. The model is the rate plus the specific things your business does.


Ready to put real numbers through it? Create a CoinGate account and settle your first month to EUR.


The costs that are not fees

Worth naming, because they are usually larger than the fees and they never appear in a comparison table.

Integration time. A plugin install on an existing platform is short. Andrius Petkus, the CCO of hosting provider Bacloud, put their integration at 15 to 20 minutes, and told us separately that a module already existed for the service management solution they use. A custom API build is a different order of magnitude. Our Bacloud case study has the rest of that account.

Reconciliation effort. This is the real one. Get it wrong and it becomes a monthly manual task. Friedrich Kräft, CEO of PlainProxies, described what it looked like before they had fiat settlement:

Without fiat settlement, every single crypto transaction had to be manually tracked against the volatile exchange rate at the time of payment.

What that used to take, in his own words, was “up to 10 extra hours of tedious manual work each month”. At any sensible hourly rate that dwarfs the processing fee. Our guide to crypto payment reconciliation is about avoiding that specific cost.

Support load. Underpayments, late payments and refunds all generate tickets. Small volume, but it is not zero.

The cost of the payment you did not take. Harder to measure and often the biggest figure on the page. If card declines are turning customers away, the relevant comparison is not one percent against a card rate, it is one percent against zero revenue. Our post on payment decline rates covers that side, and crypto versus card payments gives the honest comparison in both directions.

Nine questions to ask any provider about pricing

Useful whoever you end up with:

  1. Is the processing percentage charged on the order amount or on the amount received?
  2. Is automatic settlement into my currency included in the processing fee, or priced separately?
  3. What does it cost to withdraw to my bank, on the rails I actually use?
  4. Are payouts to third parties priced differently from withdrawals of my own balance?
  5. What does a refund cost, and what does a partial refund cost?
  6. Who pays the network fee on an incoming payment, and on an outgoing one?
  7. Is there a shortfall tolerance setting, and what happens to an order that is short and late?
  8. Are there monthly fees, minimums or volume commitments?
  9. How often is settlement, and can that change?

Any provider that answers all nine without hesitation is one you can model properly. Our B2B buyer’s checklist for choosing a crypto payment gateway covers the rest of the evaluation, and the CFO’s guide covers what to bring to a finance conversation.

Closing

Your finance lead was right to ask. The number in the bank and the number on the order are not the same number, and the difference is not one thing, it is five.

Processing is the fee you were quoted. Conversion depends on whether you set your receive currency properly at the start. Withdrawals may cost you nothing at all if you are European and settling to EUR. Refunds are cheap but real. Network fees are your customer’s problem on the way in and yours on the way out.

Model those five against what your business actually does and the arithmetic comes out the same at both ends.

Want to see where your own numbers land? Our pricing is published, or you can start with us and run a month through it.

VB
Vilius Barbaravičius Posted: September 2, 2026
Share article

Accept crypto with CoinGate

Accept crypto with confidence using everything you need in one platform.