A freelance developer in Berlin sends an invoice to a client in Buenos Aires. The wire transfer costs €35 and takes four business days. The client's Argentine peso account is frozen for FX review for another two. Eleven days after the work is delivered, the developer finally gets paid — minus €35 in fees and a 4% currency conversion spread.
The same invoice settled in USDC on Base finalizes in eight seconds and costs €0.003 in gas. The developer paste a crypto payment link into the email, the client opens MetaMask, confirms, and the funds are in the developer's wallet before the email reply is even sent.
This is the part most "should I accept crypto" articles miss: for cross-border B2B, freelance work, and any business with international customers, accepting crypto in 2026 isn't an ideological statement — it's faster and cheaper rails. This guide walks through exactly how to set it up, which assets to accept, which chains to use, and the regulatory landscape after MiCA's full rollout.
Key Takeaways
- Stablecoins beat volatile crypto for business payments — USDC on Base or Polygon settles in seconds, costs under €0.01, and removes price volatility risk
- You don't need a smart contract — hosted payment platforms generate a crypto payment link the same way they generate a Stripe link
- EU businesses are fully covered by MiCA in 2026 — accepting crypto for goods and services is legal across all 27 member states without a crypto license
- Gas fees on Base/Polygon are negligible (<€0.01); Ethereum mainnet costs €2–10 per transfer and is not worth using for payments under €500
- Conversion to EUR is optional — many businesses hold USDC as a working-capital alternative and convert only when needed
Why Businesses Are Adding Crypto Payments in 2026
Three things changed between 2022 and 2026 that flipped crypto payments from "speculative novelty" to "boring infrastructure" for international businesses.
In 2022, accepting Bitcoin meant accepting a 5–15% daily price swing. By 2026, USDC, USDT, and EURC together process over $200B in monthly settlement volume — pegged 1:1 to the dollar or euro, with reserves audited monthly. A €100 invoice paid in USDC is worth €100 when it confirms, and €100 when you withdraw it next week. The pricing risk that killed crypto-payments-for-merchants in the last cycle is gone.
Bitcoin and Ethereum mainnet were always too expensive for payments — sending €50 cost €5–10 in fees. The migration to Layer-2 networks like Base (Coinbase), Polygon, Arbitrum, and Optimism dropped per-transaction costs to fractions of a cent while keeping the same security guarantees. In 2026, the median USDC transfer on Base costs €0.003 and confirms in 2 seconds.
Three years ago, accepting crypto meant deploying a smart contract, running a node, or integrating with a complex web3 SDK. In 2026, you generate a crypto payment link the same way you generate a Stripe payment link — paste your wallet address once, share the link, and the platform handles wallet detection, on-chain confirmation, conversion to fiat, and customer receipts. The technical complexity sits inside the platform, not on your team.
Which Crypto Should You Actually Accept?
For most businesses, the answer is "USDC, and maybe one or two others." Here's the decision framework.
USDC is the obvious starting point in 2026. It's regulated under MiCA in the EU, issued by Circle (a US-regulated payment institution), pegged 1:1 to USD, and trades at par with EUR/USDC pairs at sub-1% spreads. Coinbase, Kraken, Binance, and most European exchanges support it natively. Customers who hold any USD-stable assets typically hold USDC.
Chain choice: Base for US/global customers (Coinbase's home chain, deepest USDC liquidity), Polygon for cost-sensitive use cases (slightly lower fees, broader DeFi integration). Avoid USDC on Ethereum mainnet — same asset, 1000× the gas cost.
USDT (Tether) has higher volume than USDC globally and is the dominant stablecoin in Latin America, Southeast Asia, and parts of Eastern Europe. If your customers are in those markets, supporting USDT alongside USDC roughly doubles your addressable crypto-paying audience. The trade-off is USDT's reserve attestations are less rigorous than Circle's, so some risk-averse businesses skip it.
If your customer base specifically *wants* to spend BTC — common in SaaS targeting crypto businesses, online education in crypto trading, or VPN/privacy services — accept Bitcoin via Lightning Network. Lightning settles in milliseconds with near-zero fees and is the only practical way to use BTC for payments under €1000. On-chain Bitcoin is too slow and expensive for everyday payments.
Volatile assets like ETH and SOL fluctuate too much to be useful for most invoices. Unless you have a specific business reason (NFT marketplace, DeFi tooling, etc.), keep your accepted assets short. Every additional currency adds operational complexity for minimal incremental revenue.
The Three Setup Paths
There are three meaningful ways to start accepting crypto. Pick based on where you are today.
This is the path 90% of small-to-medium businesses should take. You sign up for a payment platform with crypto support (PayRequest, Coinbase Commerce, BitPay), paste your wallet address into the dashboard once, and generate a payment link or invoice the same way you'd generate a Stripe link.
The customer clicks, picks USDC or another supported asset, pays from MetaMask or Coinbase Wallet, and you receive a webhook + dashboard confirmation when the transaction finalizes on-chain. The platform handles QR codes, mobile wallet deep-linking, EUR price quotes, and confirmation thresholds.
With PayRequest, crypto sits alongside Stripe, Mollie, and PayPal on the same checkout — the customer picks the method that suits them, and the funds settle to whichever account matches.
If you only get a handful of crypto requests per month, you can skip the platform entirely. Generate a receiving address in MetaMask or Coinbase, send it to the customer via email, and reconcile transactions manually by checking your wallet history.
The downside: no automatic invoice marking, no customer receipt, no fiat quote (the customer has to figure out the USDC amount themselves), and no protection against the customer paying late or sending the wrong amount. Workable for one-off freelance gigs, painful at any real volume.
If you're building a crypto-native product (DEX, NFT marketplace, on-chain SaaS), you'll deploy a smart contract that handles the payment logic — escrow, subscriptions, automatic splits, royalties. This is the most flexible path but requires Solidity knowledge, security auditing, and ongoing protocol fee management.
For 99% of businesses, paths 1 or 2 are enough. Smart contracts are infrastructure you build only when the off-the-shelf option doesn't fit.
What About Fiat Conversion?
You have three options for what to do with crypto once you receive it.
Set your wallet provider (Coinbase Commerce, BitPay, Mollie's crypto rail) to immediately swap incoming USDC into EUR and deposit to your bank account. The funds hit your account in 1–2 business days, the same as a SEPA transfer. The cost is the spread on the swap — typically 0.5–1% on USDC/EUR. Use this if you treat crypto as just another payment rail and your books are in EUR.
Many businesses in 2026 hold a portion of their treasury in USDC. It earns 3–5% APY on regulated platforms like Coinbase or Aave, settles globally in seconds, and serves as an FX-neutral reserve when you have international suppliers. The downside is non-trivial tax accounting (every USDC transaction is technically a taxable event in some jurisdictions). Talk to your accountant before holding more than 5% of treasury in stablecoins.
The pragmatic default: convert 80% to EUR on receipt for daily operations, hold 20% in USDC for supplier payments and yield. This minimizes tax complexity while keeping the operational benefits.
The EU Regulatory Landscape: MiCA in 2026
If you're an EU business, the regulatory picture is simpler in 2026 than it was in 2024. The Markets in Crypto-Assets regulation (MiCA) is fully in force, and it draws a clear line:
Crypto service providers (exchanges, custodians, brokers) need MiCA authorization. Businesses that accept crypto as payment do not. You're a regular business that gets paid in a crypto asset — the same legal status as a business that gets paid in foreign currency.
What you do need to handle:
- Income reporting in EUR: report crypto receipts as income at the EUR-equivalent value on the date of receipt, using a verifiable exchange rate (typically a major exchange like Coinbase or Kraken at the timestamp)
- VAT/BTW treatment: crypto payments are treated as the consideration for the underlying good or service — apply your normal VAT rate as if you were paid in EUR
- DAC8 reporting (from 2026): crypto asset service providers report transactions above €1,000 to your home tax authority, so your crypto revenue will show up on your tax filings whether you list it or not — make sure your bookkeeping matches
The US has a more fragmented picture (state-by-state money transmission laws, IRS treating every transaction as a taxable event), and other jurisdictions vary widely. Outside the EU, talk to a local tax advisor before going live.
A Practical First-Week Setup
If you want to start accepting crypto payments by the end of next week, here's the minimum path:
- Day 1: Open a Coinbase account (or MetaMask + Coinbase combo). Verify your business identity.
- Day 2: Sign up for PayRequest or another payment platform with crypto support. Connect your Stripe account if you have one — keeps fiat and crypto on the same dashboard.
- Day 3: Paste your Coinbase USDC receiving address (Base network) into the crypto payment settings. Generate a test payment link for €10.
- Day 4: Pay the test link yourself from a personal wallet. Verify the confirmation arrives in the dashboard and the funds land in Coinbase.
- Day 5: Add the crypto checkout option to your normal payment flow. Update your invoice template to mention "Pay in USDC supported" as a footer line.
- Ongoing: Each month, review the conversion-to-EUR percentage and decide whether to hold more or less stablecoin reserve.
That's it. No smart contracts, no node infrastructure, no Solidity audits. The complexity is contained in the platform; your team just sends links.
When NOT to Accept Crypto
A few situations where adding crypto is more trouble than it's worth in 2026:
- B2C retail under €50 average ticket: the payment-method friction (wallet setup, gas calculations, network choice) is too high relative to the order value
- Highly regulated industries without explicit crypto guidance: healthcare, regulated finance, gambling — wait for your regulator's position before going live
- No international customers: if 100% of your revenue is domestic and SEPA already works fine, crypto adds operational complexity without revenue upside
- Cash-flow-sensitive business with strict EUR reporting: the 1–2 day conversion lag and exchange-rate variability may complicate your forecasting
For everyone else — B2B services, freelance work, SaaS, international e-commerce, cross-border consulting, online education — crypto in 2026 is faster, cheaper, and globally accessible compared to the legacy alternatives.
How PayRequest Handles Crypto Payments
PayRequest treats crypto as a first-class payment method alongside Stripe, Mollie, and PayPal. You generate a payment link, the customer sees their preferred method (card, iDEAL, USDC on Base), they pay, and the funds settle to the matching account.
What's included:
- USDC on Base as the default crypto rail (lowest fees, fastest confirmations)
- Automatic EUR price quoting at payment time, locked for 10 minutes
- Wallet detection for MetaMask, Coinbase Wallet, Phantom, Rainbow, and 30+ others
- Webhook confirmation when the on-chain transaction reaches finality
- Same dashboard for crypto and fiat payments — no separate reconciliation flow
- Standard 2% fee capped at €25 per transaction, the same as fiat
Connect your wallet to PayRequest and start accepting USDC alongside your existing payment methods. No code, no smart contracts, no separate platform — just one more option on the same checkout your customers already use.