Educational only. Not tax, legal, or banking advice. Payment holds are decided by institutions under AML rules — outcomes vary.
A common fear after the MiCA transitional cliff: “my bank will reject every crypto transfer.” MiCA does not flip a master switch that forces banks to block crypto. Friction usually comes from AML programmes and the EU Transfer of Funds / Travel Rule framework (Regulation (EU) 2023/1113), especially when the counterparty looks unlicensed, opaque, or incomplete on originator/beneficiary data.
Related: MiCA deadline FAQ · CASP checker.
Does MiCA force banks to block crypto?
No. MiCA authorises and supervises crypto-asset service providers. Banks remain subject to their own anti-money-laundering and sanctions controls. Those controls may treat transfers to or from certain VASPs/CASPs as higher risk — that is not the same as a MiCA “ban.”
Why the Travel Rule matters
The EU Travel Rule requires certain information to travel with crypto-asset transfers between obliged entities (who is sending, who is receiving, and related identifiers, subject to thresholds and implementing detail). When a transfer involves an unlicensed or hard-to-identify venue, compliance teams may delay, query, or reject the payment until data is complete — or refuse the corridor entirely.
How an unlicensed exchange changes the picture
- Harder for the bank (and for you) to evidence a regulated counterparty.
- Higher chance of manual review on fiat on/off ramps.
- Messier paper trail if the venue later restricts EEA withdrawals.
Using an authorised CASP does not guarantee instant SEPA — but it usually reduces “who is this VASP?” ambiguity. Confirm entities on /mica/casps/.
What to keep when a transfer stalls
Tax timing often cares about when an event happened. A bank hold can desync fiat settlement from on-chain movement.
- Bank notice / chat / letter with dates.
- Exchange deposit/withdrawal tickets and txids.
- Amount, asset, fees, and the intended counterparty legal name.
- Final settlement date vs initiation date (note both).
If you abandon a transfer and reverse it, record the reverse as carefully as the original — software double-counts love chaos.
How to reduce friction (practical, not magic)
- Prefer CASP-authorised venues you can name on statements.
- Complete KYC consistently (same legal name as your bank).
- Avoid last-minute large corridors you have never used.
- Keep exports current so a frozen fiat leg does not strand your crypto history.
- Compare tax tooling on /software/ once the ledger is clean.
FAQ
My bank blocked a transfer to a licensed exchange — is that illegal?
Banks can still apply risk policies. Ask for the reason code and keep the written trail; this guide cannot override their decision.
Is Travel Rule the same as DAC8?
No. Travel Rule is about information accompanying transfers between obliged entities. DAC8 is tax-administration reporting/exchange of information. Different pipes.
Sources
- Regulation (EU) 2023/1114 (MiCA)
- Regulation (EU) 2023/1113 (Transfer of Funds / Travel Rule updates)
- ESMA MiCA register page
CryptoTax Digest — educational only.
