Fiat, Stablecoins or Crypto: How to Choose What You Settle In

Before your first crypto order lands, you have to answer a question most merchants answer by accident. What do you want to be holding afterwards?

That is the settlement decision, and it is not a question you can leave open. If you never touch the setting, the answer is USDC. Our own help centre says it plainly: unless otherwise specified, all processed orders are automatically settled in USDC. So the merchant who skips the screen has not deferred the decision. He has chosen to hold a dollar stablecoin, and he will find out at year-end.

Here is the short version, and the rest of the post is the reasoning. Most businesses should settle to fiat. Not because holding crypto is wrong, but because fiat settlement changes the least about how your finance team already works. Everything else needs a reason you can say out loud.

Setting this up for the first time? Open a merchant account and pick your settlement currency before your first order lands.

What settlement actually means here

Settlement, payout and withdrawal are three different things, and mixing them up makes every later conversation harder. We have a piece that separates the three if the vocabulary is new. For this post, settlement is the currency your CoinGate balance is credited in once a customer payment confirms. The shopper pays in whatever they picked. What you end up holding is your setting, not theirs.

Two clocks live in that sentence and they are easy to fuse. A crypto settlement lands in your balance as soon as the blockchain confirms the transaction, which is seconds on Lightning and minutes on most other networks. Getting that money into your bank is a separate step on a separate schedule, and it is the step our pricing page prices. Keep them apart and the rest of this is simple.

One thing to get straight early, because it is easy to read too much into it. Our pricing page states that the 1% exchange fee applies to manual conversions on the platform, and that automatic checkout conversions are excluded from it. That is a statement about one fee and the scope of that fee. It is worth reading it as exactly that and no further.

Where the setting actually lives, and why USDC wins by default

This is the part almost nobody gets right on the first read, and it is worth four minutes because it decides what you hold. Settlement currency is not one field on one screen. It resolves through three levels, and the most specific one wins.

1. Per order. If your integration sends a receive_currency value when it creates the order, that value decides it. Our documentation is explicit that an API value overrides whatever the dashboard says.
2. Per integration. Each API app and payment button carries its own currency settings, under Integrations in the dashboard. This is the level most merchants are actually configuring when they think they are setting an account-wide preference.
3. The account fallback chain. Under business settings you can set a primary fallback currency and up to three secondary ones, in priority order. We settle in the first currency on that list that is enabled and available.

Note the word fallback, because it was chosen deliberately. That list is not a default that overrides everything below it. It is what we reach for when the integration has nothing to say. And if the list is empty, or nothing on it can be used, settlement falls back to USDC.

Two practical consequences. First, an account whose business settings say EUR can still be settling every order in USDC, because the integration’s own currency wins and new integrations start on USDC. If your balance does not look like your settings, that is where to look. Second, the honest way to describe doing nothing is not that you postponed the decision. You took a dollar-stablecoin position, funded by revenue, without writing anything down. Our guide to configuring your settlement currency walks through both screens.

The default should be fiat, and here is why

The volatility argument against accepting crypto was always mostly an argument against holding it, which is something we have gone through before. Settle to fiat and the exposure ends at the point of sale. We lock the exchange rate at the moment of payment, and if you settle in EUR, GBP or USD the conversion happens automatically at that locked rate. Your bank speaks fiat, your ledger speaks fiat, your tax return speaks fiat. That alignment is worth more than most of the treasury upside a normal business will realistically capture.

The constraints are worth knowing before you commit to it.

The currency list is short. We settle fiat in USD, EUR and GBP only. If you bank in a currency outside those three, that is the first thing to check, because your own bank’s inbound conversion then becomes part of your cost and we have no control over it.

The rails split by currency, and so does the price. SEPA is a euro scheme, so a EUR withdrawal goes over SEPA and a USD or GBP withdrawal goes over SWIFT. That matters, because they are priced differently. SEPA and crypto withdrawals are free, with a 50 EUR minimum withdrawal amount. SWIFT costs 0.50% with a 50 EUR minimum fee, and those two numbers are not the same kind of number. A minimum fee means the percentage only overtakes the floor somewhere above 10,000 EUR, so every SWIFT withdrawal below that costs 50 EUR whatever its size. If you settle in USD or GBP, batch your withdrawals. Frequent small ones are the expensive habit.

The schedule is weekly, and faster is a plan question. Our pricing page lists automatic settlements as weekly on the Standard plan and “Weekly / on-request” on Enterprise, one of the two tiers it publishes, and its FAQ adds that faster or customised payout schedules can be arranged for Enterprise clients on request. We do not publish a settlement SLA or a guaranteed day. If your cash flow depends on money landing on a particular date, ask rather than assume.

When stablecoin settlement is the better answer

There are three situations where stablecoins genuinely beat fiat, and they are narrower than the general enthusiasm suggests.

The first is paying out in the same asset you take in. If you settle suppliers, affiliates or contractors in stablecoins, then converting to fiat and back again is two conversions doing the work of none. Worth being precise about the mechanism here, because it is a different product. Withdrawals move money to your own accounts. Paying a third party is a payout, and payouts are priced on their own line.

The second is banking friction. If your local rails are slow enough, or expensive enough, that a weekly SWIFT transfer becomes a planning problem, holding a dollar-denominated asset you can move at any hour is a practical answer rather than an ideological one.

The third is a stated policy. Not a feeling about the dollar. A written decision with a size and a review date attached to it.

What we can actually settle in is narrower than what exists in the market, and there is a reason for that. Following the introduction of MiCA in the EU we moved to USDC as our supported stablecoin and discontinued USDT. So the menu is USDC and EURC, and nothing else. USDC settles across seven networks, which is Ethereum, Solana, Base, Polygon, Binance Smart Chain, Arbitrum and Optimism. EURC settles on Ethereum only, and that is the constraint that catches euro-denominated businesses, because if your counterparty wants EURC somewhere cheaper to move, that is not currently on the table. If you are still choosing, which stablecoins your business should accept covers the selection side of it.

When holding crypto is a treasury decision, not a payments one

Crypto settlement is available in BTC, LTC, ETH, BCH, DOGE and SOL. There is also a separate mode that skips conversion altogether and keeps the coins your customers paid with, rather than converting them into one asset you picked.

Something worth noticing in that list. The assets you can settle into and the assets a shopper can pay with are two different lists. BCH can be settled into but is not something a shopper can pay you with, while XRP, TRX, BNB and POL work the other way around. Do not assume symmetry. Check both sides against what you actually need.

More importantly, settling to BTC is not a payments configuration. It is a treasury position that happens to be funded by your revenue, which is an uncomfortable way to build one, because the size of the position ends up set by how well you sold last month rather than by anything you decided. If you are going to do it, do it the way you would do any other allocation, with a cap and a review date. Our piece on how crypto treasury management works is a better starting point than the settlement screen.

Mixed settlement, and what it costs

You do not have to choose one. A common and sensible pattern is fiat for everything that pays salaries and suppliers, with a fixed share going into a stablecoin or a crypto asset for a purpose you can name.

The mechanism for that is worth stating, because the obvious guess is wrong. The account fallback list is a priority order, not a split. It does not send 20% of your revenue to the second entry. If you want two settlement currencies running at once, you run them on separate integrations, each with its own currency settings, and you route orders accordingly.

The cost of that is not financial, it is operational. Every currency you settle into is another balance to reconcile, another rate to record, another line your accountant asks about at year-end. Two settlement currencies is fine. Five is a job.

The accounting consequence, which is the part people find late

This is the bit that gets discovered in month nine, so take it seriously now. Treatment varies by jurisdiction and none of this is tax advice, but the shape of the work changes with each choice, and the shape is what you can plan around. Our guide to accounting for crypto payments goes deeper than we can here.

Fiat settlement is the boring one, which is rather the point. One conversion happens at the point of sale, you book a fiat amount, and there is no crypto sitting on your balance sheet waiting to be revalued.

Stablecoin settlement looks like cash and is not. It tracks a currency, but it is an asset in your accounts rather than a bank balance, so it gets recorded at a value, reconciled, and quite possibly treated as disposed of when you spend it. Ask your accountant how they want it carried before you accumulate six months of the stuff.

Crypto settlement is the heaviest. Every receipt has a value at the moment it arrives, and every spend or conversion afterwards is a disposal with a gain or a loss attached. That is manageable with good records and painful without them.

Which is the real reason the default recommendation is fiat. That is not a view on crypto. It is a view on how much bookkeeping you want to buy with a setting you will change twice. And it is worth noticing that the platform default, USDC, sits in the middle row rather than the easy one.

Frequently asked questions

What currencies can I settle in?

Fiat in USD, EUR and GBP. Stablecoins in USDC and EURC, with USDC available across Ethereum, Solana, Base, Polygon, Binance Smart Chain, Arbitrum and Optimism, and EURC on Ethereum only. Crypto settlement is also available in BTC, LTC, ETH, BCH, DOGE and SOL.

What happens if I never choose one?

You settle in USDC. Unless something more specific is set, either on the order through the API or on the integration itself, orders settle in USDC by default. That is a real position in a dollar stablecoin, so it is worth making it on purpose or changing it.

How often do settlements happen?

Your balance is credited as each payment confirms. Moving it out is the part that runs on a schedule, and our pricing page lists automatic settlements as weekly on Standard and “Weekly / on-request” on Enterprise, with faster or customised schedules arranged for Enterprise clients on request. We do not publish a guaranteed settlement window, so treat weekly as your planning assumption unless you have agreed something else with us.

Does converting crypto to fiat cost extra?

Our pricing page states that the 1% exchange fee applies to manual conversions on the platform and that automatic checkout conversions are excluded from it. Withdrawal costs are a separate line, with SEPA and crypto withdrawals free on a 50 EUR minimum withdrawal amount, and SWIFT at 0.50% with a 50 EUR minimum fee.

Can I settle into more than one currency?

Yes, and splitting is a reasonable way to fund a specific obligation without taking a position with your entire revenue. You do it with separate integrations rather than by splitting a percentage, because the account-level list is a priority order and not a split. The cost is reconciliation. Each additional settlement currency is another balance and another set of rates your finance team has to account for.

I am just starting out. What should I pick?

Fiat, in whichever of USD, EUR or GBP your bank account already uses. Revisit it once you have a concrete reason, such as paying suppliers in stablecoins or a treasury policy someone has actually written down. Changing later is a setting, not a migration.

The bottom line

Settlement is a small screen with a long tail. Fiat is the right answer for most businesses because it keeps one currency in your ledger and nothing to revalue at year-end. Stablecoins earn their place when you are paying out in the same asset or working around slow banking. Crypto settlement is a treasury decision wearing a payments costume, and it deserves to be argued for on those terms. The one answer nobody should be happy with is the one that arrives by leaving the screen alone.

Whatever you choose, how the payment reaches you in the first place is a separate topic, and we go through those mechanics in a companion piece on where crypto checkouts lose orders.

Thinking it is time to make this choice on purpose rather than inherit it? Start with us.