Sheet 001 EU crypto–fiat operations
Chart the crossing from chain to euro. Between a token and a bank credit lie four waypoints: the wallet, the checks, the conversion and the receipt. This atlas maps each one, with the evidence to keep at every landfall.
Legend Route 001 · USDC → EUR
01 WalletToken leaves self-custody 02 ChecksTransfer data, entity, screening 03 ConversionExecuted trade at a quote 04 Euro receiptCredit in the company’s name The token leaves self-custody.
Confirm the asset, the network and who controls the sending address before anything moves.
Token on-chain Euro after conversion
MiCA CASP authorisation Travel rule Transfer of funds regulation SEPA Instant IBAN in the company’s name DAC8 DORA Redemption at par Executed quote Source of funds Reconciliation MiCA CASP authorisation Travel rule Transfer of funds regulation SEPA Instant IBAN in the company’s name DAC8 DORA Redemption at par Executed quote Source of funds Reconciliation
Treasury off-ramp
Follow company-owned tokens through an eligible conversion provider to a verified euro account.
Open sheet → Treasury on-ramp
Map an approved company bank payment into a defined asset and custody arrangement. This is a process map, not a recommendation to buy.
Open sheet → Operating-liquidity route
Separate customer receipts, company conversion and domestic payroll. The route includes contingency planning, not just a transaction.
Open sheet → Continuity route
Move an eligible operating flow only after documenting termination terms, restrictions, destination permission and reconciliation.
Open sheet → 02 First principle
A token transfer is not a bank receipt.
There is an asset ledger, a service provider, an executed trade and a payment account. The useful questions sit in the water between them.
01 Asset 02 Evidence 03 Execution 04 Bank credit Conceptual operating sequence. Legal roles, eligibility and timing must be checked separately. Understand the distinctions → 01 Banking A bank account for a crypto company: build the evidence first A working file for EU companies that need a fiat account alongside crypto activity. Start with the entity, the activity and the expected flow. → 02 Banking When a bank exits a crypto company Separate a closure notice, a transaction review and a funds restriction. Then build an orderly response and migration record. → 03 Off-ramps From USDC to EUR: document every handoff A company treasury route from an identified wallet to a euro account, with a cost model and explicit settlement checkpoints. → 04 MiCA MiCA authorisation: map the service, then the file An operating guide to activity mapping, the contracting entity and the evidence behind a CASP authorisation application. → 05 Transfer data The travel rule: information travels with the transfer Originator, beneficiary and self-hosted-wallet checks, kept separate from the asset transfer and the commercial evidence. → 06 Banking IBAN discrimination or a different refusal? A fact-finding sequence for rejected euro payments, without treating every crypto-related restriction as an IBAN issue. → 07 Banking Explain a DeFi business to a fiat-account reviewer Translate protocol activity into legal entities, revenue, control rights and a traceable treasury file. → 08 MiCA EMT, ART and the rights behind a stablecoin Identify the referenced value, the issuer and the holder’s claim before comparing a stablecoin route with a euro balance. → 09 Reporting DAC8: organise the transaction record before reporting Separate provider reporting, tax residence information and the company’s own accounting and tax obligations. → 10 Banking What a bank reviewer needs to understand Build an indexed onboarding file that connects ownership, business activity, wallets, counterparties and expected euro flows. → MiCA · Field note
Do not leave a historic registration in a current-provider permission field.
Open sheet → Transfer data · Field note
Connect the identity information, technical event and commercial purpose.
Open sheet → Off-ramps · Field note
One calculation convention prevents several common quote-comparison errors.
Open sheet → Six dated field notes in this edition, plus twenty glossary terms.
Q Answers
Questions before you set out. 01 What is The Fiat Atlas? A visual, source-linked field guide to crypto-fiat operations for EU businesses. It maps legal roles, evidence, conversion and euro payment steps.
02 Does the site move money or open accounts? No. It is an informational project. It does not connect to wallets, execute trades, onboard customers or promise approval.
03 Are rates and provider permissions live? No. The calculator uses your scenario inputs. The register tool is a manual worksheet; official registers remain the source for current status.
04 How should the route illustrations be read? As conceptual operating maps, not prescribed legal processes. The actual entity, activity, asset and jurisdiction determine the requirements.
05 Can I use the tools privately? Calculations and worksheet exports run locally in the browser. No financial data is sent to a backend by this build.