zerohash supplies embedded digital-asset infrastructure for banks and financial platforms. Its APIs provide execution, account funding and transfer capabilities behind a partner’s application. The operating entity, customer territory, approved assets and wallet permissions determine the available transaction paths.[1][7]
EU Account Funding through zerohash B.V. has a stated release date of 14 October 2026; its announcement was posted on 20 October. USD conversion is available in that release, while EUR conversion remains described as coming soon. Account linking and jurisdictional onboarding rules have their own release schedules.[4][3][9]
Services and customers
Sections ↑Embedded transaction products
| Product | Current documented role | Relevant qualification |
|---|---|---|
| Trade and liquidity APIs | Crypto exchange and conversion capabilities embedded inside platforms. | Assets, entity and execution fee structure are platform specific.Source 1 |
| Account Funding | End-user crypto deposits converted to fiat within platform workflows. | EU B.V. available; USD conversion now, EUR identified as coming soon in the release.Source 4 |
| AUTH account linking | Link external exchange or wallet sources to funding and transfers. | Supported destinations and permissions are not universal.Source 3 |
| Withdrawals | Convert balances and send crypto to linked external wallets. | Recipient screening and Travel Rule approval may block initiation.Source 4 |
AUTH connects a customer’s external custodial account or self-custodial wallet and obtains approval for each transfer. In Account Funding, crypto is converted to or from a fiat balance. In Crypto Transfers, the platform balance remains in crypto. Platforms configure eligible connections, assets and transfer types.[3]
EU inbound and outbound compliance checks occur at different stages. A deposit can arrive before all sender information is available and enter a remediation hold. An outbound transfer with missing recipient information is blocked before a withdrawal, quote or payout request is created.[4]
Platforms, connectivity and integrations
Sections ↑API and state-management requirements
| Integration | Documented behaviour | Implementation concern |
|---|---|---|
| Sandbox and production | Separate testing and live environments using signed authenticated calls. | Secrets, permissions, entity-specific base URLs and release pinning.Source 2 |
| EU Travel Rule hold | Qualifying deposits may remain pending up to 48 hours for missing sender information. | Pending balances, customer remediation and failed-deposit recovery.Source 4 |
| Withdrawals checks | Payout cannot be initiated before required recipient data is confirmed. | Do not display it as already onchain or settled.Source 4 |
| AUTH | Linked external accounts and wallet permission flows. | Connection revocation, eligible destinations and customer consent.Source 3 |
The EU deployment uses a dedicated API environment and endpoints for Travel Rule data submission and state approval. Webhooks and polling need to distinguish deposited, pending, credited, failed and recovery states. An onboarding screen that simply treats receipt of a transaction hash as final account funding can materially misstate the customer’s available funds.[4][2]
For high-value USDC deposits, the release notes describe a pending-settlement status distinct from processed/fully settled. This means a platform has to support delayed completion, not merely an instantaneous credit expectation. The threshold for those flows may vary and platform-specific activation is needed.[10]
Pricing, fees and commercial terms
Sections ↑Charges and availability
| Layer | Public documentation | Commercial diligence |
|---|---|---|
| Execution and conversion | EU pricing methodology is public; spreads and commissions depend on the platform arrangement. | Firm quote, expiry period, separate commission and partner-added fees.Source 11 |
| Blockchain transfers | Network charges may differ by asset and transfer method. | Fee payer, network choice and failed transaction handling.Source 2 |
| Stablecoin issuer fees | Release notes expose issuer_fee_amount, rate and payor; configured platform invoiced monthly. | Whether and how the partner passes on permitted charges.Source 8 |
| EU account funding | Available to eligible B.V.-onboarded platforms. | Country, participant and quote eligibility.Source 4 |
The issuer-fee release specifies an implementation date of 26 August 2026. For configured stablecoins, zerohash records issuer mint/burn costs per funding event and invoices the platform monthly while crediting the customer’s full deposit notional. These issuer fees are not directly deducted from the customer through that feature; a platform seeking to recover them can use the separate Account Funding transaction-fee mechanism.[8]
EU execution and pricing model
| Service | Published methodology |
|---|---|
| RFQ | A time-limited firm quote includes the liquidity price and spread. A separately disclosed commission may apply; quote duration is configured per platform.Source 11 |
| CLOB | Price/time priority and supported order types; commission is agreed with the platform. Execution can span several price levels.Source 11 |
| OTC | ZHEU acts as principal and sole legal counterparty, with an agreed all-in quote. This disclosed service is arranged outside the API and trading-platform rules.Source 11 |
| Partner access | The published policy says an individual platform operator offers either RFQ or CLOB to its customers. Example spreads and commissions are illustrations, not a universal tariff.Source 11 |
Implementation and operating requirements
Sections ↑The platform should start by documenting the participant onboarding country, legal operating entity, intended asset/network, custodial model and permitted entry and exit path. Sandbox success is necessary but not sufficient: the same transaction may fail production eligibility screening. The customer onboarding funnel should disclose restrictions before funds are deposited.[2][7]
The 12 October 2026 jurisdiction notice distinguishes new and existing UAE participants. New submissions are declined unless located in DIFC or ADGM. Existing participants must sell or withdraw by 12 November unless located in those financial centres or holding a UAE cryptocurrency licence. The additional licence exception appears in the existing-participant rule and should not be assumed to authorise new onboarding.[9]
Support, complaints and incident response
Sections ↑The developer portal links integration documentation, support and live service status. The platform agreement sets escalation for delayed webhooks, compromised wallets, Travel Rule remediation, asset recovery and fee disputes.[2][4]
A customer’s primary consumer helpdesk will often be the embedding platform, not zerohash. The parties need a clear escalation boundary for rejected participants, failed conversions, blockchain reorganisation and blocked compliance payments.[1][4]
Published contact routes
Scope Official status destination linked by the integration guide; current incident state was not separately tested.
Regulatory permissions and entity scope
Sections ↑The US company disclosures identify zerohash LLC and NMLS 1699379, with state-specific money-transmission and virtual-currency permissions. They explicitly state that its Indiana money-transmitter licence does not cover virtual-currency transactions. FinCEN MSB registration and state money transmission are distinct from securities brokerage authorisation.[6][7]
The EU release names zerohash B.V. as the operator for relevant European account-funding flows. The group should be scoped by exact entity, end-customer territory, regulated product and version; even within that flow, transaction compliance and supported fiat conversions have explicit restrictions.[4][5]
Company background and contracting identity
Sections ↑zerohash operates business-to-business embedded infrastructure, with Chicago headquarters in its published corporate disclosures. It supplies behind-the-scenes digital-asset transaction features to other applications rather than necessarily maintaining their customer-facing brand or support operation.[1][7]
The corporate disclosures identify a Chicago office and separate jurisdictional terms. For EU trading, the published pricing policy names zerohash europe BV (ZHEU); the Account Funding release uses zerohash B.V. The signed platform agreement and applicable customer terms establish which group entity supplies each service.[7][11][4]
- Operator
- zerohash LLC and the applicable US or European operating affiliate, including zerohash B.V.
- Service scope
- Partner APIs and SDKs for embedded digital-asset execution, custody-related flows, stablecoins and crypto-to-fiat account funding, with country and entity-specific product availability.
- Customer types
- Fintech and broker platforms; Banks and payment applications; Wallet and trading applications; Stablecoin and crypto payment businesses
- Delivery
- API; Hosted; SaaS
- Pricing publication
- Quote only
- Headquarters
- Chicago, Illinois, United States
- Platforms
- zerohash Embedded Infrastructure; Account Funding SDK and API; AUTH account linking; Crypto withdrawals; Liquidity API
- Integrations
- REST API; Webhooks; Wallet connections; Travel Rule API; Funding SDK
- Pricing scope
- Platform-specific fees and spreads, blockchain/network charges and issuer mint/burn charges may be separate. No one universal retail percentage applies to all accounts, platforms and jurisdictions.
- Implementation
- Cert/sandbox and production environments, credentials and signed API integration are documented. A platform must configure identity/participant onboarding, webhook state machines, compliance, wallet permissions and available assets. EU Travel Rule remediation and US financial partner eligibility change the end-customer journey.
- Support
- Developer documentation, platform relationship representatives and a public service-status page. Contracted support allocates incident handling, recovery, compliance remediation and fee disputes between zerohash and the embedding platform.
- Permissions and regulatory scope
- zerohash LLC identifies NMLS 1699379 and US money-transmission arrangements; group disclosures name different jurisdictional entities. zerohash B.V. supports specific EU account-funding flows, but supported country, participant type and transaction products require confirmation. FinCEN MSB registration is not an SEC broker-dealer licence.
Provider metadata checked 22 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 6Source 7Source 8Source 9Source 10Source 11
Additional Information
Sections ↑Before embedding the service, test an ineligible participant, a missing Travel Rule sender declaration, a large deposit awaiting settlement, an unsupported chain, a revoked AUTH link and an outbound wallet whose recipient data has not cleared. Those cases distinguish a production-ready funds workflow from a passing API demo.[3][5][4]
Sources & further reading
- Embedded crypto and stablecoin infrastructure zerohash · Accessed 22 Oct 2026
- Getting started with sandbox and production API zerohash Developer Docs · Accessed 29 Oct 2026
- AUTH account linking documentation zerohash Developer Docs · Accessed 29 Oct 2026
- Account Funding available in EU through zerohash B.V. October 2026 zerohash Developer Docs · Accessed 29 Oct 2026
- zerohash product release notes and October jurisdiction restriction zerohash Developer Docs · Accessed 29 Oct 2026
- US licences and disclosures zerohash · Accessed 29 Oct 2026
- zerohash regulatory, legal and operator disclosures zerohash · Accessed 29 Oct 2026
- Release-note documentation for issuer fees in Account Funding zerohash Developer Docs · Accessed 29 Oct 2026
- October 2026 jurisdiction restrictions and UAE exceptions zerohash Developer Docs · 12 Oct 2026 · Accessed 29 Oct 2026
- High-value Account Funding deposit release zerohash Developer Docs · 18 Aug 2026 · Accessed 29 Oct 2026
- EU RFQ, CLOB and OTC pricing methodology zerohash · Accessed 29 Oct 2026
This profile reports dated public information, including provider-published services and terms. It does not independently test or guarantee service delivery, integrations or performance. Inclusion is not an endorsement. Permissions and protections apply only to the named legal entity, service and client category; check the current official records and your contract.