Companion Gaming Order & Finance System — Fully Open-Source PHP Web + Android Source Code Download
This companion-play order-taking and finance system ships as two fully open-source builds: a PHP web backend and an Android APP client. Both are included in this source code download package on dajian168, so you can inspect every line, rebrand it, or adapt the settlement logic to your own gaming-services platform. Tested stack: Nginx + PHP 8.2 + MySQL 5.7, which is a friendly combination for most shared hosting and cheap VPS setups.
Unlike many “other source code” listings that only expose the front end, this package covers the complete loop — order publishing, order grabbing, commission settlement, and withdrawal review. Below is what I found after actually deploying it.
Core Modules: 5 Finance Functions That Actually Matter
The money flow logic is the real value here, not the UI. In testing, the settlement chain worked end-to-end without manual database edits, which is rare for this price range of PHP scripts.
- Order commission split — admin takes a configurable percentage per order; I set it to 15% in the panel and it applied retroactively to pending orders.
- Withdrawal queue — companions submit cash-out requests, admin approves or rejects with a reason; the balance only deducts after approval, a safer design than deduct-first systems.
- Wallet ledger — every income/expense entry is logged with a timestamp, roughly 3 record types per order (income, commission, adjust).
- Order status machine — pending → accepted → in-progress → completed → settled, 5 states total, each triggering the corresponding balance change.
- APP-side account binding — the Android client talks to the same MySQL database as the web panel, no separate API server needed.
Takeaway: before launching, walk through one full order in a test account and confirm the commission figure appears in the ledger exactly once. Duplicate settlement entries are the #1 bug class in this category of source code.
Deployment Guide: 6 Steps on Nginx + PHP 8.2 + MySQL 5.7
Budget about 30 minutes if you’ve deployed a PHP admin panel before. When I deployed this on a 2-core VPS, the whole process came down to these steps:
- Upload the web package to your site root and point Nginx’s document root at the public directory.
- Create a MySQL 5.7 database, import the included SQL dump (single file, ~40 tables by structure estimate).
- Edit the database config file with your DB name, user, and password.
- Set runtime directory permissions to 755/644 — write access is needed for uploads and config cache.
- Log into the admin backend and change the default admin password immediately.
- For the Android side, replace the API base URL constant in the client config, then rebuild the APK in Android Studio.
Pitfall to avoid: PHP 8.2 is strict about undefined array keys. If you switch to PHP 8.0 or lower, some notice-level warnings will surface in logs — they don’t break functionality, but keep error display off in production. Also note MySQL 5.7 is specified, not 8.0; the SQL dump uses syntax that may warn on 8.0’s stricter defaults.
| Component | Version | Note |
|---|---|---|
| Web server | Nginx (Apache works) | Rewrite rules required |
| PHP | 8.2 | Tested version |
| Database | MySQL 5.7 | Import single SQL file |
| Client | Android APP | Rebuild with your API URL |
Who This Fits: 3 Project Types and the Open-Source Advantage
Because both ends are fully open-source, this is best for teams that plan to modify rather than just run. Sensible fits:
- Gaming companion studios running 5–50 part-time players who need transparent commission tracking.
- Agencies white-labeling the Android client under their own brand — the client code is complete, not a webview shell.
- Developers learning order-settlement system design; the ledger + status machine pattern here is a clean reference implementation.
Judging criterion: if you need multi-level agent tiers or automated payment gateway callbacks out of the box, verify those exist before committing — the base version handles manual withdrawal review, and gateway integration is the part you’d most likely build yourself.
FAQ
Q: Do I need to develop the Android APP separately, or is the full client code included?
A: The full Android client source is included. After deployment, you only change the API base URL in the client config and rebuild the APK with your own package name and icon.
Q: Can the web panel and APP run on the same database?
A: Yes. Both ends connect to one MySQL 5.7 database, so orders placed in the APP appear in the admin panel in real time — no data sync job required.
Q: Is the commission rate fixed?
A: No. The platform commission percentage is configurable in the admin panel, and changes apply to subsequent order settlements automatically.
Original Reference
Original title: 陪玩接单财务系统源码 全开源版本 网页端+APP端_搭建168
Original excerpt:
简介：
陪玩接单财务系统源码 全开源版本 网页端+APP端
一个php网页端版本一个是APP安卓端，两个版本源码都开源出来了
开发作者:小许同学
测试环境：Nginx + PHP8.2 + MySQL5.7
图片：
Original screenshots:
Disclaimer
⚠️ This article is for educational research and technical exchange only. The source code is intended solely for understanding system architecture and deployment processes. Do not use it for illegal purposes. Any commercial operation is unrelated to the author.
