Skip to content

Transfer Wallet

The Licensee creates player accounts within the Game Provider system and transfers funds into it via external APIs. Before entering a game, the player must transfer funds from their main wallet to the sub-wallet managed by the Game Provider. Upon exiting the game, any remaining balance is transferred back to the main wallet.

During gameplay, the Game Provider only manages the balance within the player’s sub-wallet and ensures that all betting, payouts, and promotional rewards are handled entirely within this sub-wallet.

Notes for Licensee

Transfer-related APIs are provided by the Game Provider and must be invoked by the Licensee. The Game Provider does not accept direct deposit or withdrawal requests from the Player—only the Licensee is authorized to perform these operations.

Similar to the Seamless Wallet, the Game Provider follows the same communication protocols and technical specifications:

  • Uses RESTful APIs
  • Expected response time under 300 ms
  • Requests and responses use JSON format (content-type: application/json)
  • HTTPS only
  • Authentication methods:
    1. Add authorization: ECDSA-SHA256 <API_KEY> in Request Header 1
    2. Add authorization: HMAC-SHA256 <API_KEY> in Request Header 1
    3. Add authorization: bearer <API_KEY> in Request Header
    4. Add api-key: <API_KEY> in Request Header 2
    5. Add api_key=<API_KEY> in Query String (Not Recommended)
  • API_KEY specification:
  • Provided by the Licensee
  • Recommended length: 8–22 characters
  • Allowed characters: A-Z, a-z, 0-9, ., - 3
  • API endpoint requirements:
  • Must have a valid HTTPS certificate
  • Use a fixed public IP or stable DNS record
  • Temporary tunneling services or short URLs are not accepted

Transaction Model

The Licensee can provide Deposit and Withdrawal functions on its platform, allowing the Player to transfer funds in and out at any time.

Under the Transfer Wallet model, the following operations do not interact with the Licensee’s main wallet:

  • Debit
  • Payout
  • Promo Payout
  • Cancel

All debits and payouts are handled internally by the Game Provider.

Comparison with Seamless Wallet

  • Requires Transfer-In / Transfer-Out processes
  • Player balance is fully managed by the Game Provider during gameplay
  • The Licensee does not participate in betting activities
  • The Licensee handles fewer API calls

Choosing a Wallet Model

If your platform includes game lobbies, high-frequency betting games, or operates with an independent credit system, the Transfer Wallet model is strongly recommended.

  1. HMAC-SHA256 ↩↩

  2. api-keys ↩

  3. RFC5890 ↩