Crypto Deposits SDK Guide
Enable users to deposit crypto directly onto your platform for use in trading or transfer
Initialize Crypto Deposits Flow
Retrieve Account Funding JWT token
In order to successfully invoke the Access Token, you'll need to supply a participant_code for the End Customer (see full instructions here). This customer must be in an approved status for this call to succeed. Please note: the correct permission to pass here is crypto-deposits.
Invoke the Crypto Deposits SDK
See the Crypto Deposits SDK implementation guide for technical instructions.
Crypto Deposits Webhooks
See Deposit Status Updates for more detail on deposit webhooks schemas and sample payloads.
Query Deposits
It may be helpful (or likely required) to display crypto or stablecoin deposits in the Transaction History (or like page) on your application. You can use the GET /deposits/crypto endpoint to query all deposits events.
Deposit returns
IMPORTANT: You cannot rely on the deposit’s source address as the return destination. Blockchain transactions are not inherently bidirectional, and returning funds to the sender address may result in loss of funds or failed deliveries.Some Platforms may choose to pair their zerohash integration with their own transaction monitoring tools. In situations where zerohash accepts a deposit, but the Platform’s monitoring logic flags and rejects it, the Platform may opt to return the deposit by using the POST /withdrawal/requests endpoint.
The required flow is to always request and confirm a return address directly from the customer before initiating the return.
Please speak to a zerohash sales engineer for guidance if interested in this flow.
Updated 14 days ago