🚀 Project Overview
Status: Production Ready (Backend Complete) Launch: Q1 2025 (Beta) Domain: oddxer.com Port: 6793 (dev), 8080 (production)
| Metric | Value |
|---|
| Tech Stack | Node.js, MongoDB, React 18, Socket.io |
| API Endpoints | 33 endpoints (7 auth, 8 codes, 8 wallet, 4 voting, 6 leaderboard) |
| Database Models | 6 models (User, BettingCode, Wallet, Transaction, Vote, Leaderboard) |
| Authentication | Phone OTP + JWT |
| Real-Time | Socket.io WebSocket |
| Status | ✅ Backend 100% |
| Last Updated | February 2026 |
📋 Quick Links
Product Documentation
Technical Documentation
Business Documentation
Development
Analytics
🎯 What Makes Oddxer Unique
The Problem
- Trust deficit: Bettors lose money to fake betting codes from unverified sellers
- No accountability: Scammers operate on WhatsApp/Telegram with no consequences
- Information asymmetry: Buyers can't verify seller track records
- Fragmented market: No centralized marketplace for betting codes
The Solution
Oddxer creates a transparent P2P marketplace where:
- Sellers list betting codes with detailed information (sport, odds, bookmaker, price)
- Buyers browse codes, check seller performance, and purchase securely
- Community votes on outcomes (WIN/LOSS) after bet expires
- Leaderboard ranks sellers by verified win rates and performance
- Real-time updates ensure instant marketplace changes
Key Differentiators
- ✅ Community voting for transparent outcome verification
- ✅ Performance tracking with historical seller statistics
- ✅ Secure payments via wallet system with mobile money
- ✅ Real-time marketplace with Socket.io WebSocket updates
- ✅ Mobile-first design optimized for African markets
- ✅ No direct competitors in P2P betting code marketplace
💻 Technology Stack
Backend (✅ Complete)
- Runtime: Node.js 20.x
- Language: TypeScript 5.3+
- Framework: Express.js 4.18
- Database: MongoDB 6.0 with Mongoose ODM
- Authentication: JWT (access + refresh tokens), bcrypt
- Validation: Joi 17.11+
- Real-Time: Socket.io
- Logging: Winston
- Security: Helmet, CORS, rate limiting
Frontend (🔄 In Progress)
- Framework: React 18
- Build Tool: Vite
- Styling: TailwindCSS
- State Management: Context API / Zustand
- HTTP Client: Axios
- Real-Time: Socket.io client
Infrastructure
- Deployment: Google Cloud Run
- Database Hosting: MongoDB Atlas
- Domain: oddxer.com
- CI/CD: GitHub Actions
- Monitoring: Google Cloud Logging
📊 Business Model
Revenue: Transaction Fees
Fee Structure:
- 10% on codes 0-50 ZMW
- 12% on codes 51-200 ZMW
- 15% on codes 201-500 ZMW
- 18% on codes 500+ ZMW
Example Transaction (100 ZMW code):
Buyer Pays: 100 ZMW
Platform Fee (12%): 12 ZMW
Seller Receives: 88 ZMW
Financial Projections (Year 1)
| Quarter | Users | Transactions | GMV | Revenue |
|---|
| Q1 2025 | 500 | 1,000 | 60K ZMW | 7.2K ZMW |
| Q2 2025 | 2,000 | 10,000 | 600K ZMW | 72K ZMW |
| Q3 2025 | 10,000 | 50,000 | 3M ZMW | 360K ZMW |
| Q4 2025 | 50,000 | 250,000 | 15M ZMW | 1.8M ZMW |
| Total | 50,000 | 311,000 | 18.66M ZMW | 2.24M ZMW ($93K) |
🌍 Market Opportunity
Zambia Betting Market
- Market Size: $220 million annually
- Online Betting: $88 million (40%)
- Growth Rate: 24% year-over-year
- Population: 20.2 million (median age 17)
- Smartphone Penetration: 45% (9.1 million users)
- Mobile Money: 68% of transactions
Target Addressable Market (TAM)
- Zambia Year 1: 2.7 million active bettors
- Africa Year 3: 54 million potential users (5 countries)
Regional Expansion
- Zambia (Q1-Q4 2025) - Launch market
- Kenya (Q1 2026) - M-Pesa integration
- Nigeria (Q3 2026) - Largest African market
- Ghana, South Africa (2027) - Continued expansion
🏗️ System Architecture
High-Level Architecture
┌─────────────┐
│ Client │ (React + Socket.io client)
└──────┬──────┘
│ HTTPS / WSS
┌──────▼────────────────────────────┐
│ API Gateway / Load Balancer │
└──────┬────────────────────────────┘
│
┌──────▼──────────────────────────┐
│ Express.js API Server │
│ - REST API (33 endpoints) │
│ - Socket.io Server │
│ - JWT Authentication │
│ - Input Validation (Joi) │
└──────┬───────────────────┬───────┘
│ │
┌──────▼────────┐ ┌─────▼──────┐
│ MongoDB │ │ WhatsApp │
│ (Atlas) │ │ API (OTP) │
└───────────────┘ └────────────┘
API Endpoints Summary
Authentication (7 endpoints):
- POST /auth/register
- POST /auth/verify-otp
- POST /auth/login
- POST /auth/refresh
- POST /auth/logout
- GET /auth/me
- POST /auth/resend-otp
Betting Codes (8 endpoints):
- POST /codes (create)
- GET /codes (browse)
- GET /codes/:id (details)
- POST /codes/:id/purchase
- GET /codes/my-codes (seller)
- GET /codes/purchased (buyer)
- PATCH /codes/:id (update)
- DELETE /codes/:id (delete)
Wallet (8 endpoints):
- GET /wallet (balance)
- POST /wallet/deposit
- POST /wallet/withdraw
- GET /wallet/transactions
- GET /wallet/transactions/:id
- POST /wallet/deposit/:id/confirm (admin)
- POST /wallet/withdraw/:id/confirm (admin)
- POST /wallet/transactions/:id/fail (admin)
Voting (4 endpoints):
- POST /codes/:id/vote
- GET /codes/:id/votes
- GET /codes/:id/votes/list
- POST /codes/:id/finalize (admin)
Leaderboard (6 endpoints):
- GET /leaderboard
- GET /leaderboard/top
- GET /leaderboard/by-winrate
- GET /leaderboard/:sellerId
- POST /leaderboard/recalculate (admin)
- POST /leaderboard/:sellerId/recalculate (admin)
🎯 Current Sprint (December 2025)
Sprint Goals
- ✅ Complete backend API (33 endpoints) - DONE
- 🔄 Build frontend marketplace interface - 60% Complete
- 📋 Mobile money integration (MTN, Airtel) - Pending API credentials
- 📋 Deploy to production (Google Cloud Run) - Pending
Completed This Sprint
- [x] User authentication system (phone OTP + JWT)
- [x] Betting code marketplace (CRUD + purchase flow)
- [x] Wallet system (deposits, withdrawals, transactions)
- [x] Community voting mechanism
- [x] Seller leaderboard with rankings
- [x] API documentation (this hub)
- [x] Docker containerization
- [x] Error handling and logging
In Progress
- [ ] Authentication UI (Login, Register, OTP pages)
- [ ] Marketplace browse page
- [ ] Wallet dashboard
- [ ] Seller dashboard
Growth Metrics (Year 1 Targets)
- Total Users: 50,000
- Active Sellers: 2,000
- Transaction Volume: 311,000 codes
- GMV: 18.66M ZMW ($777K)
- Platform Revenue: 2.24M ZMW ($93K)
Engagement Metrics
- DAU/MAU Ratio: >25% (sticky product)
- Voting Participation: 70% of buyers vote
- Repeat Purchase Rate: 40%
- Seller Win Rate: >65% average
Financial Metrics
- Customer Acquisition Cost (CAC): <$10
- Lifetime Value (LTV): $50
- LTV/CAC Ratio: >3
- Monthly Recurring Revenue: 180K ZMW (Month 12)
🔐 Security & Compliance
Authentication & Authorization
- Phone number-based OTP authentication (passwordless)
- JWT access tokens (15min expiry) + refresh tokens (7 days)
- Role-based access control (Buyer, Seller, Admin)
- bcrypt password hashing (10 rounds)
Data Protection
- Betting codes hidden until purchased
- Refresh tokens hashed in database
- Environment variables for secrets
- HTTPS/TLS encryption in transit
- MongoDB encryption at rest
Compliance
- Age verification (18+ requirement)
- AML/KYC preparation for payment integrations
- Data protection (GDPR-inspired)
- Responsible gambling mechanisms (planned)
🚀 Next Milestones
Q1 2026 (Current)
- ✅ Backend API complete (33 endpoints)
- ✅ Frontend marketplace interface (80% complete)
- 🔄 Mobile money integration (MTN, Airtel)
- 🔄 Production deployment (Google Cloud Run)
- 📋 Beta launch (50 sellers, 500 users)
Q2 2025
- Public launch and marketing campaign
- Mobile app development (React Native)
- Advanced features (search filters, analytics)
- Scale to 2,000 users, 200 sellers
Q3-Q4 2025
- Regional expansion (Kenya, Nigeria)
- Multi-currency support
- Premium seller tiers
- AI fraud detection (early version)
📚 Documentation Sections
Complete product documentation including vision, roadmap, features, and technical specifications.
Business model, market analysis, competitive landscape, pricing, and go-to-market strategy.
Current sprint, backlog, sprint planning, git workflow, and deployment processes.
Business metrics (GMV, revenue, CAC) and product metrics (DAU/MAU, engagement, retention).
Testing Phone Number: +26878422613
Repository Locations:
- Backend API:
/home/laslie/Documents/omevision/companies/oddxer/dev/backend/oddxer-api/ - Documentation:
/home/laslie/Documents/omevision/companies/oddxer/oddxer-hub/docs/
External Links:
- Website: oddxer.com
- API: api.oddxer.com (production), dev-api.oddxer.com (development)
Last Updated: February 2026