In brief
- Fireblocks sells a software platform, and two US subsidiaries sit beside it: Fireblocks LLC, on FinCEN’s list as a money transmitter, and Fireblocks Trust Company, LLC, a New York custody entity; their services need a separate onboarding and contract.
- Fireblocks LLC’s own 47-row table lists 39 licences in 38 jurisdictions; on 29 September 2026 we matched Connecticut and Texas against state records, could not open California’s or Florida’s, and did not attempt the other 43.
- The public pages we checked do not name the entity that signs the software contract, or say which payment products, if any, run under Fireblocks LLC’s licences.
Reader question: is Fireblocks just software, or a licensed money transmitter, and which entity am I contracting with for payments?
Fireblocks sells wallet and custody software to exchanges, banks and payment companies, plus a Network for Payments linking them to third-party on- and off-ramps, OTC desks and banks. Its payments page says it “provides technology infrastructure only”, yet a subsidiary publishes a table of state money-transmitter licences.
Entity and authority
| Entity | Role | Status (29 September 2026) |
|---|---|---|
| Fireblocks Inc. | Named with “its affiliates” in the privacy policy | Company-reported; state of incorporation not publicly disclosed |
| Fireblocks LLC (Boston) | Money transmission, crypto trading support (company-reported) | FinCEN MSB entry verified (received 5 May 2026, trading as “Fireblocks Payments Services”) |
| Fireblocks Trust Company, LLC (New York) | Digital asset custody (background: how exchange hacks happen and what protects users) | FinCEN MSB entry verified (19 December 2025); NYDFS limited purpose trust charter company-reported (NYDFS page returned HTTP 403) |
| FIREBLOCKS UK INT’L LIMITED (13650687) | UK company, SIC “other software publishing” | Status “Active” on Companies House; no FCA check made |
The regulated-entities page says these services “are not included with the Fireblocks software platform and require customers to undergo a different onboarding and contracting process.” The website terms (Israeli law, Tel Aviv courts) name no entity. No Fireblocks entity is on the OCC’s pending applications list or in ESMA’s interim MiCA register (see ESMA’s 2027 MiCA supervision plans).
What the licence table shows
Fireblocks LLC’s regulated-entities page (last modified 10 August 2026) lists 47 jurisdictions (46 states and DC). We parsed every row. On 29 September 2026 Connecticut and Texas records matched the company entries; California’s DFPI page was blocked (HTTP 403) and Florida’s OFR search did not connect. The other 43 rows’ registers were not attempted. We did not use NMLS (CAPTCHA, and terms that bar automated use), so those licences could not be verified. FinCEN, checked separately, shows federal MSB registration, not state licensing.
| Group in the company table | Rows | Matched | Tried, not accessible | Not attempted |
|---|---|---|---|---|
| Licence with a stated number | 30 | 2: Connecticut MT-2066055 (list dated 2 September 2026); Texas 3546 (Open) | 1: Florida | 27 |
| Licence listed, number shown as “N/A” | 8 (9 licences; Louisiana lists two) | 0 | 0 | 8 |
| Asterisked: state “does not currently regulate” the services, or no-action letter | 9 (CA, CO, IN, MA, MO, MT, NC, UT, WI) | 0 | 1: California | 8 |
| Total | 47 | 2 | 2 | 43 |
Neither matched record contradicts the company entry; the other 45 rows are neither confirmed nor contradicted. The Tennessee disclosure says Fireblocks LLC’s licence and surety bond “do not cover the transmission of virtual currency”. New York, Alaska, Hawaii and Virginia have no row, yet the page gives complaint routes for all four, including NYDFS for “Fireblocks LLC’s money transmission activity”, without explaining why.
Product scope, eligibility and use
The company says the Network for Payments went live on 4 September 2025 with “more than 40 providers”, among them Bridge, Circle and dLocal. Our static capture of the directory (29 September 2026) lists 11, three “Coming soon”; the page may load more by JavaScript, so the total is not yet verified. The directory calls providers “independent third parties” and helps customers “create an account” with each. We infer, though no page states it, that each provider needs its own contract. The Agentic Payments Gateway for PSPs has a company-reported launch (20 May 2026); production availability and customer use are not independently verified.
Fireblocks says it “does not provide regulated services in the EEA”. That does not settle whether EEA businesses can use the software or partner services, and no page we checked lists eligible contracting countries or providers. Evidence of use is company-reported (Trust custody clients Castle Island, FalconX, Bakkt and Galaxy; a “core technology partners” role in Wyoming’s state stablecoin) and does not show production use of the payments network. Banks are building rivals, such as the stablecoin checkout Citi and Coinbase launched for corporate clients.
Payment roles and unresolved requirements
| Role | What Fireblocks’ pages say | Status |
|---|---|---|
| Keys and control of assets | “MPC-secured keys”; embedded wallets “non custodial” | Who controls assets at each payment stage: not publicly disclosed |
| Qualified custody | Fireblocks Trust: assets “fully segregated”, “bankruptcy-remote” | Deposit-insurance status: not publicly disclosed (Trust page) |
| On- and off-ramps, FX, local payouts | Delivered by partners “under their own regulatory licenses” | Company-reported |
| Example flow: Circle Payments Network | USDC leaves the customer’s Fireblocks wallet, recipient gets local fiat; Fireblocks “handles provider connectivity” | Company-reported (July 2026) |
| Money transmission by Fireblocks LLC | “money transmission services on behalf of customers” | Which products use it: not publicly disclosed |
| Supported assets | 60+ fiat currencies; USDC, USDT, PYUSD; BTC, ETH, XRP | Per-provider lists: not yet verified |
| Banks behind settlement | None named for Fireblocks itself | Not publicly disclosed |
| Onboarding and pricing | Separate onboarding for regulated entities; an account per provider | Requirements: not publicly disclosed; pricing page: not yet verified (not captured) |
| Stablecoin issuer and reserves | Technology or infrastructure partner in the Wyoming and Open USD launches | Not applicable (not an issuer profile) |
Company scale figures
Fireblocks described US$300 billion a month as “payment flows over the Fireblocks Network” in September 2025 and as “stablecoin transactions” (up 300% year on year) in April 2026. Neither post defines the figure, so no trend follows. Asset figures also vary by page (US$10 trillion or US$16 trillion protected). All are company-wide; none measures payments handled by Fireblocks LLC.
Alternatives
| Check (29 Sep 2026 unless stated) | Fireblocks | BitGo | Anchorage Digital |
|---|---|---|---|
| On the OCC’s active trust bank list (31 August 2026) | No; no pending application either | Yes, BitGo Bank & Trust, N.A. (25366) | Yes, Anchorage Digital Bank, N.A. (25243) |
| Entity on FinCEN’s MSB list | Fireblocks LLC; Fireblocks Trust Company | BitGo Technologies LLC | None found by name search |
| On Connecticut’s money-transmitter list (2 September 2026) | Fireblocks LLC | BitGo Technologies LLC (MT-2644116) | None found by name search |
| Public page mapping services to entities | Lists entities, not which products use them | Not checked | Yes: custody via the bank, trading via Anchorage Hold, LLC; not marketed outside the US and Singapore |
The records separate legal structures only: BitGo and Anchorage have OCC-listed trust banks, and Anchorage names the entity behind each service; Fireblocks reports a New York trust charter (not confirmed with NYDFS) and holds state licences in a separate LLC. They do not show which offers better payment connectivity, and absence from a register we searched is not evidence of weaker authority. Fireblocks’ public materials leave the payment-product contracting entity unresolved.
Limitations and unknowns
- Entity signing the platform contract: not publicly disclosed (terms of use, privacy policy, deployment terms, regulated-entities page checked).
- Which payment products use Fireblocks LLC’s licences: not publicly disclosed (payments page, directory, regulated-entities page checked); its FinCEN trade name does not settle it.
- NYDFS trust charter: company-reported; register check on 29 September 2026 blocked (HTTP 403), not yet verified.
- State licences beyond CT and TX: could not be verified (see table). Why four states have no row: not publicly disclosed.
- UK FCA status: not yet verified; parent jurisdiction: not publicly disclosed.
Key facts (as of 29 September 2026)
- On FinCEN’s MSB list: Fireblocks LLC, Fireblocks Trust Company, LLC
- Licence table: 47 rows, 39 licences; 2 matched (CT, TX), 2 inaccessible, 43 not attempted
Sources
- Fireblocks: Regulated entities, Payments, Network for Payments directory, Fireblocks Trust, Circle Payments Network post
- FinCEN: MSB Registrant Search (full list, 29 September 2026)
- State registers: Connecticut Department of Banking, Texas Department of Banking entity search
- OCC: digital-asset licensing applications, active trust banks; ESMA interim MiCA register
- Comparison: Anchorage legal disclosures
Last updated: 30 September 2026 (register checks dated 29 September 2026). Next recheck triggered by: a change to the regulated-entities page, a new Fireblocks FinCEN filing, any NYDFS or state action on either US entity, an OCC, MiCA or FCA application, or a change to the “technology infrastructure only” wording.
