Stripe checkout for itinerary purchases and access-cod engine - Audio Tour Platform
Budget / Salary€8–30
TypeFreelance project
LocationRemote
Posted1 hour ago
ZenaWalk is already live in development: the core Flask back-end, MySQL schema, vanilla-JS front-end, user authentication, the certified-guide itinerary editor and an admin dashboard are all in place. I now need the remaining production-grade pieces so I can launch publicly.
Key work I still need:
• Stripe checkout for itinerary purchases – a straightforward one-off payment flow that creates an order record, marks the itinerary as owned and triggers a receipt email. No subscriptions or split payouts for this release.
• Access-code engine – codes can be reused up to a configurable limit (for example one code good for ten unlocks) and must track remaining uses in the database. The admin panel already has a stub page ready for this.
• Transactional email pipeline – on successful payment send a branded payment-receipt email via my existing SendGrid account (templates are drafted in HTML).
• Five-language support – surface text strings through Flask-Babel (or similar) so Italian, English, French, German and Spanish translations can be dropped in easily; front-end language switcher is already designed.
• Security hardening – CSRF everywhere, strict session cookies, secure headers, rate-limiting on auth routes and a once-over for common Flask pitfalls.
• Production deployment – Dockerise if you prefer, then deliver an Ansible playbook or simple bash scripts that spin everything up on an Ubuntu 22.04 VPS behind Nginx with Let’s Encrypt.
Acceptance criteria
1. Card payment completes end-to-end in Stripe test mode and records the order in MySQL.
2. A multi-use code’s remaining uses decrement correctly and block when exhausted.
3. Payment receipt email lands in the inbox with correct localisation tokens.
4. Switching language reloads strings without a page refresh.
5. OWASP ZAP scan reports no high-severity issues.
6. A fresh VPS deploys the stack in one command and passes the above tests.
Repo is on GitHub; I’ll add you as a collaborator. I’m happy to clarify the existing schema and share Postman collections for the current API.
Key work I still need:
• Stripe checkout for itinerary purchases – a straightforward one-off payment flow that creates an order record, marks the itinerary as owned and triggers a receipt email. No subscriptions or split payouts for this release.
• Access-code engine – codes can be reused up to a configurable limit (for example one code good for ten unlocks) and must track remaining uses in the database. The admin panel already has a stub page ready for this.
• Transactional email pipeline – on successful payment send a branded payment-receipt email via my existing SendGrid account (templates are drafted in HTML).
• Five-language support – surface text strings through Flask-Babel (or similar) so Italian, English, French, German and Spanish translations can be dropped in easily; front-end language switcher is already designed.
• Security hardening – CSRF everywhere, strict session cookies, secure headers, rate-limiting on auth routes and a once-over for common Flask pitfalls.
• Production deployment – Dockerise if you prefer, then deliver an Ansible playbook or simple bash scripts that spin everything up on an Ubuntu 22.04 VPS behind Nginx with Let’s Encrypt.
Acceptance criteria
1. Card payment completes end-to-end in Stripe test mode and records the order in MySQL.
2. A multi-use code’s remaining uses decrement correctly and block when exhausted.
3. Payment receipt email lands in the inbox with correct localisation tokens.
4. Switching language reloads strings without a page refresh.
5. OWASP ZAP scan reports no high-severity issues.
6. A fresh VPS deploys the stack in one command and passes the above tests.
Repo is on GitHub; I’ll add you as a collaborator. I’m happy to clarify the existing schema and share Postman collections for the current API.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.