How to get paid in crypto from US & EU clients (without the compliance headaches)

This is not tax or legal advice. Tax law is jurisdiction-specific and changes frequently. Use this as a framework, then confirm with a CPA or chartered accountant who knows digital assets before standardizing on any treatment.

Last updated: June 2026.

The two things that actually create headaches

When people say getting paid in crypto is a compliance nightmare, they almost always mean one of two things:

• The two-event tax problem. In most jurisdictions there are two potential taxable moments: (a) receiving crypto for your work is income, valued at its fiat equivalent on the receipt date; and (b) later disposing of that crypto — selling it, swapping it, or spending it — is a capital gains event measured against the value when you received it. People forget the second one exists.
• Records. If you can't show what you received, in what asset, on what date, at what fiat value, with a transaction hash, you can't file cleanly and you can't defend yourself in an audit.

Both are solvable, and the single biggest lever on both is getting paid in a stablecoin and invoicing in fiat. Here's why that collapses the headache: if you bill $5,000 and receive ~5,000 USDC, your income is ~$5,000, and because USDC holds its dollar peg, when you later convert it the capital gain is essentially zero. The two-event problem shrinks to one event with clean numbers.

How crypto income is taxed in the US

The US Internal Revenue Service treats cryptocurrency — including stablecoins — as property, not currency, under longstanding guidance (Notice 2014-21). Two consequences for someone invoicing US clients:

• Receipt is ordinary income. Crypto received for services is income at its fair-market value (in USD) on the day you receive it. A self-employed person reports it as business income (Schedule C) and it's subject to self-employment tax.
• Disposal is a capital event. When you later sell, swap, or spend that crypto, you have a capital gain or loss measured against the value when you received it. Hold a volatile asset and the gain can be large; hold a stablecoin and it's negligible.

The practical takeaway for US-facing freelancers and businesses: invoice in USD, take USDC, and you've turned a messy capital-gains tracking problem into a simple income figure.

How crypto income is taxed in the EU and UK

EU. Under the MiCA Regulation (2023/1114), fiat-referenced stablecoins like USDC are classified as e-money tokens, with the issuer rules effective from mid-2024 and crypto-asset service provider rules from the end of 2024. But MiCA governs asset classification and market conduct — the actual income and VAT treatment of a payment is set by each member state's corporate income tax and VAT rules. So an invoice paid in USDC to a freelancer in Germany, Portugal, or Estonia is taxed under that country's rules, and you should confirm locally. The constant across the bloc: the fiat-equivalent value at receipt is your starting point.

UK. HMRC treats crypto as property (exchange tokens). Crypto received for services is trading/self-employment income at its GBP-equivalent value on receipt — sole traders report on Self Assessment, companies through corporation tax. A later disposal is subject to Capital Gains Tax (rates in the 18%–24% band depending on your position), and income can fall in the 0%–45% range depending on your total. Since the 2024/25 tax year there's a dedicated crypto section in Self Assessment.

The 2026 change you can't ignore: CARF and automatic reporting

The biggest shift for anyone invoicing cross-border in crypto is automatic information exchange. The OECD's Crypto-Asset Reporting Framework (CARF) takes effect from 1 January 2026, and crypto-asset service providers are now required to collect and report user and transaction data to tax authorities, who cross-check it against your returns.

In the UK specifically, from 1 January 2026 platforms must report your personal and transaction details to HMRC — name, address, tax number, and full crypto activity — even where no gain arises, and failure to provide required details can itself trigger penalties.

What this means in plain terms: the era of they will never know is over. Tax authorities are receiving the data directly. The only sane strategy is to declare correctly and keep records that match what the platforms report. This is a reason to use compliant tooling, not avoid it.

The records you must keep (per payment)

For every crypto payment you receive, capture and store:

• Invoice number and client
• Asset and chain (e.g., USDC on Base)
• Amount received (in the crypto unit)
• Fiat-equivalent value at the moment of receipt (your income figure)
• Date and time of receipt
• Transaction hash (your immutable proof)
• Any fees paid

This is exactly the dataset that finance teams care about, and it's what a proper invoicing platform exports for you. Settlematic's reporting and exports produce revenue-by-month, aging, and per-payment detail with transaction hashes, and its crypto invoicing tax reporting guide covers VAT/GST handling — so the audit trail is generated as a byproduct of getting paid, not a quarterly scramble.

The cleanest setup for invoicing US & EU clients

• Invoice in the client's fiat (USD for US clients, EUR for EU clients) so the amount and your books are unambiguous. See fiat-quoted crypto payments explained.
• Accept USDC on a low-fee chain (Base or Polygon) to eliminate volatility between invoice and payment.
• Use a hosted payment page so the client pays without needing an account or a risky wallet-connect.
• Let the platform record the fiat value, date, and hash automatically.
• Export for your accountant monthly, and hand them a clean dataset that already matches CARF-reported data.
• Where you need fiat off-ramp, expect business verification (KYB) — that's normal and is what enables legally compliant invoicing.

For VAT specifically: stablecoin payments don't change whether VAT applies to your service — that's determined by what you sell and where your client is. They change how you record the consideration received. Keep the VAT logic in fiat.

Mistakes that turn into real headaches

• Pricing in volatile crypto. Bill in fiat. A $5,000 invoice priced in ETH can arrive worth $4,600 or $5,400 and ruins your accounting.
• No per-payment fiat value. I got 0.03 BTC is not a usable income record. You need the dollar/euro value on the receipt date.
• Assuming non-custodial means no tax. Holding your own keys changes nothing about your tax obligations. It only changes who controls the funds.
• Ignoring the disposal event. Even with stablecoins, log the disposal; with volatile assets, it can be a material gain or loss.
• Treating crypto income as invisible post-CARF. Platforms report it now. Declare it.

This article is general information, not tax, legal, or financial advice, and tax rules change. Engage a qualified, digital-asset-aware accountant for your situation.

Make your crypto invoices audit-ready by default. Start free on Settlematic — fiat-quoted invoices, USDC settlement, and exports your accountant will actually thank you for.