Skip to content

Transfer Integration Overview

Transfer integration means API Provider holds the player’s balance. You control fund transfers by calling our API to deposit or withdraw money from the player’s API Provider account.

  • Centralized Balance: API Provider manages the player’s balance
  • Transaction Control: You decide when to deposit or withdraw to the player’s account balance
  • Simplified Integration: API Provider handles all in-game transactions automatically
  • Easy Management: You only call deposit, withdrawal, and check balance APIs
  1. Player’s balance is stored in API Provider’s system
  2. You call deposit API to add funds to their API Provider balance
  3. API Provider manages all in-game transactions (bets, wins, losses) automatically
  4. You call withdraw API to remove funds from their API Provider balance
  5. You handle the money on your end as needed

KRW, USD, JPY, CNY, PHP, HKD, THB, VND, BDT, INR

EndpointPurposeWhen to Use
Account InitCreate API Provider accountFirst time player accesses games
Account DepositAdd funds to API Provider balancePlayer wants to add money
Account WithdrawRemove funds from API Provider balancePlayer wants to cash out
Account BalanceCheck player’s API Provider balanceView the current balance stored in API Provider
Check TransactionVerify transaction statusConfirm pending transactions

Refer to the error codes to handle common scenarios like insufficient balance, account not found, duplicate transactions, and invalid amounts.

Error Codes

{
"https": {
"200": "successful request",
"202": "failed request",
"500": "internal error"
},
"codes": {
"0": "successful request",
"1": "error occured",
"2": "missing data",
"3": "invalid key",
"4": "data format error",
"5": "expired request",
"6": "invalid agent",
"9": "blocked user",
"100": "data value error",
"101": "permission denied",
"102": "insufficient balance",
"103": "integration failure"
},
"history_types": {
"ALL": "all",
"END": "ended",
"ING": "ongoing"
}
}
  • Use unique transaction IDs for all deposits and withdrawals
  • Duplicate transaction IDs will return the original response
  • Never reuse transaction IDs across different operations

Your Responsibility:

  • Decide when to add funds (call deposit API)
  • Decide when to remove funds (call withdraw API)
  • Handle transaction failures and retries
  • Track your own financial records if needed

API Provider’s Responsibility:

  • Store and manage player’s balance
  • Process all bets, wins, and losses automatically
  • Update balance for deposits and withdrawals
  • Provide current balance information on request
  • All requests must be encrypted (see Encryption Guide)
  • Validate amounts before API calls
  • Use HTTPS for all endpoints
  • Store credentials securely
  • Log all transactions for auditing

Follow this order when implementing transfer integration:

  1. Implement Account Init
  2. Test account creation for new players
  3. Handle existing account scenarios
  1. Implement Account Deposit
  2. Test adding funds to player’s API Provider balance
  3. Implement Account Withdraw
  4. Test removing funds from player’s API Provider balance
  1. Implement Account Balance
  2. Implement Check Transaction
  3. Test complete deposit-play-withdraw flow

Before starting implementation, ensure you have:

  1. Read the Getting Started Guide
  2. Understand Transfer API concepts
  3. Set up your encryption
  4. Implement Account Init
  5. Test deposit and withdrawal flows
  6. Review integration patterns above

Ready to start? Begin with Account Init to create your first API Provider account.