The short answer
“Crypto-friendly” is not a licence category or a promise of acceptance. Assess the account against the company’s actual activities, the provider’s legal role and its written eligibility criteria. Authorisation of a crypto service and a bank’s onboarding decision are separate checks. [EUR-Lex] [EBA]
Source-linked facts below are distinct from our suggested workflows. Examples are hypothetical; this is not individual legal, tax or investment advice.
- 01Business model
- 02Legal roles
- 03Evidence file
- 04Account review
Define the business before choosing the account
A software studio paid in tokens, a proprietary treasury, a custodial exchange and a token issuer do not present the same operating profile. Write down what the company sells, who pays it, whether it holds assets for clients, and where conversion takes place. A brand label such as Web3 is not an adequate description of these activities. The MiCA service categories concern specified services, not every company that owns a token. [EUR-Lex]
Draw a single representative transaction with names of legal entities rather than logos. Mark who controls the wallet, who executes the trade, who sends the euro payment and who owns the receiving account. If client assets appear anywhere, separate them from company treasury. This drawing is an editorial preparation tool, not a legal determination of scope.
Read the legal roles separately
A bank deposit, a payment account, an electronic-money balance and crypto custody should not be treated as interchangeable products. Ask for the legal entity in the contract and identify what it is authorised to do. The European register is useful for MiCA services, but a CASP entry does not by itself establish banking authorisation or protection for a particular balance. [ESMA] [EUR-Lex]
Make a short role register: account provider, crypto-service provider, issuer where relevant, and any payment intermediary. Record the official source used to check each one. Do not collapse several group entities into one row because their websites share a brand. A contract naming a different entity from the register result requires investigation before funding.
Prepare evidence that can be followed
Build a document index rather than sending an unlabelled archive. It should connect incorporation and ownership records to the operating model, material counterparties, financial information, wallet-control arrangements and the origin of expected receipts. The document set depends on the provider and the business; this is not a universal onboarding checklist.
For a token receipt, connect the commercial agreement, invoice or other underlying transaction with the wallet entry, conversion record and anticipated bank receipt. A transaction hash proves that an on-chain event can be located. It does not explain the commercial reason for the payment or prove the legal ownership of a wallet. Explain gaps explicitly, with an owner and a proposed way to resolve them.
Get written answers on the proposed flow
Before submitting a full application, ask whether the provider supports the exact activity, entity location, expected currencies and named conversion counterparties. Ask whether transfers from a third-party exchange or an omnibus account are permitted, and what evidence is needed to identify the sender. Keep the answer with the contract version and the date.
Avoid treating a conversation with sales as permission for an activity excluded by the applicable terms. Record any uncertainty as unresolved. Do not change descriptors, counterparties or the business description to make a prohibited flow look ordinary. A workable setup is one the provider understands and accepts, not one that passes unnoticed.
Plan the first transfer and the fallback
Use a controlled test only after the receiving account and crypto provider are approved for the flow. Confirm the asset, network, address, beneficiary name and reference through trusted channels. Agree who can authorise a transfer and who verifies that the instructions match. Size the test to the operating risk rather than taking a percentage from a generic guide.
After a successful test, reconcile the execution report, fees and actual bank credit. A small transfer is not proof that a larger one will clear without review. Set operational escalation contacts and keep enough liquidity outside an untested route to avoid making payroll dependent on its first full-size transaction. This is an operational scenario, not an investment recommendation.
Maintain the file after onboarding
Account access is an ongoing relationship. An acquisition, new token, new customer geography or change from own-account dealing to client services can materially change the activity described in the original file. Maintain a change log and ask which changes must be notified under the provider’s agreement.
A periodic internal review can compare expected and actual volumes, counterparties, wallets and jurisdictions. Record discrepancies and the explanation; do not rewrite the original forecast after the fact. The EBA distinguishes individual risk management from blanket exclusion of categories, but its guidance does not promise that a particular company will receive an account. [EBA]
Working checklist
Ticks record your work, not an approval or compliance score. Progress stays in this browser where storage is available.
Method, assumptions and limits
Regulatory facts are linked to primary sources. Suggested workflows are our editorial synthesis; examples and fee scenarios are hypothetical. The mechanical illustration is a conceptual navigation aid, not a prescribed legal funds flow.
This is a dated research edition, not an automatically updated register or live price feed. Check the applicable entity, service, jurisdiction and source version before using the material.
Read the methodologyQAnswers
Questions before you set out.
01Does a MiCA authorisation guarantee a bank account?
No. MiCA status and bank onboarding are different questions. Assess the exact service and the bank’s requirements.
02Should the company hide token-related revenue?
No. Describe the activity and flow accurately; concealment is not a reliable or appropriate onboarding method.
03Is a transaction hash enough?
Not normally as a complete operating explanation. Link the on-chain record to the commercial purpose and the relevant party.
04Does this page recommend a particular bank?
No. It supplies an evidence and eligibility framework, not a ranking or approval promise.
Sources & scope
Research snapshot: 12 November 2026. The dated rule, its scope and the legal entity matter. Open the primary source before acting.
- EUR-Lex: Regulation (EU) 2023/1114 — Markets in Crypto-AssetsEU legislation
- ESMA: MiCA implementation and the central registerRegulator register and guidance
- EBA: Guidelines challenging unwarranted de-riskingRegulator guidance
- EUR-Lex: Regulation (EU) 2023/1113 — information accompanying transfersEU legislation