Opening a business account for a crypto company is not an ordinary onboarding exercise. The provider is confirming more than the company’s legal existence. It is assessing what the business does, how funds move, which customers it serves, which jurisdictions it touches and whether its compliance controls match the operating model.
The process is not random. Setting up a crypto business account is documented and predictable when the application is prepared properly. Most delays come from incomplete ownership records, unclear product descriptions, missing licences, inconsistent forecasts or compliance policies that do not reflect actual operations.
Vellis crypto business accounts are structured for eligible digital asset businesses that need a managed route through setup. Vellis acts as an authorized provider, works with relevant underlying banking and payment partners, and manages the client relationship from assessment through activation. You work with Vellis.
The objective is to submit one complete, internally consistent file that allows compliance and underwriting teams to understand the business without reconstructing it from separate documents.
The Crypto Business Account Setup Process at a Glance
A well-run setup normally moves through six phases.
1. Initial eligibility review
The first review confirms the legal entity, business model, jurisdictions, ownership, licence position, expected account use and any immediate exclusion issues. This is a fit check, not the final underwriting decision.
2. Document collection
The applicant provides corporate records, ownership and identity documents, licences or legal analysis, financial information, policies and a detailed business description. Agree the document list at the start rather than responding to repeated ad hoc requests.
3. Compliance and underwriting review
The provider and relevant partners assess the company, beneficial owners, products, customers, counterparties, transaction profile and controls. They may request clarification, evidence or changes to the proposed structure.
4. Account design
The parties confirm the account-holding entity, currencies, payment routes, permitted activity, access rights and reporting requirements. Every entity and material flow should have a defined purpose.
5. Approval and contracting
The approved structure, terms and responsibilities are documented. Approval applies to the disclosed model. New products, markets or transaction types may require further review.
6. Activation and monitoring
The account goes live after final checks, access setup and testing. Crypto businesses should expect ongoing transaction monitoring, sanctions screening, periodic reviews and questions when activity changes.
The fastest applications are not always the simplest. They are the ones that explain complexity clearly and provide evidence early.
Documentation Checklist for a Crypto Business Account
Exact requirements depend on the entity, jurisdiction, licence status and proposed account use. Most applications cover five document groups.
Corporate and ownership documents
Prepare current formation documents, a registry extract, articles or operating agreement, tax details, shareholder and director registers, and a group structure chart. Include an ownership chart that continues through every corporate shareholder until all ultimate beneficial owners are visible.
Where required, add a board resolution or authorization for opening and operating the account. Names, addresses, dates and ownership percentages must match across every document.
KYC documents
For directors, beneficial owners and other relevant individuals, expect to provide valid identification, proof of address, nationality, tax residence, role, ownership or control details, and source-of-wealth or source-of-funds evidence when requested.
Licensing and regulatory evidence
Provide current licences, registrations and relevant regulator correspondence. Where a licence is not required, the provider may ask for a legal memorandum explaining the activity, jurisdiction and basis for exemption or classification.
A statement that the company is “not regulated” is not enough. The application should explain what the business does and why that activity falls within the stated legal position.
Business and financial information
Include a plain-English business description, product list, customer types, supported assets and networks, target and restricted jurisdictions, pricing, revenue model, account purpose, expected monthly volumes, average and maximum transaction values, financial statements or forecasts, operating capital and key exchange, custodian, liquidity or supplier relationships.
Forecasts should connect to contracts, users, pricing or funding plans. Unsupported high-volume projections create more questions.
Compliance documents
The policy set normally includes AML and counter-terrorist financing, customer due diligence, enhanced due diligence, sanctions screening, transaction monitoring, suspicious activity escalation, business-wide risk assessment, prohibited activity, Travel Rule procedures where applicable, wallet screening, record retention, training and compliance governance.
Templates do not prove readiness. Policies must match the real product, staffing, jurisdictions, customer base and transaction flow.
AML and Compliance Requirements Providers Need to See
Underwriting focuses on whether the business can identify risk, apply controls and produce evidence. Correct language in a policy is not enough if the process cannot be operated.
Customer risk and due diligence
The business should classify customers using factors such as location, legal form, ownership, activity, product use and expected transactions. The framework must define when standard or enhanced review applies and who approves higher-risk relationships.
Onboarding should establish identity, beneficial ownership, purpose of the relationship and expected activity. Business customers require entity and ownership checks, not only verification of the user creating the account.
Sanctions screening
Explain who is screened, which lists and data sources are used, how often rescreening occurs and how potential matches are investigated. Screening should cover customers, directors, beneficial owners, counterparties and relevant wallet addresses where appropriate.
The process must address both geographically focused sanctions and targeted sanctions against named individuals and entities. A country field alone is not sufficient.
Transaction and blockchain monitoring
The provider will want to see how fiat and digital asset activity are monitored together. Define expected behaviour, alert scenarios, thresholds, investigation steps, escalation routes and recordkeeping.
Blockchain analytics can support detection, but software does not replace judgment. The company should explain how alerts lead to restrictions, enhanced review, reporting or exit.
Travel Rule, governance and evidence
Where applicable, the business should be able to collect, retain and transmit required originator and beneficiary information. It should also document how transfers involving self-hosted wallets and unsupported counterparties are handled.
Named compliance ownership matters. Strong evidence includes completed risk assessments, monitoring reports, training records, sample case files, audits and documented remediation.
Eligibility Criteria: What Is Assessable and What Is Not
Crypto is not automatically ineligible. Business model, licensing, ownership, geography, controls and account use determine whether the case can be assessed.
Under the eligibility boundaries stated for this Vellis offering, the hard blocks are OFAC-restricted jurisdictions or sanctioned parties and MATCH-listed businesses. Everything else is subject to case-by-case assessment, underwriting and partner approval.
This does not guarantee approval. It means the decision is based on the complete risk profile rather than a blanket refusal based only on the word “crypto.”
Assessment factors commonly include:
• licence, registration or exemption status
• transparency and experience of owners and management
• countries of incorporation, operation and customer acquisition
• retail, institutional or business customer mix
• custody of customer assets
• fiat deposit and withdrawal flows
• exposure to mixers, privacy-enhancing assets or high-risk services
• self-hosted wallet use
• sanctions and blockchain monitoring
• transaction size, volume and velocity
• financial position and funding source;
• previous provider history.
MATCH is a terminated-merchant database used in card acquiring. A listing can affect the wider account and payment structure where card acceptance forms part of the setup. Known listings should be disclosed early.
A previous rejection is not always permanent. The key questions are why it happened, what has changed and whether the issue has been corrected.
Jurisdictional Considerations
Providers assess three maps: where the company is registered, where it operates and where its customers and counterparties are located.
Incorporation and management
The registered jurisdiction affects ownership transparency, tax, licensing and access to official records. The business should explain why each entity exists, what it does and how it connects to the account.
It should also disclose where management, staff, technology, custody, compliance and support functions sit. A company registered in one country but effectively managed from another must explain both.
Customers and counterparties
Identify current and planned customer locations, restricted markets and the controls used to enforce those restrictions. A global website with no geofencing, onboarding rules or location controls will create questions.
Counterparty geography also matters. Exchanges, custodians, liquidity providers, affiliates and major clients can introduce risk even when the applicant is incorporated in a lower-risk jurisdiction.
Coverage remains subject to eligibility, sanctions requirements and the risk appetite of relevant partners. OFAC-restricted jurisdictions and sanctioned parties are excluded.
For businesses that have already experienced blanket refusals, the guide on how to get banked when traditional banks refuse crypto explains how to distinguish a weak application from a genuinely unsupported model.
Timeline Expectations for Account Setup
There is no guaranteed onboarding timeline. Plan the process by stage.
Preparation: approximately 3 to 10 business days
A company with current records, clear ownership and completed policies can assemble the file quickly. Multi-entity groups or businesses missing legal analysis will need longer.
Initial review: approximately 5 to 15 business days
The provider checks fit, completeness and obvious eligibility issues. An indexed submission shortens this phase because missing information is easier to identify.
Detailed review: approximately 1 to 4 weeks
This phase creates most variation. Questions may cover licensing, customers, counterparties, wallet controls, financial forecasts and previous provider history. Speed depends partly on whether the applicant answers in complete, evidence-backed batches.
Final setup and activation: approximately 1 to 3 weeks
After approval, contracting, configuration, access controls, testing and final checks must be completed. Multi-entity or multi-currency structures can require more coordination.
A well-prepared case may complete within several weeks. A complex structure can take longer. Timelines remain indicative until the full file and partner structure have been reviewed.
Common Reasons for Rejection or Delay
Most unsuccessful applications fail for recurring reasons.
Vague business description
Terms such as “crypto services” or “Web3 infrastructure” do not explain the activity. State what customers do, which assets move, who controls funds, how revenue is earned and where fiat enters and leaves.
Contradictory information
The website, application, licences, terms and forecasts should describe the same business. Undisclosed entities, products or markets weaken trust.
Unresolved licensing
A pending application, uncertain exemption or outdated legal opinion can prevent approval. Explain the legal status directly and provide the basis, regulator correspondence and operating restrictions.
Unclear ownership or funding
Layered companies, nominee arrangements, undocumented loans and unexplained capital create additional risk. Provide a complete ownership path and evidence for operating funds.
Generic compliance policies
Copied documents often refer to products, regulators or procedures the company does not use. Reviewers compare policies with staffing, customer flows and monitoring capability.
Unsupported forecasts
Projected volume should connect to users, contracts, pricing, historical performance or funding. Large round numbers without assumptions weaken the file.
Undisclosed previous problems
Account closures, regulatory inquiries, frozen funds or provider disputes should be explained accurately. Controlled disclosure with remediation evidence is stronger than an omission found during screening.
Unclear account purpose
Describe who will send funds, why, in which currencies, where money will go and how often. An account request without a transaction map is difficult to assess.
How to Prepare a Stronger Application
Build one controlled application file before submission.
Start with a two- to four-page summary covering the entity, ownership, products, licensing, customers, jurisdictions, account purpose, expected volume, key counterparties and compliance controls.
Add a document index and use consistent file names. Where an item does not exist or apply, explain why.
Create a transaction-flow diagram showing who sends funds, which entity receives them, the commercial reason, any digital asset conversion, the exchange or custodian involved, the destination of withdrawals and the controls applied at each stage.
Review the file as one story. The company chart, licence position, website, customer process, forecast and AML controls should not contradict each other.
Assign one internal owner to coordinate legal, compliance, finance, product and management responses. Follow-up questions should be answered in complete batches.
Account setup should also support the wider finance model. The article on crypto treasury management explains how to separate operating cash, customer-related flows, exchange exposure and entity-level liquidity after approval.
Working With Vellis to Set Up a Crypto Business Account
Vellis manages the setup as the client’s authorized provider and point of contact. Underlying account, banking or payment infrastructure may be delivered by relevant partners, and Vellis may act as a referral agent in some instances. Vellis is not a bank or an acquirer.
The process begins with an eligibility and structure review covering the business model, entities, ownership, licences, operating jurisdictions, customer profile, expected flows and account requirements.
Vellis then defines the documentation request and coordinates questions with the relevant partners. You work with Vellis while the application moves through review. Where more evidence or structural changes are required, the objective is to resolve them in a controlled sequence rather than through disconnected requests.
After approval, Vellis supports account setup, access, operational alignment and ongoing relationship management. Material changes – including new entities, products, jurisdictions, customer segments or transaction flows – should be reviewed before introduction.
The business remains responsible for accurate disclosure and effective compliance. Vellis provides the structure, coordination and direct account contact needed to move an eligible case from preparation to activation.
