Stablecoins as a Payment Method for Dutch Businesses

Not Legal Tender, But Not Illegal Either

The first question a Dutch entrepreneur typically asks about accepting stablecoin payments is whether it is even allowed, and the honest answer is yes, with a qualification worth understanding properly rather than glossing over. Stablecoins are not wettig betaalmiddel, legal tender, in the Netherlands; only the euro carries that status. A Dutch business is under no legal obligation to accept a stablecoin as payment, and a customer cannot legally insist on paying with one. But nothing in Dutch law prohibits the two sides from contractually agreeing to it, and once they do, the payment obligation is genuinely fulfilled the moment the agreed stablecoin amount lands in the agreed wallet address, exactly as a bank transfer discharges a euro-denominated invoice.

The regulatory backdrop for 2026 sits inside MiCA, Regulation (EU) 2023/1114, which splits stablecoins into two categories. Electronic money tokens, EMTs, reference a single fiat currency, the euro or the dollar, and their issuer needs a credit institution or e-money institution licence, supervised in the Netherlands by DNB. Asset-referenced tokens, ARTs, reference multiple currencies, commodities, or a basket of assets, and face stricter requirements again. Crypto-asset service providers, CASPs, the payment processors and exchanges that actually move these tokens around, need their own AFM licence or a valid EU passport from another member state's regulator.

USDT, Tether's dollar-referenced stablecoin and still the most widely used stablecoin globally by circulation, technically falls under the EMT category since it references a single fiat currency, but Tether never sought the authorisation MiCA requires for that category. The practical consequence unfolded in stages rather than on a single date: EU exchanges began delisting USDT trading pairs through late 2024 and into 2025, Coinbase in December 2024, Crypto.com in January 2025, Binance and Kraken by the end of March 2025, ahead of MiCA's full application deadline of 1 July 2026, after which every MiCA-licensed venue in the EU had removed USDT trading for EEA customers entirely. By the time a Dutch business is reading this in the second half of 2026, USDT is simply not available through any regulated EU platform, and a payment setup built around it needs to migrate. Circle's USDC and EURC, both properly authorised EMTs issued through Circle's French-licensed entity, are the primary MiCA-compliant alternatives for business payments today.

Key takeaway: Three stablecoins a Dutch business can reasonably build a payment setup around in 2026: EURC, euro-referenced and MiCA-compliant; USDC, dollar-referenced and MiCA-compliant; and other properly authorised EMT issuers operating under an EU passport. One stablecoin to actively avoid for EU-regulated business payments: USDT, since no MiCA-licensed CASP in the EU can offer it to customers any longer, regardless of how widely it still circulates elsewhere.

Working with a properly licensed provider is what actually protects the business here, since it shifts the regulatory burden of customer verification and compliance onto the CASP rather than leaving it with the entrepreneur directly. Since digital payment regulation more broadly shapes how a Dutch business actually receives money day to day, PSD2 and open banking Netherlands covers the wider regulatory landscape stablecoin payments now sit alongside.

What Happens to Your BTW Return

The BTW treatment of accepting stablecoin payments is considerably cleaner than most Dutch entrepreneurs expect going in. The underlying sale of goods or services is subject to BTW exactly as it would be for a euro payment, at exactly the same applicable rate; what actually changes is purely a documentation requirement, not the tax logic itself.

The core rule is that BTW is calculated on the euro value of the transaction at the moment payment is received, and any later movement in the coin's own value against the euro simply does not touch that BTW obligation at all, since it has already crystallised. For a euro-referenced stablecoin like EURC, this calculation is close to trivial: 100 EURC at a genuine 1:1 peg equals 100 euros, and BTW at the applicable rate applies to that 100 euros. For a dollar-referenced stablecoin like USDC, the entrepreneur converts the received amount to euros at the exchange rate prevailing at the exact moment of receipt; if USDC trades at 0.93 euros that day, a payment of 100 USDC represents 93 euros for BTW purposes, not 100.

A second, separate rule governs what happens next, once the stablecoin actually gets converted into euros through a payment processor or an exchange. That conversion transaction is itself VAT-exempt, following directly from the Court of Justice of the EU's 2015 ruling in Hedqvist, case C-264/14, which established that exchanging cryptocurrency for fiat currency sits within the same VAT exemption that covers ordinary currency exchange. The practical result is that a Dutch business owes BTW once, on the original sale, and the subsequent conversion of whatever stablecoin it received into euros carries no separate BTW calculation of its own. It is worth being precise about scope here too: the Hedqvist exemption addresses the exchange transaction itself, and how cleanly it applies can depend on whether the token in question functions as a straightforward means of payment, as EMTs like EURC and USDC generally do, rather than as some more exotic asset-referenced structure, which is one more reason the EMT-versus-ART distinction covered above matters beyond pure MiCA licensing.

None of this works without proper documentation, though, and this is where the Belastingdienst's actual scrutiny lands. The exchange rate source used to convert a stablecoin amount into euros needs to be applied consistently and recorded alongside every transaction, not selected after the fact to produce a favourable number. A payment processor's own quoted rate at the transaction timestamp is generally the most defensible source, and a major exchange rate, Coinbase, Kraken, or Bitvavo, at that same timestamp works equally well. Switching sources transaction by transaction, or using a rate that cannot actually be verified later, is exactly the kind of gap a boekenonderzoek surfaces quickly. Since this documentation ultimately feeds the same quarterly cycle every other BTW-registered transaction does, when to file VAT Netherlands covers that filing rhythm in full.

The Bookkeeping Choice That Determines Everything

A Dutch BV that starts accepting stablecoin payments faces a single decision early on that determines almost all of the accounting and tax complexity that follows, and it is a decision most guides skip past entirely: does the business convert the received stablecoin to euros immediately, or does it hold the stablecoin on its own balance sheet for some period first?

For most Dutch businesses accepting stablecoin for the first time, immediate conversion is genuinely the correct starting point. It eliminates the balance sheet complexity entirely, removes any need to track exchange rate movements over time, and reduces the practical difference between a stablecoin payment and an ordinary bank transfer down to a single documentation note recording the rate used at receipt. Businesses only start needing the fuller accounting apparatus once they have a genuine reason to hold the asset, paying an overseas supplier directly in stablecoin, for instance, or deliberately treating it as a treasury position.

Watch out: A BV holding stablecoin as a treasury asset needs a consistent, documented accounting policy, generally at cost or the lower of cost and market value. If a stablecoin experiences even a brief de-peg, as USDC itself briefly did in March 2023, the lower-of-cost-or-market principle can require a year-end impairment write-down even where the peg fully recovered soon after. A de-peg the business never noticed at the time can surface later as an unreported write-down during a boekenonderzoek.

Since classifying an asset like this on the balance sheet is really a specific case of a much broader question, how to prepare a balance sheet covers how financial assets generally get structured for a Dutch BV.

DAC8 and Why Everything Just Got More Visible

Until fairly recently, a Dutch entrepreneur accepting crypto payments and not fully declaring them faced a genuinely limited detection risk. From 1 January 2026, that changed materially. DAC8, the EU's eighth directive on administrative cooperation in tax matters, requires crypto service providers operating in the Netherlands to collect customer and transaction data from that date, with the first formal reporting deadline to the Belastingdienst falling on 31 January 2027, covering the entire 2026 calendar year. The Dutch implementing legislation was enacted on 1 April 2026 with retroactive effect back to 1 January, so the data collection itself has already been running for months by the time most entrepreneurs even hear about the requirement.

What this means in practice is straightforward, and worth stating plainly. Every transaction processed through a MiCA-licensed CASP, every stablecoin payment received through a licensed Dutch payment processor, every conversion executed on a licensed exchange, now feeds into a dataset the Belastingdienst receives directly and cross-references against submitted BTW returns, VPB returns, and personal box 3 declarations. A business that declared 80,000 euros in revenue for a year where DAC8 data shows 120,000 euros in stablecoin receipts through a licensed provider has created an automatic discrepancy, and that discrepancy triggers a review without anyone having to go looking for it manually first.

The practical compliance message that follows from this is specific rather than merely cautionary. Any Dutch entrepreneur who has been accepting stablecoin payments and has not fully declared the euro equivalent, as BTW-taxable turnover, as VPB or IB profit, or, for personal holdings, in box 3, should make a voluntary correction now rather than waiting for a DAC8-triggered comparison to surface the gap first. The mechanisms for this are well established and considerably cheaper than the alternative: a BTW suppletieaangifte corrects a VAT underdeclaration, and an amended VPB or IB return corrects the profit side, and both, filed voluntarily and promptly, avoid the boete exposure that follows once the Belastingdienst finds the same gap first through its own data. Anyone accepting direct wallet-to-wallet stablecoin payments without a licensed CASP sitting in between should also remember that the Wwft cliëntenonderzoek obligation for unusually large transactions then sits entirely with the business itself, since there is no licensed intermediary to shoulder it. Since the timing of a voluntary correction relative to any Belastingdienst review changes the outcome considerably, boekenonderzoek Belastingdienst covers exactly how that audit process actually runs and where voluntary correction genuinely helps, and BTW suppletieaangifte covers the correction mechanism itself in full.

Setting It Up Practically

A Dutch BV that wants to accept stablecoin payments in 2026 needs four things genuinely in place before the very first transaction, and getting them right at the outset is considerably easier than retrofitting them after six months of unstructured stablecoin receipts that nobody documented consistently.

The first is a MiCA-compliant payment provider, an AFM-licensed CASP or one holding a valid passport from another EU regulator. The provider's actual licence status can be verified directly on the AFM's own CASP register, which is a five-minute check worth doing rather than relying on a provider's own marketing claims about compliance. The second is an explicit decision on conversion policy, made before the first payment arrives rather than reactively afterward: will the business convert immediately, hold temporarily, or hold strategically, and this decision should be written down as an actual accounting policy statement, since it determines both how every subsequent transaction gets recorded and what valuation rules apply once the year closes.

The third is an exchange rate source protocol, a single chosen source, the provider's own rate, a major exchange, or the European Central Bank reference rate for euro-denominated comparisons, applied consistently to every transaction and recorded alongside the amount and timestamp in the administration. This is precisely the record a boekenonderzoek will actually examine if the question ever arises. The fourth is an updated BTW invoice workflow: the invoice itself is always issued in euros, since the BTW amount is a euro figure regardless of what currency actually settles the payment, while the payment confirmation separately records the stablecoin amount received and its euro equivalent at the exchange rate used. Together, these two documents form the complete administration record for that single transaction, and most modern bookkeeping software with crypto transaction import, or a payment processor offering a euro-equivalent export file, handles this pairing automatically rather than requiring manual reconciliation every time. Since the invoice itself still needs to meet the same underlying format rules regardless of what currency the client ultimately pays in, e-invoicing Netherlands covers those requirements directly.

Get Your Stablecoin Payments Set Up Correctly From the Start

None of this needs to feel like a specialist crypto compliance project. For a business that converts every stablecoin payment to euros immediately, the whole picture reduces to little more than a documentation habit layered on top of an ordinary sale. The complexity genuinely only grows once a business chooses to hold the asset, and even then, the rules are specific and learnable rather than uncertain.

If you want help setting up a stablecoin payment workflow that keeps your BTW, bookkeeping, and DAC8 exposure genuinely clean from the first transaction, book a demo and we will walk through your specific setup. Our team can also help you incorporate your BV or get bookkeeping and payroll running correctly around whatever payment methods you actually accept.

FAQs

Is it legal to accept stablecoin payments in the Netherlands?

Yes. Stablecoins are not legal tender in the Netherlands, so no business is obligated to accept them, but nothing prohibits two parties from contractually agreeing to use one as a payment method, and doing so fulfils the underlying payment obligation once the funds arrive.

What is the difference between a stablecoin and regular cryptocurrency for tax purposes?

A stablecoin is designed to hold a stable value against a reference currency, which removes most of the price-volatility complexity a volatile asset like Bitcoin creates, but it remains a crypto-asset rather than fiat currency, so BTW documentation, balance sheet classification, and box 3 rules still apply exactly as they do to any other crypto-asset.

Does accepting stablecoin payment change my BTW obligations?

No, not in substance. The underlying sale of goods or services is taxed exactly as it would be for a euro payment, at the same rate, calculated on the euro value at the moment of receipt; what changes is the documentation needed to support that euro conversion.

Which stablecoins can a Dutch business use in 2026?

EURC and USDC, both issued by Circle and properly authorised as electronic money tokens under MiCA, are the primary compliant options, alongside any other stablecoin issued by a properly EMT or ART-authorised issuer holding a valid EU licence or passport.

Is USDT still usable for business payments in the Netherlands?

Not through any MiCA-licensed platform. Tether never obtained the EMT authorisation MiCA requires, and every regulated EU exchange had removed USDT trading pairs for EEA customers by the time MiCA's full application deadline arrived on 1 July 2026.

How do I record a stablecoin payment in my BV's bookkeeping?

If the payment is converted to euros immediately, it is booked as ordinary euro revenue with no crypto appearing on the balance sheet at all. If the stablecoin is held instead, it is recorded as a financial asset at its euro value on receipt, with gains or losses handled according to Dutch accounting and VPB rules once realised.

What is DAC8 and how does it affect stablecoin reporting?

DAC8 is an EU directive requiring licensed crypto service providers to collect and report customer transaction data to the Belastingdienst from 1 January 2026, with first reporting due 31 January 2027, giving tax authorities direct visibility into transactions that previously relied entirely on self-reporting.

Do I owe tax if I hold stablecoins in my BV without selling them?

Unrealised gains are not taxed in the Netherlands under the prudence principle; the asset stays on the books at cost or a lower market value until an actual sale or conversion realises a gain or loss, at which point it becomes taxable or deductible under VPB.

What is the box 3 treatment of stablecoins held by a DGA personally?

The Belastingdienst classifies stablecoins, including euro-referenced ones, as overige bezittingen in box 3, taxed at a 6.00% deemed return times the 36% box 3 rate, an effective 2.16% of the holding's value annually, even though a stable-value asset generates no actual return at all.

What is a MiCA-compliant payment provider?

It is a crypto-asset service provider holding an AFM licence in the Netherlands, or a valid passported licence from another EU regulator under MiCA, which shifts most of the customer verification and compliance burden for the transaction onto the provider rather than the business accepting payment.