Opening a Crypto Business Bank Account. Requirements, process and pitfalls.

Founders typically approach business banking as a procurement exercise: find an institution, submit an application, wait. For a digital-asset company that sequence produces repeated declines, because the decision is largely determined by facts that were fixed months earlier — where the entity was incorporated, how ownership is layered, whether the activity requires authorisation, and what the money actually does.

Reversed, the process is far more tractable. Decide the operating jurisdiction based on where your customers are and what authorisation that requires. Structure ownership so it can be explained in a single diagram. Obtain or apply for the licence. Build the compliance stack. Then, and only then, approach institutions with a complete file.

This ordering costs time up front and saves months of rejected applications. It also protects your record: a trail of declines and short-lived accounts is visible to the institutions you will eventually want, and it makes each subsequent application harder.

The rest of this guide sets out what each stage requires and where files commonly fail.

Jurisdiction choice drives everything downstream: which authorisation applies, which institutions will look at you, what substance is expected, and how your counterparties perceive you.

Operating jurisdiction should follow your customers and your regulatory obligations, not tax outcomes. A business serving European customers is expected to hold European authorisation and will find European institutions accessible. Structuring the operating entity into a jurisdiction with no connection to the customer base creates a mismatch that compliance teams identify immediately and treat as a red flag.

Substance is assessed, not assumed. A real office, resident directors where required, local staff, and genuine decision-making in the jurisdiction of incorporation. An entity with a registered agent address and no presence is a materially weaker file, and in several markets it is an automatic decline.

Keep the ownership chain short. Every intermediate holding company adds a layer that must be documented, verified and explained. Structures exceeding two layers between the operating company and the ultimate beneficial owners routinely stall in due diligence, and structures involving nominee shareholders without a clear commercial rationale are frequently terminal.

Group entities matter. If the operating company sits within a group, expect the institution to review the group, not just the applicant. Related-party flows should be documented before they are asked about.

In every major market, authorisation is now the entry requirement for banking a digital-asset business, not a competitive advantage.

Establish first whether your activity falls within scope. Custody of client assets, exchange between digital assets and fiat, operating a trading venue, transfer services and, increasingly, certain stablecoin activity are in scope in most developed frameworks. Software vendors, holding companies and treasury entities frequently are not, but that position must be documented rather than assumed.

Where the activity is in scope, apply. An application in progress, with a reference number and a credible timeline, is materially better than nothing and some institutions will begin onboarding in parallel. An unlicensed in-scope operator is not a candidate at any serious institution.

Where the activity is genuinely out of scope, obtain a short written legal analysis stating why, and include it in the application pack. This single document resolves the question a compliance officer would otherwise escalate.

Do not treat licensing as a jurisdiction-shopping exercise. Institutions know which regimes are supervised in substance and which are nominal. An authorisation from a regime with no meaningful supervision adds little and can raise questions the file would otherwise not face.

Corporate: certificate of incorporation, memorandum and articles, register of directors, register of shareholders, certificate of good standing where the entity is more than a year old, and a group structure chart showing ownership to natural persons with percentages.

Individuals: certified passport and dated proof of address for every director and every beneficial owner above the applicable threshold, plus a professional CV for the founders. Documents dated more than three months before submission should be refreshed.

Source of wealth and source of funds: evidence of where founding capital originated. For digital-asset founders this often means historic exchange statements, disposal records and, where relevant, tax filings. Assertions without records are not accepted.

Business narrative: a two-page description of the business, its revenue model, its customers, its counterparties, and its expected volumes, accompanied by a flow-of-funds diagram showing money in, money out, currencies and rails. This document does more work than any other in the pack.

Compliance: written AML and KYC policy, sanctions policy, named compliance officer with CV, onboarding and monitoring procedures, blockchain analytics tooling in use, escalation thresholds, and any independent compliance review.

Commercial evidence: signed customer or partner agreements, invoices, audited or management accounts, and existing bank statements. Evidence that the business is real and trading materially strengthens an application.

Licensing: the licence, or the application with reference and status, or the legal analysis explaining why none is required.

The flow-of-funds description is where most applications are won or lost, because it is where the institution decides whether it understands your risk.

State plainly who pays you, in what currency, through what rail, and at what frequency and size. Then state who you pay, in what currency, through what rail, at what frequency and size. Then state what sits in between: conversion, custody, settlement, treasury.

Quantify. Expected monthly inbound volume, expected monthly outbound volume, average transaction size, largest expected single transaction, and the top counterparties by volume with their jurisdictions. Institutions will set monitoring thresholds from these numbers, and an account that immediately exceeds its stated parameters triggers review.

Be conservative and accurate rather than impressive. Overstating projected volume to appear attractive causes the account to be opened with expectations you then miss, which reads as a change in business model. Understating it causes your normal operations to trip monitoring in month one.

Distinguish own-account activity from client money. An institution treats a treasury moving its own funds very differently from one holding customer balances, and conflating them in the narrative creates confusion that compliance resolves conservatively.

Explain any activity that will look unusual before it is discovered: large one-off settlements, seasonal spikes, intercompany transfers, or funding rounds.

Applying widely is counterproductive. Each application creates a record, and a pattern of recent declines is itself an adverse signal.

Match on appetite, not on marketing. An institution's current appetite is defined by the profiles it has onboarded in recent months, not by the sectors listed on its website. Appetite moves quickly, and an institution that was open six months ago may have exited the segment entirely.

Match on service need. If the business requires multi-currency accounts, SEPA and SWIFT, and card acquiring, a payment institution may serve better than a bank. If it requires credit facilities, treasury products and deposit protection, only a bank will do. Applying to the wrong category wastes a quarter.

Match on jurisdiction logic. An institution wants to see a coherent connection between the entity, the licence, the customers and the account. The stronger that logic, the easier the file.

Plan for redundancy from the outset. Two relationships in different institution types and different jurisdictions is the practical minimum for an operating digital-asset business, because closure notices commonly give thirty days and a cold search under that deadline rarely succeeds.

File preparation: two to four weeks if documents exist, longer if the structure needs remediation. Institution selection and introduction: one to two weeks. Institutional due diligence: six to sixteen weeks. Account activation and rail testing: one to two weeks. Three to six months end to end is the realistic assumption for a bank relationship; specialist payment institutions can be materially faster.

Costs include account opening and maintenance fees, per-transaction and FX charges, and, where advisory support is used, professional fees. Opening balance requirements are set case by case by institution type and are not published.

Approval is the start of the relationship, not the end of the process. Expect periodic reviews, refreshed documentation annually or more often, and questions about transactions that fall outside stated parameters. Institutions terminate accounts for unresponsiveness as readily as for risk.

Operate the account as described. The most common cause of closure among approved digital-asset businesses is divergence between the flow described at onboarding and the flow observed in monitoring. Where the business changes, tell the institution before the transactions arrive.

Keep the compliance function funded. An institution that sees a client investing in monitoring, screening and staff treats it as a lower-risk relationship, and that shows up in review outcomes and in pricing.

Applying before licensing. In-scope activity without authorisation is a first-stage decline everywhere that matters.

Opaque ownership. Nominee shareholders, unexplained holding layers, or a chart that cannot be read in one pass.

Vague business descriptions. Phrases such as blockchain solutions or digital asset services tell a compliance officer nothing and force escalation.

Undisclosed prior closures. These are discovered, and non-disclosure converts a manageable history into a termination.

Mismatched jurisdiction. An entity in one place, customers in another, licensing in neither.

No substance. No office, no staff, no local decision-making.

Overstated projections. Numbers that do not materialise read as a change in business model and prompt review.

Simultaneous scattergun applications. Visible, and read as distress.

No compliance stack. No written policy, no named officer, no analytics tooling, no escalation procedure.

Poor responsiveness. Slow, partial answers during due diligence end more applications than adverse findings do.

We are an advisory firm working with lawfully structured and appropriately authorised businesses. We prepare files to institutional standard, match them against current institutional appetite, and make introductions. We do not hold client funds, operate accounts, or promise outcomes, and no institution can be committed ahead of its own due diligence.

Engagements begin with a structural review: entity, ownership, licensing position, substance, flow of funds and compliance stack. Where the profile is not currently bankable we say so and set out precisely what would need to change, which is often a structuring or licensing step rather than a banking one.

Where a case exists, we build the pack, write the business narrative and flow-of-funds documentation with you, and approach the specific institutions whose stated appetite fits. Our network spans more than a hundred banking and payment institutions across Europe, the Middle East, Asia and international financial centres, and we track which are currently open to which profiles.

We also build redundancy deliberately, because a single relationship is the largest operational risk most digital-asset businesses carry.