Release date

June 11th, 2025

Release type

Informational – Optional action from platforms.

Summary

Zero Hash now supports the following Polkadot Asset Hub assets on our platform:

• DOT (native token)
• USDC
• USDT

This includes the ability to deposit, hold and withdraw funds on the native chain of these assets.

📘

USDT not available in CERT environment

Note that USDT is not available in CERT for testing. We recommend use USDC instead for CERT testing.

NY supported

Only the asset DOT is supported in NY State. USDC and USDT on Asset Hub are NOT supported on NY State.

Action required

No action required by the platforms, these assets are enabled automatically for your use.

Endpoints impacted

No endpoints impacted. When the asset is required on an action, just use the proper notation:

• DOT.DOTHUB
• USDC.DOTHUB
• USDT.DOTHUB

Relevant documentation

• https://docs.zerohash.com/page/cert-environment-assets
• https://docs.zerohash.com/page/what-assets-do-you-support-two

Release date

2025-06-03

Release type

Informational – Optional action from platforms.

Summary

The endpoint to add accounts for the CLOB now works for NNPs.

Action required

No actions required from Platforms.

Endpoints impacted

• POST /clob/accounts

Relevant documentation

https://docs.zerohash.com/reference/post_clob-accounts

Release type

Informational – Optional action from platforms.

Summary

A new field was added to the participants information sharing endpoint:

• Metadata (object): Can be used to submit any additional unstructured metadata

This field will relay the content of metadata sent by the platform when creating the participant. This field is part of the participant creation endpoint and entity creation endpoint.

The information now is incorporated into the following endpoint payload:

• GET /participant/{participant_code}/full_info

Action required

No action needed from platforms. The field will be included on the payload as described.

Platforms who want to access the Full Information endpoint need to contact client support to have this endpoint enabled.

Endpoints impacted

• GET /participant/{participant_code}/full_info

Relevant documentation

• https://docs.zerohash.com/reference/get_participant-participant-code-full-info
• https://docs.zerohash.com/changelog/participant-information-sharing-with-platform#summary

Jun 3, 2025

Release type

Informational – Optional action from platforms.

Summary

There is a new endpoint under the Participant information sharing endpoints that allows the platform to access the information of Control Persons or Ultimate Business Owners of an entity with a participant code in Zero Hash.

• GET /participant/{participant_code}/full_info/cp_bo
• GET /participant/{participant_code}/sanction_screening_info/cp_bo
• GET /participant/{participant_code}/basic_info/cp_bo

This endpoint will provide the Control Person / Ultimate Business Owner information according to the PII access level the platform is certified for.

For more information on this, refer to the following documentation:

https://docs.zerohash.com/changelog/participant-information-sharing-with-platform#summary

Action required

No action needed from platforms. The endpoint will be available upon release.

Platforms who want to access the Full Information endpoint need to contact client support to have this endpoint enabled.

Endpoints impacted

• GET /participant/{participant_code}/full_info/cp_bo
• GET /participant/{participant_code}/sanction_screening_info/cp_bo
• GET /participant/{participant_code}/basic_info/cp_bo

Relevant documentation

• https://docs.zerohash.com/reference/get_participant-participant-code-full-info
• https://docs.zerohash.com/changelog/participant-information-sharing-with-platform#summary

Release Details

Release Date: June 2nd, 2025

Release Type

Informational – optional action from platforms

Summary

Zero Hash is pleased to announce the launch of the Payouts SDK - an embeddable, low-code widget that allows Platforms to offer stablecoin (and crypto) payouts to their end customers.

Use Cases

• Gig economy payouts: Instantly pay freelancers, creators, and contractors in stablecoins or crypto - no more waiting days for bank transfers.
• Marketplace payouts: Let sellers withdraw earnings in stablecoins or crypto for faster, global, low-fee access to their funds.
• Cross-border payroll: Pay remote teams or international employees without the friction of traditional banking rails.
• Creator economy: Enable platforms like streaming services, music apps, or influencer platforms to pay creators in real-time using stablecoins or crypto.
• Affiliate & partner rewards: Instantly settle commissions and partner earnings globally with fewer currency conversion headaches.
• DeFi and crypto-native platforms: Add stablecoin or crypto payouts for dApps or web3 tools that need to distribute funds or earnings.

How it works

• See end to end integration guide here

Release Details

Release Date: May 12th, 2025

Release Type

Informational – optional action from platforms

Summary

Trade status and balance updates are now available via webhooks. This enhancement provides more granular and timely information on trade settlement, the flow of crypto assets, and authoritative changes to account balances held at Zero Hash. To enable this feature, please reach out to your Zero Hash rep and they will configure your Platform accordingly.

New webhook notifications:

1. trade.status_changed
2. account_balance.changed

For more information about configuration and handling webhook payloads, visit the Webhooks Overview page.

Trade Status Changed

Trade status notifications provide information about the current trade status. Net Settlement Trades (a.k.a allocation trades) are filtered out and thus don’t generate a notification for the platforms. There are 3 types of status change notifications:

• accepted - the trade was successfully submitted, accepted, and pending settlement
• active - within the settlement window, settlement was attempted but is not yet complete
• terminated - trade was successfully settled; no further status updates will be issued

Note: The x-zh-hook-payload-type must be set to trade_status_changed

While the schema closely follows the existing GET /trades/{trade_id} endpoint, it does NOT contain EVERY field exposed by the endpoint, such as:

• "accepted_timestamp"
• "defaulted_timestamp"
• "settled_timestamp"
• "last_update"
• "settlement_timestamp"
• "expiry_timestamp"
• "spread_notional"
• "spread_bps"
• "session_id"
• “payment_processor”
• “fees”
• “batch_trade_id“

Any additional or supplementary information should still be fetched from GET /trades/{trade_id} endpoint.

Balance Changed

Account balance change notification provides information about the current available account balance. A notification is emitted when the account balance changes for the following account types:

• available
• collateral

Note: The x-zh-hook-payload-type must be set to account_balance.changed.

The schema of the event payload will follow the existing private websocket balance updates feed

Relevant Documentation

• Webhooks Overview Page
• Trade Status Webhook Reference
• Account Balance Webhook Reference

Release Details

• Release Date: April 30th, 2025

Release Type

Informational – Optional action from platforms

Summary

Zero Hash is pleased to announce support for the Worldchain network. Worldcoin on Worldchain (WLD.WORLDCHAIN) and Ethereum on Worldchain (ETH.WORLDCHAIN) has been added to buy, sell, deposit, withdraw and account funding in both our Cert and Prod environments.

These assets are not currently transact-able by New York residents. A future release note will be created once New York support is enabled.

Action Required

These assets are immediately available using the symbols (WLD.WORLDCHAIN) and (ETH.WORLDCHAIN)

Endpoints Impacted

There are no changes to existing endpoints as a result of this launch.

Relevant Documentation

For a full list of supported assets and instruments, please use the links below.

• Supported Assets
  • Production
  • Certification
• Supported Instruments
  • Production
  • Certification

Release Details

Release Date: April 16th, 2025

Release Type

Informational – optional action from platforms

Summary

The Account Funding product now supports sub-accounting. It's common for platforms to offer their customers the ability to create multiple accounts. For instance, a brokerage may allow customers to open separate trading accounts for tax optimization, risk management, differentiated trading strategies, or to simply organize investments by distinct goals.

As a result, it's essential that Zero Hash provides the flexibility to segregate transactions based on the specific account in use - enter Customer sub-accounts.

There is a new optional query param called the account_label which has been added to the following Account Funding SDK's

• Fund SDK
• Withdraw SDK

Read the end-to-end integration guide to see this new feature in action. At a high-level, here are the impacts:

Funding

• The Platform will acquire an access token the same way they do today, just additionally specifying an account_label on the call
• Zero Hash will save this and attach it to an address once the user selects the Asset and Network
• Once the Customer deposits, Zero Hash will:
  • Recognize the deposit, where the account will have the specified account_label
  • Auto-convert the asset to USD
  • Auto-transfer the USD to the Platform (if configured for this)
  • Send a Fund webhook with the specified account_label in the payload
• The Platform will also be able to retroactively query GET /fund/transactions and see the proper account_label associated with the transaction

Withdrawal

• The Platform will acquire an access token for the Account Link SDK identically to how they do today. No change here
• The Platform will acquire an access token for the Withdraw SDK the same way they do today, just additionally specifying an account_label on the call
• The Customer will initiate a withdrawal on the SDK, triggering the following
  • Auto-convert from the Float account to the asset (no change)
  • Auto-disburse the asset to the destination address, debiting the Customer's account with the specified account_label
  • Send a Payments webhook with the specified account_label in the payload

Products Impacted

Account Funding - this impacts both the SDK and API

Relevant Documentation

• Onboarding API + Fund API Integration Guide
• Onboarding API + Fund SDK Integration Guide
• Onboarding SDK + Fund SDK Integration Guide
• Account Link + Withdrawal SDK Integration Guide

Release Details

Release Date: April 3rd, 2025

Release Type

Informational – optional action from platforms

Summary

The Account Funding product has added additional asset support for both the API and the SDK:

Prior to this release, Account Funding supported the following:

This brings the total asset support to 37 across 19 different networks

Configuration

Platforms can choose which assets they'd like configured. The process for making this configuration is to reach out to your Zero Hash contact, who can then make a quick adjustment on our end.

How it works - Deposit

Select Asset

Select Network

Transaction Pending

The user is presented with the address, a calculator and a rate:

• Address: The address that the user should send the asset to
• Calculator: A helpful tool for users to get an approximate fiat conversion amount for their desired deposit quantity
• Rate: A non-executable current price of the asset. Deposits will be converted at the price at the time of deposit

Calculator

Asset Deposited and Converted

Once the user's deposit has confirmed on-chain, Zero Hash will automatically and immediately liquidate the deposited asset into fiat currency (ie, USD) at the current prevailing rate.

How it works - Withdrawal

The above described assets are also now available to be withdrawn using the Account Link + Withdraw SDK

Account Link SDK

Withdraw SDK

Action Required

If you're interested in configuring your SDK for these additional assets, please reach out to your Zero Hash contact. It is a quick process for us to make this configuration.

Products Impacted

Account Funding - this impacts both the SDK and API

Relevant Documentation

• Onboarding API + Fund API Integration Guide
• Onboarding API + Fund SDK Integration Guide
• Onboarding SDK + Fund SDK Integration Guide
• Account Link + Withdrawal SDK Integration Guide

Release Details

Release Date: March 27th, 2025

Release Type

Informational – optional action from platforms

Summary

Background

Platforms can accompany their Zero Hash integration with a PSP integration. This is to allow customers to purchase crypto or stablecoins using a card or a popular digital wallet (ie, Apple Pay) - the company responsible for this part of the flow is the PSP.

The PSP is responsible for the processing of the fiat leg of the transaction, Zero Hash is responsible for the crypto or stablecoin side (unless of course you are using any of Zero Hash's fiat product offerings directly).

New Requirements

To fulfill regulator audits, Zero Hash must be able to associate a Zero Hash transaction to an associated PSP transaction. We will do this by leveraging the new Zero Hash object payment_processor. This has been added to the following endpoints:

• POST /liquidity/rfq
• POST /convert_withdraw/rfq

and it contains two sub-fields:

Example requests:

-- POST /liquidity/rfq
  
  {
  "participant_code":"CUST01",
  "side": "buy",
  "underlying": "USDC", 
  "quoted_currency": "USD",
  "total": "500", 
  "payment_processor": {         
      "name": "checkout.com", -- the name of the PSP clearing the fiat leg of the trade
      "id": "5cd07738b861c31e3bd61467BTC1Buy1568311644602" --this will be used by Zero Hash to reconcile with the PSP
    }
}

-- POST /convert_withdraw/rfq
  
  {
  "participant_code":"CUST01",
  "side": "buy",
  "underlying": "USDC",
  "quoted_currency": "USD", 
  "total": "500", 
  "withdrawal_address": "0x1c7D4B196Cb0C7B01d743Fbc6116a902379C7238",
  "payment_processor": {         
      "name": "checkout.com", -- the name of the PSP clearing the fiat leg of the trade
      "id": "5cd07738b861c31e3bd61467BTC1Buy1568311644602" -- the  unique ID that must be tied back to the PSPs transaction - this will be used by Zero Hash to reconcile with the PSP
    }
}

Settlement Flow

There are 2 different types of settlement sessions:

• Net buy session: There is more buy volume than sell (therefore Zero Hash receive a settlement)
• Net sell session: There is more sell volume than buy (therefore Zero Hash will disperse a settlement)

Net Buy

• Zero Hash will receive a settlement directly from the PSP
• The funds will be credited to the Platform's float account

Net Sell

• Platform can request a USD withdrawal on the client portal or via API to their respective bank

Action Required

n.a

Products Impacted

• Remittance
• On and Off Ramp

Relevant Documentation

• Remittance integration guide