Tennis League Registration & Scoring DB

I need a purpose-built database that runs an entire tennis league season from online sign-up through to final standings. Only our league administrators will log directly into the back-end, authenticated with a straightforward username-and-password system. Players will meet us through public web forms, but all of their activity—registration, fee payments, match results—must flow cleanly into the same data store. Core workflow • Registration: players enter contact details, pick divisions, and immediately pay their fees. The system has to process Credit/Debit Card, PayPal, and Bank Transfer without forcing us into a single gateway. • Scheduling: after registration closes, I drop in league parameters (divisions, courts, dates) and the database auto-generates a season’s fixture list that avoids duplicates and honors availability constraints. • Match day: players enter and record each result (sets, games, tiebreaks). The moment a score is saved, current standings and individual player records update. • Reporting: at any time I can pull a clean export—season standings, head-to-head stats, or payment summaries—for sharing with coaches or publishing on our site. Acceptance criteria 1. A relational database schema delivered in SQL (MySQL or PostgreSQL) with tables for users, payments, fixtures, results, and standings. 2. Clear API or admin panel to perform every task above without direct SQL edits. 3. Role-based authentication restricted to administrators. 4. Payment integration demo showing all three methods posting test transactions into the Payments table. 5. Documentation that lets a developer new to the project deploy the database, connect the payment gateways, and trigger the scheduling script. Clean architecture and readable code matter more than fancy UI. Once the database, scripts, and admin interface hit the acceptance criteria, the job is done.

Project ID: 40561478