Institutional Exchange Integration Flow

The following is a specific integration flow for platforms using Zero Hash for agency-based settlement for institutional exchanges.

Participant Onboarding

Connecting with Customers

  1. Onboarding of institutional participants, customers, and counterparties requires manual KYC processes. You can submit the KYC information online via our portal or via some other mutually agreed-upon process. Once the customer is onboarded, we will associate them with your exchange platform.

Viewing All Customers

Note: you must obtain the participant_code for each of your customers. You can do this a variety of ways:


  • You can review all of the participants you are associated with via the Parties page in the portal. Also, refer to the Participant Relationships and Access Rights page for more information on relationships.


  • You can review all of the participants listed as a customer_of_platform via the Platform Customers report in the Reports page in the portal.


  • You can perform a GET /participants request to be provided a list of participants you are connected with. You can read more here.

Client Funding


  • Clients can initially fund their account through one of our banking partners for fiat or via one of their dedicated wallets for digital assets.
    - Fiat Deposits
    - Digital Assets


Once funded, clients can allocate funds to various Zero Hash-integrated platforms. It's important to note that this type of movement will not produce an on-chain or inter-bank account movement. It will only take place on the Zero Hash ledger and gives the client trading power on different platforms.

Platforms can elect to lock assets once allocated to their platform.

Monitoring Client Fund

  • Email: When configured, platforms can receive email updates when clients balances change on their platform.
  • Reports: Reports can be found in the Reports section of the portal. Here are the relevant options for client funding:
    • Platform Net Open Positions (NOP)
    • Platform Net Delivery Obligations (NDO)
    • Platform Account Balances, Snapshot
    • Platform Account Balances, Historical
  • API: You can perform a GET /accounts request and filter on account_owner = your customer’s participant_code to see how much they have in accounts dedicated for trading on your platform.

Trade Submission

Trade submission can be done via the standard Zero Hash FIX STP gateway, a custom FIX STP gateway, or REST API.


Zero Hash operates a standard FIX STP gateway into which you can submit trades. Note: you must include the participant_code of the customers as tag 448 PartyID. You can read more here.

Custom FIX Gateway

For specific engagements, Zero Hash can develop custom gateways to receive drop copies from third party trade feeds. This requires custom development work and mapping. Please contact [email protected] if this is of interest.


You can submit trades via REST API via the POST /trades endpoint. Upon submission, and as a response, you will receive a trade_id. This is the unique ID for the trade, useful in step 4. You can read more here.

Trade Settlement

Settlement Schedules

We can process a trade for settlement according to a variety of schedule parameters, including:

  • Instant settlement
  • Repeated settlement attempts across any time interval
  • Batch settlement every day at a certain time

Further, we can configure a different schedule to retry settlement after the initial attempt.



The Trades section of the portal allows you to view high-level information about trades that have been submitted to Zero Hash. The trade_state field will indicate whether a trade is accepted, active, or terminated.


You can submit a GET /trades/ to see all trades and their status. You will want to see that the trade_state is terminated and the settlement_state is settled. Optional validation: you can perform a GET /accounts request and filter on account_owner = your customer’s participant_code to see that they now have crypto in their account.