I will build a secure backend with jwt auth, events, and ticketing apis


About this gig
I design and build robust backend APIs using ASP.NET Core, with a strong focus
on security, clean architecture, and long-term maintainability.
This gig is intended for projects that require a reliable backend foundation,
such as MVPs, SaaS products, or internal systems where a well-structured API
is critical.
What you can expect:
- Secure JWT-based authentication and authorization
- RESTful APIs developed with ASP.NET Core
- PostgreSQL database integration using EF Core
- Dockerized services for consistent and easy setup
- Clear API documentation via Swagger
- Clean, modular, and readable codebase
Based on the selected package, the solution may include authentication,
event and ticket management APIs, mock payment workflows, and PDF ticket
generation with QR codes.
Scope clarification:
- Backend development only (no frontend or UI)
- Real payment providers are not included by default
- Production deployment is not part of this service
I prioritize clear communication, realistic scope, and technically sound
solutions. If you need a backend that is built with care and clarity,
this gig is designed for you.
Get to know Okan GUMUS
Software Engineer
- FromTurkey
- Member sinceDec 2023
- Avg. response time4 days
Languages
English, Turkish
My Portfolio
Other Software Development Services I Offer
FAQ
Do you provide frontend or UI development?
No. This gig is for backend development only. Frontend or UI development is not included.
Is real payment integration included?
No. The premium package includes a mock payment flow only. Real payment providers like Stripe or PayPal can be added as an extra.
Will you deploy the backend to my server?
Deployment is not included by default. I can assist with deployment as an extra if needed.
Can you customize the backend for my project?
Yes, minor adjustments are included based on the selected package. Larger changes or new features may require a custom offer.
What do you need from me to start?
Project requirements, preferred features, and any existing documentation or API expectations are usually sufficient to get started.

