Ever feel tired of ticketmasters downtime and poor queue management? Fear not, because with EventGo, you will never have to worry about your seat being stolen by another user.
EventGo's Key Features:
- Ticket Transfer
- Never get scammed again! Transfer your tickets worry free between users on EventGo, where we manage the payments for you. Tickets are only transferred when the buyer pays successfully!
- Split Payment
↔️ - Buying for your friends? EventGo offers seamless split payment methods, so you never have to worry if you have enough money to cover the whole group!
- Managed Event Cancellation ❌
- Remeber when Justin Bieber cancelled his tour.. EventGo maanges these events fuss free, ensuring that ticket holders are kept in the loop and promptly refunded.
To set up Stripe with this application, you will have to set up the Stripe webhook listener. Run the following commands in your terminal
stripe login
stripe listen --forward-to localhost:8010/webhookMake sure to take note of the webhook secret given by Stripe
- Copy the content of
eventgo-backend/.env.exampleand paste intoeventgo-backend/.env
cd eventgo-backend
cp .env.example .env- Replace Stripe Secret Key and Webhook Key with your own
STRIPE_SECRET_KEY=sk_test_...
STRIPE_WEBHOOK_SECRET=whsec_...- Seed the data and start the containers. This has been managed via a script
python restart_docker.py OR
python3 restart_docker.py- Install dependencies
cd eventgo-frontend
npm i
- Populate
.env.local
Copy the content of eventgo-frontend/.env.example and rename it to eventgo-frontend/.env.local.
cp .env.example .env.local- Replace the Stripe Public Key with your own:
NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY=********npm run dev
To test our functionalities, you can log in with the following credentials:
- "email": "admin@eventgo.com", "password": "admin", "role": "admin",
- "email": "user1@example.com", "password": "password", "role": "user",
- "email": "user2@example.com", "password": "password", "role": "user",
- "email": "user3@example.com", "password": "password", "role": "user",
*For Scenarios with timeout (i.e. Scenario #3), the timeout duration has been reduced to 1 minute for demonstration purposes. To effectively perform split payment, party member has to pay within 1 min or else split payment will not work. This is set up to demonstrate us triggering the timeout mechanism which will conditionally release Bob's ticket as per video demo.
Video Demo Link: https://www.youtube.com/watch?v=DokQSL0xvL0
| Scenario | Problem | Solution | Key Concepts Demonstrated |
|---|---|---|---|
| #1 - Event Cancellation + Automatic Refunds | Users are left confused or frustrated when events are canceled without timely updates or refunds. | Admin cancels an event, triggering automatic refunds, status updates, and real-time email notifications. | - Microservice orchestration - Asynchronous processing via AMQP - Composite service for cancellation - Stripe refund integration - Personalized notifications |
| #2 - Ticket Transfer & Resale via Stripe | Peer-to-peer ticket reselling often leads to fraud, fake tickets, or payment disputes. | EventGo enables authenticated ticket transfers and payments directly in-app, using Stripe and email notifications. | - Two-phase orchestration pattern - Payment link generation with Stripe - Direct ticket ownership transfer through EventGo - Message-based communication - Secure ticketing ecosystem |
| #3 - Split Payment for Group Booking | Group leaders face financial risk or inconvenience when booking tickets for friends. | Split booking lets users share payment responsibilities. Reserved seats timeout if not paid in 10 minutes. | - Split payment orchestration - Timeout-based logic - Conditional refund handling - Coordinated microservices - Notification queue system |
| Bonus: #0 - Basic Event Booking with Timeout | Users may abandon the booking mid-payment, locking seats and limiting availability. | Implements a 10-minute timer to release unpaid reservations, ensuring fairness. | - Timeout with delayed function - Booking validation via Stripe - Ticket status management - Real-time user notification via AMQP |