Overview

There are mainly three steps involved in tracking your user deposits:

1. You need to enable HMAC.

2. You need to create a deposit tracking session for your user.

3. You need to prepare a callback endpoint in which we inform deposit events for your users.

The system administrators manage the callback URLs for deposit event objects. You must communicate with our system administrators to set your callback URL for deposit events.

How Does The System Work?

When the customers open a deposit tracking session for one of their users, the system creates blockchain deposit addresses from a common xpub for this user. It starts to monitor incoming deposits for these addresses.

Unless we remove these addresses from the system, the system will monitor these addresses indefinitely. After six months of inactivity, disposal of these addresses takes place.

When the system creates blockchain addresses for the users, the system permanently assigns these addresses to the users and does not change them. These addresses are monitored for deposit arrivals, even if the customers do not create a deposit tracking session. So the customers may occasionally get webhook notifications, even if they do not initiate a session.

Opening a session is not essential to receive deposit events. If a user deposits to their pre-assigned address without opening a session, the system will still inform this event to the customer.

However, the customers must create a session for their users for the first time to have their blockchain deposit addresses generated.

The system sets an expiration time for the session, which is currently one hour after the creation time. It expects a deposit within a one-hour timeframe. If the cryptocurrency state does not change within that timeframe, we consider the session expired. The system promises a fixed cryptocurrency-to-fiat rate if the deposit arrives within an hour.

It is also possible to accept payments after the session is expired. If the system detects a deposit after an expired session, it automatically generates a new session token. Unfortunately, providing a fixed cryptocurrency-to-fiat rate is impossible when this situation happens.