BEFORE YOU BEGIN
- Keep one factual business description across every document.
- Link commercial records, wallet activity and fiat credits.
- Treat the checklist as preparation, not a promise of account approval.
Give the reviewer a usable starting point
Lead with a short description of what the company sells, who its customers are and why it receives or holds crypto-assets. Show the legal entity and ownership structure. Explain which activities are the company’s own treasury operations and which, if any, are services for clients.
A concise operating description helps a reviewer interpret the documents that follow. It should agree with the website, contracts, regulatory analysis and expected transaction profile. If an old pitch deck tells a different story, replace or explain it rather than sending both without context.
Build the evidence around three questions
First: who owns and controls the business? Second: where do the funds come from? Third: what will this account be used for? Create a document index around those questions, with a named contact for any follow-up.
| Question | Preparation examples |
|---|---|
| Ownership and control | Company records, ownership chart, authorised signatories |
| Commercial source | Contracts, invoices, revenue explanation and relevant statements |
| Asset route | Wallet inventory, transaction identifiers and conversion records |
| Expected account use | Counterparties, currencies, volumes and payment purposes |
Explain the controls you actually operate
EBA guidance frames assessment around risk factors and mitigating measures, including patterns of activity and geographical exposure. The bank may ask how the company identifies unusual activity, reviews counterparties or reconciles funds. Describe the current process and responsible person.
If a third party provides screening or transaction monitoring, explain what the company does with the output. A vendor logo is not an escalation procedure. Do not invent controls to make an application look complete; document gaps and the plan to address them accurately.
Keep the submission controlled
Use a dated index and avoid sending duplicate versions with inconsistent figures. For sample transactions, choose records that demonstrate the ordinary business and clearly label any exceptional activity. Request the provider’s secure submission route for identity or confidential material.
After submission, maintain a question log containing the request, answer, evidence and owner. Record material conditions attached to any acceptance. Keep the pack current when markets, products or counterparties change. Good preparation can make a review more efficient, but it cannot guarantee a particular institution’s decision or timing.
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