Each cryptocurrency your application plans to accept, needs a callback URL in order for the Playbetr system to notify you of incoming deposits. When a cryptocurrency deposit is first received by our system, we send out a notification that an unconfirmed deposit has been received. Once the deposit gets the required amount of confirmations, another notification is sent out that a confirmed deposit has been received. One final notification is sent out that a complete deposit has been received once the required confirmations are met. By default, the number of confirmations needed for each of these notifications are as follows:
0 confirmations = unconfirmed
1 confirmation = confirmed
3 confirmations = complete
These values are configurable on a property basis.
Whenever any of these conditions are met, we will send a POST request to your callback URL with the following parameters:
crypto_transaction_detail_id - This field represents the unique id for the transaction in the Playbetr system. The client endpoint needs to keep track of this id and make sure deposits are not duplicated in their system
transaction_id- This is the id for the transaction in the Playbetr system. This can usually be disregarded on the client system.
txid - This is the cryptocurrency txid of the transaction.
source_id - This is the id for the source in the Playbetr system. This can usually be disregarded on the client system.
account_id - This is the id for the account in the Playbetr system.
amount - This is the amount of the deposit in the local currency.
received - This is the amount of the deposit in cryptocurrency.
address - This is the address that received the deposit.
currency - This is the currency the deposit was received in.
status - This is the status of the deposit.
0 = unconfirmed
1 = confirmed
2 = complete
apikey - This is the api key used to authenticate this request on the client system.