BitLicense cost and technical requirements: what New York asks your systems to show
BitLicense cost: a $5,000 fee, a bond generally of $500,000 or more, capital and a yearly DFS assessment. What Parts 200 and 500 ask your systems to show.
BitPolaris Engineering
English original
The BitLicense application fee is $5,000. The licence costs much more than that: a surety bond or trust account that the New York Department of Financial Services (DFS) says is generally at least $500,000, capital that DFS sets for each licensee, a yearly supervision assessment, and the audits and tests that 23 NYCRR Part 200 requires every year. Most of the technical work is evidence. DFS wants to see that your ledger, logs, keys and recovery plan work as described before it reviews the application.
This article covers BitLicense cost and requirements from the system side. It lists the fees and recurring charges with their sources, maps the Part 200 and Part 500 rules to platform controls and evidence, and notes what the rules leave to you. We read the regulation text and the DFS pages on 12 November 2026. This is a technical reading of the rules, not legal advice; counsel should confirm. The official Westlaw text of Part 200 returned an error to us, so section quotes are from the Cornell Legal Information Institute copy of the same regulation.
Who needs a BitLicense?
Under 23 NYCRR 200.3(a), no person may engage in Virtual Currency Business Activity without a licence. Section 200.2(q) defines it as any of five activities involving New York or a New York resident:
- receiving virtual currency for transmission, or transmitting it;
- storing, holding or maintaining custody or control of virtual currency on behalf of others;
- buying and selling virtual currency as a customer business;
- performing exchange services as a customer business;
- controlling, administering or issuing a virtual currency.
DFS says an out-of-state business needs the licence if it deals with any person who resides, is located or does business in New York. Registration with FinCEN does not replace it. Merchants that accept crypto for goods, and people who only invest, are exempt (200.3(c)). DFS also says that developing and distributing software “as a purely technical service” does not need a BitLicense, but running a wallet service that holds other people’s funds probably does.
Three points change the plan:
- Fiat needs a second licence. A BitLicensee that moves US dollars also needs a New York money transmitter licence under Banking Law Article 13-B, which is a separate application.
- A trust charter is the alternative. A New York limited purpose trust company can conduct virtual currency business with the Superintendent’s approval, can act as a fiduciary and can transmit money without a separate licence. It is a different, heavier process under the Banking Law.
- The federal layer still applies. A money services business registers with FinCEN (31 CFR 1022.380). The funds Travel Rule applies to transfers of $3,000 or more (31 CFR 1010.410(f)), and FinCEN applies it to convertible virtual currency.
On 12 November 2026 the DFS page listed 24 BitLicensees (9 with a virtual currency licence only, 15 with virtual currency and money transmitter licences) and 13 limited purpose trust companies. Four authorisations were dated 2026.
What does a BitLicense cost?
DFS publishes some of the costs. Others depend on the business model. The table lists what we could source and marks what we could not.
| Item | Amount | Source |
|---|---|---|
| Application fee | $5,000, not refunded if denied or withdrawn | 23 NYCRR 200.5 |
| Fingerprinting and background reports | Vendor fees for each principal and each employee with access to customer funds | 200.4(a)(4)–(5); amount not published |
| Surety bond or trust account | Generally at least $500,000, can be higher for the business model | 200.9(a); DFS BitLicense FAQ 17 |
| Capital | Set by DFS for each licensee, in cash, virtual currency or investment-grade assets | 200.8; no published minimum |
| Yearly DFS assessment | FY 2026-27 budget $15,462,000 across 24 institutions | 23 NYCRR Part 102; DFS assessment chart, FY 2026-27 Q3 |
| Money transmitter licence | Separate fee, bond and net worth if you move fiat | Banking Law Article 13-B; not covered here |
| Recurring audits and tests | Audited financials with internal-control attestation, yearly AML test, yearly pen test, quarterly vulnerability assessments, yearly BCDR test | 200.14(b), 200.15(c)(2), 200.16(e)(1), 200.17(e); prices depend on your providers |
We did not include legal fees or total budgets from secondary sites. They are rarely sourced and they vary widely with the business model.
The yearly assessment, worked out
Since a 2022 amendment to Financial Services Law section 206 and the adoption of 23 NYCRR Part 102 in April 2023, DFS bills licensees for the cost of supervising them. Each licensee gets four estimated quarterly bills and a final true-up. The cost has two parts. The supervisory part splits 50% of supervisory hours by transaction count and 50% by average custody value, in size bands. The regulatory part is shared equally among licensees.
The DFS chart for fiscal year 2026-27 (quarter 3) gives an hourly rate of $157 and these hours per institution:
| Band | Transactions in the prior year | Hours | Custody value (average of four quarter-ends) | Hours |
|---|---|---|---|---|
| None | 0 | 0 | $0 | 0 |
| Small | 1 – 124,106 | 383 | $1 – $88,868,305 | 863 |
| Medium | 124,107 – 14,171,177 | 1,725 | $88,868,306 – $2,020,688,678 | 2,588 |
| Large | 14,171,178 or more | 6,900 | $2,020,688,679 or more | 6,900 |
The regulatory component is $4,534,373. The following figures are our arithmetic from the chart, not DFS figures. It assumes the regulatory part is split equally across the 24 institutions in the chart.
- Licensee with no volume: about $189,000 a year ($4,534,373 ÷ 24). Bands are set from the prior year’s volume, so a new licensee probably starts here.
- Smallest bands for both bases: (383 + 863) × $157 = $195,622, plus the regulatory share: about $385,000 a year.
- Largest bands for both bases: (6,900 + 6,900) × $157 = $2,166,600, plus the regulatory share: about $2.36 million a year.
The real bill moves with the number of licensees, DFS staffing and the true-up. Treat these figures as a planning range and ask DFS or counsel for your expected band.
How does the application work?
Applications go through the Nationwide Multistate Licensing System (NMLS) and follow its New York virtual currency checklist. In a June 2020 notice, DFS set out two practices that still apply. It starts substantive review only when every checklist item is in and each looks adequate on its face. It may deny an application, without further notice, if a set of requirements (it names BSA/AML, cybersecurity and background checks) is still open after the third deficiency letter. Once DFS deems the file complete, 200.6(b) gives it 90 days to approve or deny, and it can extend that period.
Section 200.4 lists the contents. The parts the CTO and CISO own are:
- All written policies and procedures that Part 200 requires (200.4(a)(10)). This means compliance, AML, cybersecurity, BCDR, complaints and the rest, before you have a licence.
- The methodology for valuing virtual currency in fiat (200.4(a)(14)). The $3,000 and $10,000 thresholds in 200.15 are measured with it, and you must notify DFS before you change it (200.14(d)).
- Banking arrangements and a description of products, websites and jurisdictions (200.4(a)(8)–(9)).
- A demonstration that you will comply with Part 200 on the day you are licensed (200.4(b)). DFS may grant a conditional licence that expires after two years unless renewed (200.4(c)).
DFS reviews coin listing separately. A licensee may offer coins DFS has approved for it, coins on the DFS Greenlist, or coins it self-certifies under a coin-listing policy that DFS has approved. Under the November 2023 guidance, DFS will not approve a listing policy without a delisting policy. Each new market on your exchange is therefore a governed listing decision.
What does Part 200 require from your systems?
Records (200.12). Keep all books and records in their original form or native file format for at least seven years. For each transaction, record the amount, the date and precise time, any payment instructions, the fees, and the names, account numbers and addresses of the customer parties and, where practicable, the other parties. DFS gets immediate access to records “wherever located” (200.12(b)) and examines each licensee at least once every two calendar years (200.13(a)).
Customer assets (200.9). Hold virtual currency of the same type and amount that you owe customers. Do not lend, pledge or otherwise use it except at the customer’s direction. The September 2025 DFS custody guidance adds detail. Customer assets are segregated on-chain and on the internal ledger, in per-customer or omnibus wallets that hold only customer assets. The licensee is “prepared at all times to demonstrate reconciliation” between its books and the chain. A new sub-custodian is a material change that needs prior approval.
AML (200.15). The AML program is based on a yearly risk assessment and is tested every year by people independent of it, with a written report to DFS. The rule also requires:
- identity verification for any transaction over $3,000;
- notice to DFS within 24 hours of crypto-to-crypto transactions above $10,000 in one day by one person that federal currency reporting does not already cover;
- OFAC screening, and no transfers that conceal a customer’s identity (200.15(g)).
DFS’s April 2022 blockchain analytics guidance asks licensees to use analytics in KYC, on-chain transaction monitoring and on-chain sanctions screening, whether they build the tools or buy them.
Cybersecurity (200.16). The licensee needs a board-approved policy covering 13 named areas, including access controls, BCDR, capacity planning, application development, vendor management, incident response, and “monitoring and implementing changes to core protocols” it does not control (a chain fork, for example). It must also have:
- a CISO who reports to DFS each year;
- penetration tests at least once a year and vulnerability assessments at least once a quarter;
- an audit trail that can reconstruct every financial transaction, is protected from tampering, and logs every access to the audit system and every system administrator action.
Continuity (200.17). A written BCDR plan with off-site backups and back-up facilities. Independent staff or a third party test it every year, and DFS is told promptly of any disruption that affects regulatory obligations.
Customer-facing rules (200.18–200.20). Written risk disclosures go out before the first transaction with a customer (200.19). Advertising carries the DFS legend and is archived for seven years (200.18). Complaint contacts and the DFS address appear on the website (200.20).
Change control (200.10). A materially new product or a material change to an existing one needs DFS’s prior written approval. This affects your release planning more than any other rule. Earn, staking, a new chain or a new custody provider can all count as material, so map your product roadmap against it before you sign up customers.
What does Part 500 add?
Part 500 applies to every person licensed under the Banking, Insurance or Financial Services Law (500.1). A BitLicensee is therefore a covered entity, in addition to section 200.16. Its second amendment set new duties from 1 November 2023, and the last transitional dates passed in November 2025 (500.22). Several rules shape the system design:
- 72-hour notice. Notify DFS no later than 72 hours after determining that a cybersecurity incident has occurred, including one at a third-party service provider (500.17(a)).
- Yearly certification. By 15 April each year, the highest-ranking executive and the CISO sign either a certification of material compliance or an acknowledgement that lists the gaps and a remediation timeline (500.17(b)).
- MFA for everyone. Multi-factor authentication for any individual accessing any information system, unless a limited exemption applies (500.12).
- Asset inventory. Each system is listed with its owner, location, classification, support end date and recovery time objective (500.13).
- Vulnerability management. Penetration testing from inside and outside at least once a year, and automated scans at a risk-based frequency and after material changes (500.5).
- Vendors. Due diligence and contract terms on access controls, MFA, encryption and incident notice for each third-party service provider (500.11). Your exchange software vendor, hosting provider, KYC provider and analytics provider are all on that list.
The DFS virtual currency page also lists Part 504, the transaction monitoring and filtering rule. We could not retrieve its text. Ask counsel whether it applies to you through a money transmitter licence.
Which controls and evidence will DFS look for?
The first column is the rule, paraphrased. The other columns are our implementation recommendation, based on building and running exchange, wallet and custody software at the reference exchange since 2024. DFS does not prescribe these controls.
| Requirement (citation) | Control in the platform | Evidence | Owner |
|---|---|---|---|
| Records in native format for 7 years, with precise transaction times (200.12) | Double-entry ledger with timestamps; retention set to seven years, with no deletion jobs on records | Retention configuration; sample export | CTO |
| Audit trail that can reconstruct transactions and logs admin actions (200.16(e)(2)) | Append-only operator log; database and server admin actions logged separately | Log export; reconstruction test of one transaction | CISO |
| Same type and amount held for customers; reconciliation on request (200.9(b); 2025 guidance) | Daily ledger-to-chain reconciliation for each asset; customer and company wallets kept apart | Reconciliation reports; wallet map | CFO, CTO |
| Identity check above $3,000; $10,000 daily crypto-to-crypto notice (200.15(h)(4), (e)(2)) | KYC tiers that gate limits; daily aggregation of each person’s transactions by value | Tier rules; aggregation report | MLRO |
| On-chain monitoring and sanctions screening (200.15; 2022 guidance) | Address screening on deposits and withdrawals; risk-based holds; case log | Alert and case records | MLRO |
| Pen test yearly, vulnerability assessment quarterly (200.16(e)(1); 500.5) | Test calendar linked to releases; remediation tracker | Reports; remediation status | CISO |
| MFA for every person (500.12) | 2FA enforced for customers and staff; hardware keys for privileged roles | Configuration; access review | CISO |
| 72-hour incident notice (500.17(a)) | Incident register with a “determined” timestamp; notice template | Register; drill record | CISO |
| BCDR plan tested yearly (200.17) | Standby environment; restore drill on clean hardware | Timed drill report | CTO |
| Prior approval of material changes (200.10) | Release process that flags new products, chains and providers for compliance review | Change log with sign-off | Compliance |
What do the rules not spell out?
We did not find these in Part 200 or Part 500. Confirm them with counsel; until then, treat them as good practice:
- Server location. We found no rule that requires servers in New York or the United States. DFS must get immediate access to records wherever they are, and a vendor-run environment is a third-party service provider under 500.11.
- Key management design. The rules require you to protect the assets and hold the same amounts you owe. They do not prescribe multisig, MPC or HSMs. DFS will judge your design through the custody guidance and the cybersecurity program.
- Recovery time targets. Section 200.17 requires recovery “as soon as reasonably possible”, and 500.13 makes you record a recovery time objective for each asset. Neither sets a number.
BitLicense FAQ
How much does a BitLicense cost?
The application fee is $5,000 and is not refunded. Add a surety bond or trust account that DFS says is generally at least $500,000, capital that DFS sets for your business, and a yearly assessment. From the FY 2026-27 DFS chart, we estimate the assessment at about $189,000 for a licensee with no volume and about $385,000 for one in the smallest bands.
How long does a BitLicense application take?
DFS must decide within 90 days after it deems the application complete, and it may extend that period. The 90 days start only after every checklist item is in. DFS may deny an application if a requirement is still open after the third deficiency letter.
Does a crypto software vendor need a BitLicense?
Not for software alone. DFS says that developing and distributing software as a purely technical service does not need a BitLicense in itself. The operator that holds customer assets or runs the exchange does.
Does a BitLicense cover US dollar transfers?
No. A BitLicensee that transmits fiat currency also needs a New York money transmitter licence. A limited purpose trust company can transmit money without one.
Does Part 500 apply to BitLicensees?
Yes. Part 500 applies to anyone licensed under the Financial Services Law, which includes BitLicensees, on top of the cybersecurity section of Part 200. It brings the 72-hour incident notice, the 15 April certification and MFA for all users.
How BitPolaris helps
BitPolaris builds the exchange and custody software that has run in production at the reference exchange since 2024. The exchange has an operations console with roles, an audit log and reports, KYC tiers with Sumsub or Didit, and travel-rule data capture with an export for your travel-rule provider. Custody adds hot, warm and cold tiers, M-of-N approvals, address whitelists with delays, a reserve monitor that compares the ledger with the blockchain around the clock, and an exportable operator log. Custody is self-hosted only, so key generation, storage and recovery stay with you. The self-hosted exchange licence is €24,500 one-time plus €4,900 a year for updates and support, and custody is €14,000 when bought with the exchange (excluding VAT, pricing). Self-hosted also means the software vendor has no standing access to your systems. It is still a third-party service provider for the due diligence in 500.11.
The Licence Technical Pack does not cover New York. We supply the software and the evidence it produces (logs, reports, reconciliations). Your counsel and compliance team prepare the application. Blockchain analytics, penetration tests, the CPA audit and the independent AML test come from third parties. Background: what regulators ask for, the MiCA CASP ICT and custody sections and what custody software includes.
We are not a law firm and do not file applications. Installing our software does not make anyone licensed or compliant; DFS decides.
BitPolaris builds the exchange and custody software with the ledger, audit log, reconciliation reports and operator records that Part 200 asks a licensee to keep. Self-hosted, so keys and records stay in your perimeter.
Sources
- 23 NYCRR Part 200 (Virtual Currencies), §§ 200.2–200.21, Cornell LII (official text: NYCRR on Westlaw), read 12 November 2026
- 23 NYCRR Part 500 (Cybersecurity Requirements for Financial Services Companies), §§ 500.1, 500.5, 500.11, 500.12, 500.13, 500.17, 500.22, Cornell LII, read 12 November 2026
- DFS, Virtual Currency Business Licensing: applicant information, BitLicense FAQs, regulated entities, Greenlist, read 12 November 2026
- DFS, Annual Assessment of Virtual Currency Businesses and the FY 2026-27 Quarter 3 assessment chart, read 12 November 2026
- DFS, Notice of Virtual Currency Business Activity License Application Procedures, 24 June 2020, read 12 November 2026
- DFS, Updated Guidance on Custodial Structures for Customer Protection in the Event of Insolvency, 30 September 2025, read 12 November 2026
- DFS, Guidance on Use of Blockchain Analytics, 28 April 2022, read 12 November 2026
- DFS, Guidance Regarding Listing of Virtual Currencies, 15 November 2023, read 12 November 2026
- 31 CFR 1010.410(f) and 31 CFR 1022.380, eCFR: § 1010.410, § 1022.380, read 12 November 2026
- FinCEN, FIN-2019-G001, Application of FinCEN’s Regulations to Certain Business Models Involving Convertible Virtual Currencies, 9 May 2019, FinCEN PDF
- New York Banking Law, Article 13-B (money transmitters), read 12 November 2026