Transfer Wallet API Introduction

What is Transfer Wallet Mode?

Transfer Wallet mode is a gaming integration solution where member balances are divided into main wallet and game wallet. Players need to transfer funds from the main wallet to the game wallet before placing bets. After the game, the balance can be transferred back to the main wallet.

Differences with Single Wallet

Feature	Transfer Wallet	Single Wallet
Balance Management	Managed by Platform	Managed by Operator
Betting Process	Transfer then Bet	Real-time Deduction
Implementation Requirements	Operator calls Platform APIs	Operator implements 4 APIs
Fund Flow	Transfer In/Out Required	No Transfer Required
Use Case	Platforms requiring fund isolation	Operators with existing wallet systems

In Transfer Wallet mode:

1. 🎮 Players first transfer funds from main wallet to game wallet
2. 🔐 Gaming platform uses transferred funds for gaming
3. 💰 Betting and settlement occur within the game wallet
4. 📊 After gaming, balance can be transferred back to main wallet

Documentation Structure

This documentation contains the following functional modules:

📗 Platform APIs (Called by Operator)

Operators can call the following platform APIs for member management, fund transfers, and queries:

• Fund Transfer

  • Transaction - Transfer funds from main wallet
  • Get Balance - Query main wallet and game wallet balance
  • Query Transaction Detail - Query single transfer details
  • All Cash Out - Withdraw game wallet balance to main wallet

• Member Management

  • Create Member - Register new members on the platform
  • Query Online Members - View currently online members
  • Get Member Sessions - Check member login status
  • Kick Out Player - Force logout member

• Game Management

  • Get Game List - Query available games
  • Get Popular Game List - Query popular game rankings
  • Open Game - Generate game launch URL

• Item Management

  • Get Operator Card Information - Get Operator Card Information
  • Use Operator Card - Use Operator Card
  • Cancel Operator Card - Cancel used item
  • Query Operator Card Status - Query item usage status

• Bet Logs

  • Get BetLog - Query member bet records
  • Query Transaction Details - Query single bet details
  • Get BetLog Reply - Generate bet replay URL
  • get Daily Report - Query daily operation report
  • Query Member Report - Query Member Report

Version Information

• Version: v2.0.0
• Type: Transfer Wallet Mode
• Encryption Method: AES-256-GCM
• Authentication Method: JWT Token + SHA256 Signature

Decrypted request content typically includes:

• token: Gaming platform authentication token
• account: Player Account
• nonce: Unique transaction identifier (UUID)
• timestamp: Request timestamp

Common Response Format

Success Response (With Data)

All API responses are in plain JSON format, following this structure:

{
  "code": 0,
  "message": "No error.",
  "data": {
    // API-specific response data
  },
  "logUUID": "042d4437-cbe3-440a-8acf-4baff3722fd6"
}

Field	Type	Description
code	number	Status code, 0 indicates success
message	string	Status message, "No error." on success
data	object	API response data, varies by API
logUUID	string	Request tracking ID for troubleshooting and log queries

Success Response (No Data)

For operations that do not require returning data, the response format is as follows:

{
  "code": 0,
  "message": "No error.",
  "logUUID": "042d4437-cbe3-440a-8acf-4baff3722fd6"
}

Error Response

{
  "code": 6,
  "message": "The username already exist.",
  "logUUID": "6589bf8d-fe74-48bd-841a-71bf8f848f86"
}

Field	Type	Description
code	number	Error code (non-zero), refer to error code table for each API
message	string	Error description message
logUUID	string	Request tracking ID for troubleshooting and log queries

Common Response Codes

Below are common response codes. For detailed error codes, please refer to "Appendix" page.

Fund Flow

Testing Recommendations

• Use stage environment for development testing
• Ensure all error scenarios are properly handled
• Verify uniqueness of nonce
• Test network exceptions and timeout situations
• Regularly query balance to ensure correct funds

Important Notes

1. Dual Wallet: Need to manage both main wallet and game wallet balances
2. Transfer Confirmation: Recommend using balance query API to confirm after transfer/withdrawal operations
3. Balance Management: Ensure game wallet has sufficient balance for gaming
4. Transaction Tracking: Save all transfer records for reconciliation
5. Exception Handling: Properly handle and notify players when transfer fails