Fantasy Sports Platforms in India: Regulatory and Technical Primer
Fantasy sports is one of India's largest digital categories, and one of the most regulatorily complex. Building a platform requires understanding both. Here's the primer.
Key takeaways
- Fantasy sports is legal in most Indian states; some prohibit it (Andhra Pradesh, Telangana, Tamil Nadu have restrictions).
- Skill-based vs chance-based classification matters legally; design for skill.
- Architecture must handle peak concurrency (millions during marquee matches).
- Real-time scoring requires high-quality data feeds.
- Payment, KYC, AML compliance is mandatory.
The regulatory landscape
Skill vs chance
Indian courts have held that fantasy sports involving knowledge and judgment is a game of skill, not chance, legal in most states. But some states explicitly restrict or ban (TN, AP, TG with varying scope).
State-by-state restriction
Geo-block restricted states from contest entry. Maintain current list, laws change.
KYC and AML
PMLA applies. KYC required at deposit thresholds. Real-name verification.
Taxation
TDS on winnings. GST on platform fees. Plan integration with tax compliance early.
Self-exclusion and responsible gaming
Mandatory features in most regulated digital gaming.
Technical architecture
Contests engine
Create contests pre-match. Slot fills as users join. Lock at match start.
Team builder
User picks players, manages credits, captain/vice-captain.
Real-time scoring
Live match data feeds in. Update fantasy scores every event. Push to user.
Leaderboard at scale
Millions of users in one contest. Sub-second rank computation. Specialized data structures.
Payouts
After match ends, winners determined. Withdrawals to user bank accounts.
Mobile-first
Most fantasy users on mobile. Native iOS/Android.
Scale
Marquee IPL matches: 10M+ concurrent users. 100M+ contest entries. Sub-second rank updates.
Architecture:
- Sharded contest storage
- Redis for leaderboards (sorted sets)
- Kafka for event streams
- Aggressive CDN caching for static content
- Pre-warming for known peak times
Data feeds
Live match data (ball-by-ball cricket, play-by-play football) from licensed providers, typically expensive. Negotiate at scale.
Reliability matters: data feed lag = user complaints.
Anti-fraud
Common patterns:
- Multi-account abuse (same user with many accounts)
- Bots
- Match-fixing related (rare but reputational)
Detection: device fingerprinting, behavioral analysis, network graph for related accounts.
Common pitfalls
Treating it as a generic mobile app. Fantasy has unique scale and regulatory needs.
Underestimating data feed cost. Real-time data is expensive.
No state geo-blocking. Legal risk.
Latency in scoring. User trust depends on accuracy and speed.
What we recommend
Plan for IPL-scale from day one if cricket-heavy. Negotiate data feeds carefully. Comply with state geo restrictions actively. Build responsible gaming features as first-class.
FAQs
Dream11 architecture? Proprietary. Several public talks describe high-level approaches.
Daily fantasy vs season-long? Both common; daily more popular in India.
Legal advice needed? Yes. Engage Indian counsel.