BEFORE YOU BEGIN
- Describe each incoming and outgoing flow before comparing accounts.
- Check the contracting entity and permitted activity, not just the brand.
- Get material restrictions in writing and keep a dated copy.
Start with the transaction you need to make
A software company paid occasionally in USDC, a broker handling client orders and a token issuer can all describe themselves as crypto businesses. Their account requirements are different. Begin with a one-page flow: who pays the company, for what, in which asset, through which conversion provider and into whose bank account.
Add the expected monthly volume, normal transaction size and occasional peaks. Label company treasury separately from client money. This is an editorial preparation checklist, not a universal bank application form. Its purpose is to make the first conversation specific enough to produce a useful answer.
Read the entity behind the interface
Ask which legal entity contracts with the company and which entity provides the account, conversion and payout. Record the applicable regulator and register entry for each regulated service. ESMA publishes MiCA register information, but a crypto-service authorisation does not establish that a particular bank will accept your business.
Ask whether the displayed balance is a bank deposit, e-money or another claim; request the relevant protection and insolvency terms. Do not use the existence of an IBAN as a substitute for understanding the account structure.
Turn restrictions into a comparison
Use the same scenario in every provider enquiry. “Can we receive EUR from this named exchange for our own software revenue?” is easier to assess than “Are you crypto-friendly?” Record the answer, date and any conditions.
| Question | Evidence to retain |
|---|---|
| Which activities are accepted? | Written eligibility criteria for your business model |
| Which counterparties may pay? | Named restrictions and third-party payment rules |
| What can interrupt a payout? | Review process, document requests and escalation route |
| How is pricing calculated? | Account, conversion, payout and minimum-volume terms |
Prepare for ongoing review
The EBA describes a risk-based assessment that considers customers, products, delivery channels and geography. Opening an account does not end the information process. Assign someone to update the provider when the activity changes materially and to answer requests with consistent records.
Maintain a route file containing the business description, ownership chart, sample invoices, conversion statements and reconciliations. Review account terms before a new token, market or customer segment changes the original story. A shortlist is useful when it survives these operational questions, not when it contains the most logos.
Read the source in context. Provider policies, eligibility and national implementation can change. This field note explains an operating framework, not an account approval or individual legal opinion.
Back to all field notes