Fix Game Logic & Wallet Sync Bug in Lotus365-Based Platform I’m running a product that relies on the Lotus365 gaming API. The frontend and authentication work fine, but a logic flaw in the gameplay endpoints is producing incorrect results during live play. Sometimes, games show “Insufficient balance” even when funds exist, or fail to credit winnings / deduct losses after a round. I need this bug traced, patched, and tested so game results and wallet balances are fully reliable. Scope of Work Inspect current Lotus365 API integration and pinpoint the faulty gameplay routine. Fix the logic without breaking existing login, UI, or balance flow. Validate real-time wallet sync between gameplay, callbacks, and balance updates. Add regression and unit tests to ensure stability. Provide a short technical summary of the issue, fix, and recommendations. What I’m Looking For You’ve handled gameplay or wallet logic bugs in gaming / betting platforms, know how to debug PHP + MySQL APIs, and can work comfortably with Lotus365 or similar SDKs. Experience with real-time balance updates (SSE / WebSocket), API performance profiling, and secure wallet transactions will help you hit the ground running. To Apply Briefly describe: A similar bug-hunt or gameplay logic issue you’ve fixed before. The tools you used (debugging, API testing, encryption handling, etc.). Once selected, I’ll share full repo access, database dump, and test credentials.