Account Funding Available through zerohash B.V. (EU entity)
Release Details
Release Date: October 14, 2026
Release Type
New product availability – optional action from platforms
Summary
Account Funding is now live in the EU through zerohash B.V., zerohash’s EU entity.
EU Account Funding
Platforms onboarded through zerohash B.V. can integrate either the Account Funding SDK or the Account Funding API, which lets end customers fund their accounts with crypto that is converted to fiat. Includes support for:
- Transaction Limits
- Conversion to USD
- Conversion to EUR (coming soon)
EU Account Funding Withdrawals
Platforms onboarded through zerohash B.V. can integrate either via SDK or API to enable Account Linking and Withdrawals. This lets Account Funding end customers convert fiat balances to crypto and withdraw them to their linked external wallets.
EU Travel Rule Compliance & Remediation Flows
Account Funding Deposits
EU Travel Rule compliance is built in. Every qualifying EU crypto deposit is screened for the sender’s Travel Rule information.
- Information verified: the deposit is credited and converted to fiat right away.
- Information missing: the deposit is held as pending for up to 48 hours while the end customer submits the missing sender information. Once it’s validated, the deposit is credited and converted. If no valid information is submitted within 48 hours, the deposit fails and enters fund recovery.
Two options for collecting missing Travel Rule information from the end customer:
- A fully zerohash-hosted Travel Rule information recovery experience, with no collection UI to build on your end. Available to Platforms integrated via API and SDK.
- In the Account Funding SDK: a “Pending deposit” screen with a “Provide information” button opens the Travel Rule flow.
- Through the EU Secondary Portal: end customers receive a “Deposit Pending, Action Required” email that links to a zerohash europe branded portal where they can see pending deposits and the time left to verify, then submit information.
- Build your own Travel Rule information recovery experience using zerohash APIs, with full control over the UI and the end-to-end flow. Submit information via API. Only Available to Platforms integrated via API.
Account Funding Withdrawals
EU Travel Rule compliance is built into withdrawals. Before a withdrawal starts, the receiving wallet is screened for the recipient’s Travel Rule information.
- Information verified: the withdrawal proceeds as normal.
- Information missing: the withdrawal is blocked until the end customer provides the recipient’s information. No withdrawal, quote, or payout request is created and no funds move until the information is confirmed.
Two options for collecting missing Travel Rule information from the end customer:
- A fully zerohash-hosted Travel Rule collection experience, with no collection UI to build on your end. Available to Platforms integrated via SDK.
- In the Crypto Withdrawals SDK: when the end customer enters a receiving wallet and clicks “Continue” on the review screen, the SDK checks the wallet’s Travel Rule status. If information is missing, it opens the Travel Rule flow. Afterwards the end customer reconfirms the quote and the withdrawal proceeds.
- In the Account Link SDK: when the end customer links a receiving wallet, the SDK checks its Travel Rule status and opens the Travel Rule flow if information is missing. Wallets linked this way are ready for Fund Out and Payouts. Travel Rule information on the receiving wallet must be fully collected before you can open the Fund Out and Payouts SDKs. If it isn’t, the SDK returns an error, and you should re-open the Account Link SDK to collect it.
- Build your own Travel Rule collection experience using zerohash APIs, with full control over the UI and the end-to-end flow. Submit information via API before calling POST /withdrawals/requests, POST /payments or a withdrawal SDK. Available to Platforms integrated via API and SDK.
Endpoints Impacted
| Endpoint | Update |
|---|---|
| POST /fund/rfq | Available in the EU environment (api.zerohash.eu). Deposits made to the returned address are subject to Travel Rule screening. |
| POST /travel-rule/submit | New endpoint. Submits Travel Rule information about the owner of a crypto address. Use it to whitelist self custody wallets for deposits and withdrawals, or provide missing travel rule information. |
| GET /travel-rule/state-approval | New endpoint. Returns whether a deposit or a planned withdrawal can go ahead under the Travel Rule and, if it cannot, what information is still needed. Use it to identify whether Travel Rule information provided is sufficient. |
| GET /travel-rule/vasps | New endpoint. Lists the Virtual Asset Service Providers (VASPs) that zerohash can exchange Travel Rule data with. Use it to identify the appropriate casp-id when submitting travel rule information for an Exchange via POST /travel-rule/submit |
| Account Funding webhooks | New webhooks for handling deposits received missing Travel Rule information on the sending wallet. |
| Deposit/Withdraw webhooks | New webhooks for handling deposits received missing Travel Rule information on the sending wallet. |
Relevant Documentation
- Account Funding SDK EU Integration Guide
- navigate to 'EU Integration Guide' tab
- Account Funding API EU Integration Guide
- navigate to 'EU Integration Guide' tab
- Account Funding Withdrawals EU Integration Guide
- navigate to 'EU Integration Guide' tab
- Travel Rule Remediation Guide
- Account Funding webhooks
- Deposit/Withdraw webhooks