Player Balance Management
Wallets Introduction
When integrating EvenBet Gaming software (referred to as EBG) into your system (the Customer Platform), one of the most critical decisions you will make is selecting the right wallet integration method. This choice determines how player funds are managed, tracked, and transferred between the Customer Platform and EBG Poker.
We offer three integration approaches, each designed to support different business models and technical requirements. This guide will help you understand the key differences and select the option that best fits your needs.
Integration Types
1. Seamless Integration (Recommended)
This is the most popular integration method due to its high level of player transparency and control.
How it works: With Seamless integration, all player funds remain in the Customer Platform at all times. EBG Poker communicates with the Customer Platform to check balances and reserve funds for gameplay, but never actually holds the money.
- Player funds always remain in the Customer Platform's ownership.
- Players see their full Customer Platform balance when accessing poker.
- No separate deposit/withdrawal flow is required for the user.
- Complete transparency of fund movements.
Technical flow:
- Player joins poker: EBG System calls the Customer Platform API for the current balance.
- Player sits at a table: EBG System sends a request to reserve funds on the Customer Platform (e.g., $100 buy-in).
- Player plays the game: Funds remain reserved on the Customer Platform. (The API is not called for every hand).
- Player leaves the table: EBG System sends a request to return the final amount. This amount includes the original buy-in plus winnings or minus losses.
- Customer Platform updates the player's balance based on the game outcome.
Best for:
- Operators who want complete ownership of player funds.
- Operators prioritizing a smooth player experience with minimal friction.
- Platforms requiring full financial transparency.
Link to Seamless Integration documentation →
2. Transfer Integration
How it works: With Transfer integration, players must explicitly transfer funds from the Customer Platform into EBG Poker before playing. The poker wallet operates as a separate balance.
- Players maintain a separate poker balance.
- Explicit deposit and withdrawal actions are required.
- Funds for poker games are tracked within the EBG System.
Technical flow:
- Player initiates deposit from the Customer Platform — calls EBG System deposit API method.
- Funds move to poker balance in the EBG System.
- Player plays using only their poker balance.
- Player initiates withdrawal — calls EBG System withdrawal API method.
- Funds return to the Customer Platform.
While transfers are usually triggered by a player action, the Customer Platform can also program these API calls to be automatic (e.g., auto-transfer upon login).
Best for:
- Platforms where poker should operate as a distinct game with a separate player balance.
- Systems with limited API development resources.
- Operators comfortable with delegating poker fund management.
- Scenarios requiring clear separation between poker and platform finances.
Trade-offs: This integration provides less transparency into player behavior and fund flow from the Customer Platform's perspective, which is why it is less commonly chosen by operators.
Link to Transfer Integration documentation →
3. Reverse Integration
How it works: Reverse integration is a custom solution where EBG System adapts to match your existing API setup. Instead of you building to our specifications (as in Seamless), we modify our integration logic to work with your protocols—similar to how other game providers integrate into your platform.
- Custom-built to your API standards.
- Funds remain in your system.
- Players see their full platform balance.
- EBG System conforms to your technical specifications.
Best for:
- Large operators with established, non-negotiable API standards.
- Platforms already integrating multiple game providers via a standardized protocol.
- Organizations requiring vendors to adapt to their system.
This option requires a robust, well-documented wallet API on your side and significantly more development resources from EvenBet Gaming. Please discuss viability with your Account Manager before proceeding.
Comparison Table
| Seamless Wallet | Transfer Wallet | Reverse Wallet | |
|---|---|---|---|
| Balance location | Customer Platform | EBG System | Customer Platform |
| Player balance visibility | Full platform balance | Separate poker balance | Full platform balance |
| API development required | Customer Platform side | Customer Platform side (minimal) | EBG side |
| Technical Requirements | Callback API + IP Whitelist | IP Whitelist | Existing Wallet API |
| User friction | Low | High | Low |
| Transparency | Complete | Limited | Complete |
| Regulatory compliance | Simpler (funds stay with you) | Complex (fund transfers) | Simpler (funds stay with you) |
| Popularity | ⭐⭐⭐⭐⭐ Most popular | ⭐⭐ Less common | ⭐ Least common |
Next Steps
- Review the detailed documentation for your chosen integration type.
- Assess your technical capabilities and business requirements.
- Contact our integration team to discuss your specific use case.
- Begin API development following our specifications.
If you have questions about which integration type is right for your platform, our team is here to help guide your decision.