Safepays Havale/EFT Client Api
    Safepays Havale/EFT Client Api
    • Changelogs
    • Callback
    • Methods
      • deposit
        POST
      • withdraw
        POST
      • bank list
        POST
      • transaction status
        GET

    Callback

    #

    Safepays transfer callbacks aim to inform you about the transactions you have made. You will definitely receive a callback from us for your transactions after each deposit and withdrawal.
    **Important : Sometimes we may send the callback we have already delivered for the 2nd time. In such cases, we expect you to reject our 2nd callback. Contact us for more information.
    We may send callback with status Pending if deposit transaction was needed reapprove while it has been rejected first. You can ignore this request with pending status if you will not use.
    It may take up to 12 hours for the callbacks to reach you, you can cancel the transactions that did not receive the callback within 12 hours. (We usually deliver within 15-20 minutes.).
    Do not forget that the endpoint to which we will send the callback will be provided by you.
    Callback requests are sent to you with the POST method as content-type: application/json.
    After your deposit/withdraw transactions, the following information is sent to the endpoint you provided to us.
    Retry callback: Callback requests will be retried 3 times if we could not received response with status 200 by your endpoint
    ParametersValueDescription
    purposedeposit/withdrawTransaction type.
    bet_provider_txidstring (60)The transaction id provided by you.
    txiduuidThe transaction id issued by us.
    player_idstring (60)Player id provided by you.
    player_usernamestring (60)The player username provided by you.
    player_fullnamestring (60)The player name provided by you.
    amountstring (60)The string representation of the amount of the transaction. note: amount can vary
    The decimal separator is a dot, 2 digits after a dot, no thousands separator.
    tokenstring (64)Token info of the transaction. Encrypted data. It is formed by hashing following data side by side with sha256 : txid, amount, secret, betProviderTXID. Please combine the data in order and do not use commas.
    statuscompleted / canceled / pendingStatus of the transaction.
    reject_reasonobject (id,name, description)If the transaction status is canceled, it contains the reason.
    Previous
    Changelogs
    Next
    deposit
    Built with