Opening a corporate bank account for a digital-asset business in the United States is one of the most consequential – and most frequently underestimated – steps in building a compliant payments operation. Federal anti-money-laundering obligations under FinCEN, combined with a patchwork of state money transmitter licences (MTLs), mean that a crypto company without the right regulatory posture will be declined, debanked, or worse: frozen mid-operation by a correspondent bank that has quietly reassessed its risk appetite. The analysis below maps the regulated basis, the process, and the common fault lines we see in practice.
For an inbound business, the short answer is this: a US corporate bank account for a digital-asset company generally requires, at minimum, a FinCEN Money Services Business (MSB) registration and – for any business transmitting value on behalf of customers – state MTL coverage in the states where those customers are located. No single federal licence replaces the state layer. And no bank relationship survives without documented AML/KYC infrastructure that can withstand examination. This page explains each element and the cross-border complications that compound them.
The Regulated Perimeter: Federal and State Overlap
The United States does not operate a single federal digital-asset banking licence. Instead, FinCEN (Financial Crimes Enforcement Network) sits at the federal level, classifying virtual-currency exchangers and administrators as Money Services Businesses subject to the Bank Secrecy Act. That classification imposes registration, AML program, recordkeeping and reporting obligations – but it is not a licence to transmit. The money-transmitter licence is a state-level instrument, and the requirement applies state by state based on where a company's customers are located, not where the company is incorporated.
Separately, the SEC and CFTC regulate securities and commodities activity within the digital-asset space. A company facilitating spot transactions in assets the SEC deems securities faces broker-dealer or exchange registration requirements that operate entirely apart from the MTL layer. Operators we advise regularly underestimate the overlap: a single product that accepts fiat, converts to a token, and transmits value can simultaneously engage FinCEN's MSB rules, state MTL requirements, and potentially the SEC's registration framework. Getting the perimeter wrong before approaching a bank is the most common reason an account application stalls before it begins.
Who Needs a State MTL Before Applying to a Bank?
Any business that receives money from one person and transmits it to another – or that exchanges value on behalf of customers – is likely a money transmitter under state law and needs an MTL in each relevant state. The threshold question is whether the activity involves "money transmission" as defined by the applicable state statute, and definitions vary. Some states exempt intra-company transfers; others impose MTL obligations on stablecoin issuers, custodians, or even certain lending arrangements.
In our cross-border practice, we see three operator profiles that consistently misread their MTL exposure. First, foreign-incorporated exchanges that onboard US retail customers and assume a single offshore licence resolves US compliance. It does not. Second, token issuers that collect fiat at primary sale and believe they fall outside the money-transmission perimeter because they are "issuing" rather than "transmitting." State regulators frequently disagree. Third, DAO-adjacent structures that distribute treasury proceeds to contributors, which several state regulators have treated as money transmission. The NYDFS BitLicense adds a further layer for any business that touches New York customers – a standalone, activity-specific permit with its own capital, cybersecurity and compliance program requirements.
Practical bridge: The process above describes the standard path. Your facts – the entity, the user base, the banking – change the analysis materially. For a scoped assessment of your MTL exposure before you approach a US bank, contact OBOLUS at info@oboluslaw.com.
What US Banks Actually Assess in a Crypto Onboarding
US banks conducting due diligence on a digital-asset applicant are not simply checking for a licence. They are assessing whether the applicant's compliance program will survive a federal examination. The FinCEN MSB registration is table stakes. Beyond it, the bank's compliance team will typically review the AML/KYC policy documentation, the sanctions screening program, transaction monitoring logic, the beneficial ownership structure (to satisfy Customer Due Diligence – CDD – rules), and the adequacy of the applicant's on-chain forensics capability.
Banks operating in the US are themselves subject to federal AML obligations, and they are examined on the quality of their customer risk assessments. A crypto applicant without documented controls shifts risk onto the bank's own examination posture. That is the commercial reality behind most account declines we see – it is rarely a blanket policy against crypto, and almost always a documented-controls gap. In our practice, we have seen applications with strong MTL coverage declined because the applicant's AML policy was a repurposed template with no crypto-specific transaction monitoring logic. Conversely, we have seen applicants without a full MTL stack onboard successfully at the community-bank level because they could demonstrate a mature, examined compliance program and a limited, clearly bounded activity scope.
The Travel Rule (the obligation to pass originator and beneficiary data with a virtual-asset transfer) also enters the bank's assessment. A VASP counterparty that cannot demonstrate Travel Rule compliance – particularly with US-based counterparts – is a material compliance risk for the receiving institution. Operators we advise build Travel Rule capability before approaching US correspondent banks, not after.
The Account-Opening Process: Steps and Timeline
Opening a US corporate bank account for a digital-asset business is a sequential process that typically spans several weeks to several months, depending on the bank tier, the complexity of the applicant's structure, and the completeness of the submission package. The timeline is not fixed in statute – it is driven by the bank's internal review process and the applicant's ability to respond to information requests without delay.
The process generally follows five stages. First, entity and structural diligence: the bank verifies the corporate structure, beneficial ownership chain, and jurisdictions of incorporation. For a cross-border business with a non-US parent, this includes confirmation that the US entity is the correct counterparty and that the inter-company flows are documented. Second, regulatory status confirmation: FinCEN MSB registration, state MTL coverage (or a documented exemption analysis), and any activity-specific licences such as the NYDFS BitLicense. Third, compliance program review: AML policy, KYC procedures, sanctions screening, transaction monitoring, and any third-party audit or examination history. Fourth, product and transaction-flow review: the bank maps anticipated flows against its own risk appetite – on-chain volumes, fiat entry and exit mechanics, custody arrangements, and counterparty jurisdictions. Fifth, account structuring and controls agreement: operating account, trust or custodial account (if client money is held), and any reserve or compensating balance requirement the bank imposes.
In a recent matter, a payments company incorporated in a European jurisdiction sought US correspondent banking for a stablecoin-to-fiat settlement product. The company held a MiCA-transitional registration in its home jurisdiction but had not completed FinCEN MSB registration or assessed its MTL exposure in the states where its US institutional clients were located. We structured the US compliance layer – registration, a multi-state MTL filing plan, an updated AML policy with US-specific transaction monitoring thresholds, and Travel Rule documentation – before the bank submission. The account was onboarded within a commercially acceptable window after the submission package was complete.
Cross-Border Complications: Foreign Entities Seeking US Rails
A foreign-incorporated digital-asset business that wants US fiat rails faces a layered problem. The US bank must satisfy itself that the foreign entity is not using a US account to circumvent its home jurisdiction's rules, that the US nexus is genuine, and that the AML standards of the home jurisdiction are at least broadly consistent with US expectations. Jurisdictions assessed as high-risk by FATF – or subject to OFAC sanctions programs – create per se barriers. But even businesses from well-regarded jurisdictions face elevated scrutiny if their home regime's Travel Rule implementation is immature or if correspondent banking relationships in the home country have historically been problematic.
The entity structure matters as much as the licence. A Delaware LLC or a US subsidiary of a foreign parent is generally the required form. The subsidiary must be the actual operating entity for US-facing flows – not a passthrough for the parent. Banks examine inter-company agreements, management fee structures, and the real location of decision-making. A nominal US entity with all commercial substance offshore will not survive the enhanced due diligence that US banks apply to cross-border digital-asset clients.
Tax interaction is another axis that operators in our practice routinely defer too long. A US subsidiary engaged in money transmission may generate effectively connected income subject to US corporate tax. The cross-border royalty or IP licensing arrangements that reduce taxable income in other jurisdictions require careful documentation to survive IRS scrutiny when combined with regulated money-transmission activity. We structure the licence, banking and tax layer as a single mandate rather than three disconnected workstreams – because the banking relationship depends, in part, on the coherence of the overall structure.
If a prior application stalled or an account was closed, a second read can surface the structural reason and the route back. For a scoped review of a declined or disrupted US banking relationship, write to OBOLUS at info@oboluslaw.com.
Decision Matrix: Which Profile Needs What
Not every digital-asset business approaching a US bank presents the same fact pattern. The right structure depends on the operator's activity, customer base and home jurisdiction.
Profile A – Foreign exchange with US institutional clients only: The typical path is a US subsidiary, FinCEN MSB registration, a limited MTL portfolio covering the states of incorporation and operation, and an institutional-grade AML/KYC program. The NYDFS BitLicense is required if New York-based institutional clients transact through the account. Timeline to a complete submission package is variable – typically measured in months for a well-resourced applicant working from a standing compliance infrastructure.
Profile B – US-incorporated fintech adding crypto-to-fiat settlement: The entity exists; the question is whether the new activity triggers additional MTL requirements or NYDFS BitLicense obligations beyond the existing money-transmitter or payment-services coverage. A gap analysis against the new product scope is the starting point. Adding a crypto leg to an existing licensed money-transmitter operation is faster than a greenfield application, but regulators in several states treat it as a material change requiring pre-approval.
Profile C – Non-US stablecoin issuer seeking US redemption rails: This is the highest-complexity profile. The issuer must assess whether its stablecoin constitutes a prepaid access product, an e-money instrument, or a security under US law. Each classification carries a different regulatory path. FinCEN's guidance on prepaid access and the SEC's ongoing enforcement posture on stablecoins both bear on the analysis. A US bank accepting redemption flows from a stablecoin issuer will require documented legal analysis of the token's classification before onboarding. We map the classification, the licence stack and the banking structure as a single engagement.
Common Mistakes That Stall or End a US Banking Relationship
The most consequential mistakes we see are structural, not operational – and they are made before the first bank conversation begins.
The first is assuming that FinCEN MSB registration is sufficient for banking purposes. It is necessary but not sufficient. State MTL gaps – particularly the absence of coverage in commercially important states – are a leading reason for declined applications at mid-tier and large US banks. The second is submitting an AML policy that describes a compliance program the company does not actually run. US banks are experienced at identifying template-derived policies that do not reflect the applicant's real transaction flows. The third is failing to disclose prior banking relationships that were terminated. US bank onboarding questionnaires ask directly; a disclosed termination with a documented explanation is survivable. An undisclosed termination discovered during due diligence ends the application.
A common assumption is that a single offshore licence – an EU CASP authorisation under MiCA, a VARA licence from Dubai, or a MAS DPT service licence from Singapore – is enough to satisfy a US bank's regulatory compliance question. It is not. Those licences demonstrate good standing in their own regimes, but they do not substitute for US federal and state requirements. In our practice, we present offshore licences as evidence of a compliance culture, not as a replacement for US-specific compliance infrastructure. The US bank's examiner will assess US compliance standing on US standards.
FAQ
Why do banks close crypto company accounts?
US banks close crypto company accounts for several recurring reasons: undisclosed or incomplete MTL coverage, AML compliance programs that fail internal review or examination, activity outside the scope described at onboarding, and correspondent-bank pressure applied through the bank's own risk-tiering process. A documented, examined compliance program – including transaction monitoring, Travel Rule capability and sanctions screening – significantly reduces termination risk. Where an account has been closed, the underlying structural reason should be identified before a new application is made.
How can a VASP onboard with an EMI?
A VASP (virtual asset service provider) seeking onboarding with an EMI (electronic money institution) in the US context typically approaches a licensed e-money or prepaid-account issuer rather than a deposit-taking bank. The EMI will assess the VASP's AML/KYC program, its FinCEN MSB registration, state licensing posture and transaction monitoring capability. The EMI's own regulatory obligations require it to treat the VASP as a high-risk customer. Documented controls, a clear product scope and a disclosed regulatory history are prerequisites. Engagement typically requires a period of enhanced due diligence before account activation.
What does client-money safeguarding require?
Client-money safeguarding in the US context for a licensed money transmitter generally requires that customer funds be held in a permissible investment or trust account, segregated from the company's own operating funds, and covered by adequate surety bonding or net-worth requirements set by each state's MTL rules. The specific requirements vary by state. A company holding customer fiat balances must map each state's safeguarding rules against its actual custody arrangement and document compliance before opening the relevant accounts. Failure to segregate customer funds is an examination finding that can trigger MTL suspension.
Related at OBOLUS
- Banking, Payments & EMI Onboarding – full-spectrum counsel on fiat-rail structuring for digital-asset businesses globally
- Fiat on/off-ramp banking in the Czech Republic – EU-based banking alternatives for cross-border payment structures
- Token legal classification for regulated entities – how token classification affects banking and licence requirements
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 – and we structure licensing, banking and tax as one mandate rather than three disconnected workstreams. To discuss your US banking structure, contact info@oboluslaw.com.
By Victor Olsen, Regulatory & Compliance Analyst – specialising in US federal and state digital-asset regulatory frameworks, FinCEN MSB compliance and cross-border payments structuring.
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.