A digital-asset business expanding into the Gulf frequently treats its Abu Dhabi Global Market registration as the hard part. Banking, the operators discover, is the harder part. The Abu Dhabi Global Market (ADGM) is an international financial free zone on Al Maryah Island, regulated by the Financial Services Regulatory Authority (FSRA) – a common-law jurisdiction whose banking infrastructure sits squarely at the intersection of regional compliance expectations and global correspondent-bank scrutiny. Without a funded corporate account, the licence is commercially inert: fiat rails, payroll, client-money segregation and settlement all depend on it.
This page maps the corporate bank account opening process for businesses in ADGM, with particular attention to digital-asset operators. It addresses the regulated basis, the practical sequence, the cross-border friction points, and the decision logic that determines which institution a crypto-adjacent business can realistically approach.
Why the regulated basis matters before you approach a bank
Banks operating in ADGM conduct their own regulatory analysis of every prospective client, and for digital-asset businesses that analysis begins with the FSRA licence or registration the applicant holds. The FSRA governs regulated activities for virtual assets within the ADGM framework, and its recognised-virtual-assets concept directly influences how a bank classifies the risk profile of an inbound account application. A business that arrives at the bank without a clear FSRA permission – or with a permission that does not cover its actual activities – is likely to be declined or placed on an indefinite due-diligence hold.
The same logic applies to businesses that are ADGM-incorporated but not FSRA-regulated. A holding company or special-purpose vehicle with crypto-related beneficial owners will still face enhanced due diligence, particularly where the parent group holds a VASP (virtual asset service provider) licence in another jurisdiction. Banks operating inside the free zone are subject to the same FATF-aligned AML/CFT baseline as institutions outside it, including the obligations that flow from FATF Recommendation 15 on virtual assets.
In our practice, the single most avoidable reason a crypto-business account application fails in ADGM is a mismatch between what the entity says it does and what its licence actually permits. Banks see that mismatch immediately. Resolving it before submission – not after a decline – is the structural work we undertake before any client approaches a financial institution.
For a scoped review of your ADGM entity and its banking-readiness, contact OBOLUS at info@oboluslaw.com. The process above describes the standard path. Your facts – the entity, the user base, the banking – change the analysis. Map your options.
Which banks operate in ADGM and what do they require from crypto businesses?
Several international and regional banks hold ADGM licences and offer corporate account services, but the number willing to onboard a digital-asset business is meaningfully smaller than the total. The gap between a bank's presence in the free zone and its appetite for crypto-related business is one of the consistent friction points we see in ADGM mandates.
Banks that do engage with virtual-asset businesses in ADGM typically require, at minimum: a certified copy of the FSRA licence or exemption notice; a complete beneficial-ownership declaration traceable to natural persons; a source-of-funds and source-of-wealth narrative for each ultimate beneficial owner holding a material interest; a description of the business model in plain English (not in marketing language); projected transaction volumes and counterparty profiles; and an AML/CFT policy document that maps to the FSRA's own AML rulebook expectations.
Several banks additionally require evidence of the compliance officer's qualifications and, for exchange-type businesses, a demonstration that the entity has implemented the Travel Rule (the obligation to pass originator and beneficiary data with a virtual-asset transfer). Operators we advise routinely underestimate the depth of that documentation package. The bank's compliance team is not reviewing a summary; it is building a risk file it can defend to its own regulator and correspondent banks.
Timeline from submission of a complete package to account opening varies. Where the application is well-prepared and the business model sits within the bank's stated risk appetite, the process typically resolves in a matter of weeks. Incomplete submissions or novel business structures – including businesses with cross-border custodial arrangements or multi-chain settlement flows – can extend that materially.
What is the step-by-step account opening process in ADGM?
The process follows a defined sequence, and each step has a common failure point that a well-prepared applicant can avoid.
Step one: entity and licence verification. The ADGM entity must be registered with the ADGM Registration Authority and, if conducting regulated financial activities, licensed by the FSRA. The bank will verify both directly. Businesses that are incorporated in ADGM but operate through an offshore holding structure need to be ready to explain and document the full group structure, including any parent entities holding VASP permissions in other jurisdictions such as under the VARA regime in Dubai, under MiCA through an EU CASP authorisation, or under the MAS Payment Services Act in Singapore.
Step two: KYB and UBO documentation. Know-your-business and ultimate-beneficial-owner documentation is the single largest cause of delay. Every natural person who directly or indirectly holds a material interest in the entity must be individually verified. For entities with layered holding structures – a common feature of digital-asset businesses that have raised multiple funding rounds – this can involve producing certified identification, proof of address and source-of-wealth evidence for founders, major investors and, in some cases, key management personnel. Banks in ADGM apply enhanced due diligence to politically exposed persons and to beneficial owners resident in jurisdictions the bank internally classifies as elevated-risk.
Step three: business model review. The bank's onboarding team will conduct a substantive review of the business model. This is distinct from legal due diligence. The bank is assessing whether it understands what the business does, whether the projected transaction flows make commercial sense and whether the AML risk can be managed within the bank's own risk appetite. A business that describes itself as a "Web3 platform" without precision about whether it holds client funds, whether it exchanges tokens, or whether it settles in fiat will be asked for clarification – and that clarification, if it surfaces a regulated activity not covered by the FSRA licence, will lead to a hold or a decline.
Step four: compliance infrastructure review. Banks increasingly require sight of the applicant's AML/CFT policy, its Travel Rule implementation plan and its transaction monitoring arrangements. For exchange-type businesses, the bank will want to understand the on-chain analytics tools in use and whether the business has a mechanism for declining or flagging transactions from high-risk wallet addresses. This expectation is not uniform across all ADGM banks, but it is standard among those with established crypto-business programmes.
Step five: approval and account activation. Once the compliance file is complete and approved, account documentation is executed and the account is activated. Initial transaction limits may apply and are typically reviewed after a defined operating period.
How do ADGM accounts interact with cross-border fiat rails?
An ADGM corporate account is denominated primarily in UAE dirhams (AED), but multi-currency accounts – including USD, EUR and GBP – are available from several institutions. For a digital-asset business, the more consequential question is not the currency of the account but the quality of the correspondent-banking relationships sitting behind it.
Correspondent banks – the institutions that clear international dollar payments – apply their own screening to transactions flowing through them. A crypto business that successfully opens an ADGM account may still find that large USD transactions to or from certain counterparties trigger holds at the correspondent layer. This is not an ADGM-specific problem; it is a structural feature of dollar-clearing that affects virtual-asset businesses in every jurisdiction.
Businesses that route significant transaction volumes between ADGM and EU counterparties face an additional layer: EU banks onboarding a counterparty in a non-EU jurisdiction will apply their own due-diligence standards, and where the ADGM entity is also a virtual-asset business, those standards increasingly reference the MiCA regime and the FATF mutual evaluation record of the UAE. The UAE's removal from the FATF grey list in 2024 improved the environment materially, though individual bank policies have not all updated at the same pace.
Where fiat rails through a traditional bank are constrained, some operators in ADGM supplement their banking arrangements with an EMI (electronic money institution) relationship – an EMI licensed in an EU or UK jurisdiction that provides a payment account and IBAN without the full correspondent-bank exposure of a traditional corporate account. The interaction between an ADGM entity and an EU or UK EMI raises its own regulatory questions, including whether the activity being conducted through the EMI triggers a licensing obligation in the EMI's home jurisdiction. That analysis must be done before the arrangement is put in place, not after the EMI asks for an exit.
If your fiat rails are constrained or your banking arrangements need a second read, write to OBOLUS at info@oboluslaw.com. If a prior application stalled or an account was closed, a second read can surface the structural reason and the route back. Map your options.
What crypto-specific banking risks do ADGM operators face?
Operating without the right regulatory permission in ADGM – or allowing the account to be used for activity that exceeds the licensed scope – exposes a business to enforcement action by the FSRA, account suspension by the bank and, in the most serious cases, referral to the relevant UAE financial intelligence unit. The consequence is not theoretical: we have seen businesses lose their banking in ADGM precisely because a transaction pattern – high-volume stablecoin settlements or cross-border crypto-to-fiat conversions – emerged that the bank had not underwritten at onboarding.
Three risk categories are consistently present in ADGM crypto-banking files. First, activity creep: the business expands into a new product line (lending, yield, structured products) without updating its FSRA licence, and the bank's transaction monitoring surfaces the new activity before the licence does. Second, counterparty risk: the business receives funds from an exchange or wallet that the bank's screening tool flags as elevated-risk. Third, documentation drift: the KYB file the bank holds no longer reflects the current beneficial-ownership structure after a funding round or a founder departure.
Each of these is manageable. None of them is avoidable by ignoring them. The discipline of keeping the bank's compliance file current – treating it as a live document rather than a one-time submission – is the operational practice that distinguishes businesses that retain their banking from those that lose it.
A common assumption among inbound operators is that an ADGM incorporation and a clean FSRA licence is sufficient to unlock banking with any institution in the free zone. That is not the position. Each bank applies its own risk appetite, its own correspondent-bank constraints and, in many cases, its own internal policy on digital-asset exposure. The regulatory permission is a necessary condition for banking. It is not a sufficient one.
A recent matter: account access recovered after a compliance review
In a recent engagement, a custody-and-settlement business that had held an ADGM account for several months had its account placed under a transaction hold following a routine review by the bank's compliance team. The bank's stated concern related to a series of outbound transfers to counterparty wallets the bank had not been informed of at onboarding. We reviewed the transaction record, identified the specific screening flags that had triggered the hold and prepared a comprehensive response to the bank's compliance notice – including an updated counterparty profile, a reconciliation of the transaction log against the entity's licensed activity and a revised AML policy document addressing the Travel Rule gap the bank had identified. The account hold was lifted and the relationship was restructured on revised terms. The matter resolved within a matter of weeks. No enforcement action was taken.
Which business profile should take which approach to ADGM banking?
The right approach to ADGM corporate banking depends on the operator's profile and the nature of its regulated activities.
Profile A: an FSRA-licensed exchange or trading platform. This business conducts regulated virtual-asset activity within the ADGM perimeter. Its account application is supported by an active licence, but the bank will apply the deepest scrutiny to the transaction-volume projections and the AML infrastructure. The priority is a complete, pre-cleared compliance file before submission. Timeline to account opening, where the file is well-prepared, is typically measured in weeks rather than months.
Profile B: a holding company or special-purpose vehicle with a crypto-active subsidiary. This structure is common among digital-asset fund managers and venture vehicles. The holding company may not itself hold an FSRA licence, but its beneficial owners and the nature of the subsidiary's activities will be the primary focus of the bank's due diligence. Group-structure clarity and a clean UBO chain are the determinative factors. Banks will want to understand how funds flow between the holding entity and its operating subsidiaries, including any offshore VASP licensed under, for example, the VARA regime or the BVI FSC.
Profile C: a business with prior banking disruption. A business that has had an account closed – whether in ADGM or in another jurisdiction – needs to address that history directly in its application narrative. Banks share information through correspondent networks and compliance databases. A prior closure that is not disclosed and is later discovered will almost always result in a decline. Where the closure was the result of a compliance gap that has since been remedied, a clear and documented account of the remediation is a stronger approach than omission.
Profile D: an EU or UK operator using ADGM as a second banking anchor. This profile is increasingly common as MiCA-regulated CASPs build redundancy into their banking structures. The cross-border analysis here focuses on whether the ADGM entity's activities require an FSRA permission and on how the EU or UK regulator will characterise the relationship between the two entities. Where the ADGM entity conducts activity that falls within the EU's regulatory perimeter – for instance, providing services to EU-based retail clients – the MiCA passporting rules may apply regardless of where the entity is incorporated.
Related at OBOLUS
Related at OBOLUS
- Banking, Payments & EMI Onboarding – structuring fiat access, EMI relationships and payment licences for digital-asset operators.
- Fiat on/off-ramp banking in Bermuda – a comparative view of offshore fiat access for licensed virtual-asset businesses.
- Worldwide freezing orders in France (AMF/PSAN) – cross-border enforcement and asset-recovery options for businesses with French-regulated exposure.
FAQ
Why do banks close crypto company accounts?
Banks close crypto company accounts when transaction patterns, counterparty profiles or documented compliance gaps exceed the bank's internally underwritten risk appetite. Common triggers include undisclosed beneficial-owner changes, activity that exceeds the licensed scope, and receipt of funds from wallet addresses flagged by the bank's screening tools. A prior account closure in another jurisdiction that is not proactively disclosed is a particularly common cause of termination once it surfaces during a periodic review. Structural remediation – not merely a revised narrative – is required to re-establish banking on sustainable terms.
How can a VASP onboard with an EMI?
A VASP can onboard with an EMI (electronic money institution) by satisfying the EMI's KYB and AML requirements in the same way it would a bank, but the regulatory interaction is more complex. The EMI must assess whether providing payment services to a virtual-asset business makes it an indirect participant in VASP activity for the purposes of the Travel Rule. The VASP must assess whether using the EMI's infrastructure in a given jurisdiction triggers a local licence obligation. Both questions require legal analysis before the arrangement is put in place, not after a compliance notice arrives.
What does client-money safeguarding require?
Client-money safeguarding – the obligation to hold client funds in a segregated account separate from the firm's own money – is required under the FSRA's regulatory framework for licensed activities involving client assets. In practice it requires a designated safeguarding account at an approved credit institution, clear contractual terms with the bank confirming the segregated nature of the account, and ongoing reconciliation procedures that the FSRA can inspect. Businesses that commingle client and operational funds, even temporarily, risk both regulatory action and a bank compliance review that can result in account termination.
About OBOLUS
OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance that sit around them. Digital assets are the whole of our practice. We map the licence stack across operating, custody and payment layers before you commit – because a licence without banking is commercially inert, and we have seen that outcome more often than it should occur. To discuss your ADGM banking structure or a stalled account application, contact info@oboluslaw.com or message us at t.me/oboluslaw.
By Victor Olsen, Regulatory & Compliance Analyst – specialising in FSRA and Gulf-region regulatory frameworks for digital-asset businesses seeking licensed fiat access.
This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.