Nacth Store
A live digital commerce platform for game top-ups and vouchers, operating in production at nacthstore.com with instant transaction flows and controlled back-office management.
Nacth Store brings catalogue, checkout, payment, fulfilment, and content operations into one responsive commerce system. I designed the customer flow and engineered the platform across storefront, API, database, provider integration, and production deployment at nacthstore.com.
What needed solving
Game top-up catalogues become difficult to operate when storefront content, pricing, products, and fulfilment are managed in disconnected workflows.
What I built
I designed a unified storefront and administration experience that connects catalogue presentation with the operational controls behind it.
Why it matters
The platform is live and fully operating at nacthstore.com, passing all backend & frontend test suites with fast transaction response times.
How I approached it
I started by connecting the customer journey to the operational journey: catalogue discovery, top-up selection, transaction handling, and the dashboard actions needed to keep products accurate. The presentation follows that same order so visitors can understand the whole system, not just its storefront.
Tools & Workflow
Built and audited with Laravel, Tailwind CSS, JavaScript, MySQL, REST-oriented services, automated tests, linting, type checks, and a production build.
How this work wasvalidated.
- Full-stack implementation
- Storefront UX
- Operations dashboard
- Quality audit
From intention toimplementation.
Unify shopping and operations
Designed customer discovery and administrative controls as one coherent product system.
Audit the build
Validated tests, lint, types, and the production build before presenting the project.
Interface & Workflow Captures
Architecture at a Glance
Game catalogue, search, top-up flows, account access, and promotion surfaces.
Dashboard tools for game and voucher catalogue, pricing, promotions, and transactions.
Sistem webhook otomatis dengan pencatatan log transaksi yang aman dari manipulasi.
What this case study does not claim
- The production build completed but made one local API request to 127.0.0.1:4100; deployment needs an environment-specific API configuration.