Server-to-Server API

Integrate directly with your Casino or Platform backend seamlessly using our REST API. All requests must be authenticated via an HMAC SHA256 Signature.

POST

/api/v1/deposit

Generates a unique crypto transit wallet linked strictly to the provided player_ref. Return payload includes the generated standard network address.

Request Body Payload

{
  "player_ref": "USER_77812",
  "pg_ref": "DEP_9901A",
  "network": "TRC20",
  "token": "USDT",
  "expected_amount": "50.00"
}

200 Response Array

{
  "status": "success",
  "data": {
    "internal_ref": "B_8819_TRC20",
    "destination_address": "T...",
    "status": "awaiting payment"
  }
}
POST

/api/v1/withdrawal

Submits a player payout request to the admin pool to be processed by the Treasury Hot wallet. Requires manual confirmation in the backend unless Auto-Approve is enabled.

Request Body Payload

{
  "player_ref": "USER_77812",
  "pg_ref": "WD_128A",
  "target_wallet_address": "0xABC...",
  "network": "ERC20",
  "token": "USDT",
  "amount": "100.00"
}

200 Response Array

{
  "status": "success",
  "message": "Withdrawal requested",
  "data": {
    "internal_ref": "W_9918_ERC20",
    "status": "pending_review"
  }
}
GET

/api/v1/deposit/{internal_ref}

Query the absolute real-time block-status of a pending deposit transaction. The internal daemon verifies blockchain confirmation heights natively.

200 Status Returns

  • awaiting payment
  • detected (Tx found in mempool)
  • confirming (Waiting on blocks)
  • confirmed (Funds valid)