Gameket
[Client]
Gameket
[Year]
2024
[Project Focus]
- Let customers find, buy, and receive game top-ups and vouchers reliably.
- Keep checkout and fulfillment stable as catalog and traffic grow.
Scroll to explore
[Overview]
Gameket is a digital commerce and payments platform. Reliability is as important as the catalog.
[What I did]
- Developed backend APIs and service logic for orders, payments, and fulfillment
- Contributed to frontend features for product discovery and purchase workflows
- Improved platform stability and performance across core transaction paths
[The role]
Full-Stack Engineer
Njay
Project Info
Gameket is a marketplace for game top-ups, vouchers, and digital codes — including checkout in cryptocurrency. The catalog is the storefront. The product is whether a paid order still arrives when traffic increases or a payment provider stalls.
I worked across the stack: order, payment, and fulfillment APIs on the backend, and the discovery and checkout paths on the frontend. The requirement was one journey from product page to delivered code that the rest of the platform could grow around.
Overview
2024
Gameket is a marketplace for game top-ups, vouchers, and digital codes — including checkout in cryptocurrency. The catalog is the storefront. The product is whether a paid order still arrives when traffic increases or a payment provider stalls.
I worked across the stack: order, payment, and fulfillment APIs on the backend, and the discovery and checkout paths on the frontend. The requirement was one journey from product page to delivered code that the rest of the platform could grow around.
The Process
Backend work sat on the transaction path. Orders, payments, and fulfillment were implemented as services that report a clear state, rather than an unstructured set of status fields. GraphQL and Node.js handled the contract the Next.js storefront needed to render a purchase.
On the frontend I contributed the paths customers use: finding a product, choosing a denomination, and completing checkout without losing the order if they pause. Those screens were wired to the same order model the fulfillment side consumes.
Stability work followed the transaction path. When catalog size and traffic grew, the changes were on the core path — query shape, payment confirmation, and fulfillment retries — rather than secondary optimizations on non-transactional pages.
The Outcome
Customers can find a top-up or voucher, pay, and receive it through a path that remains intact as the catalog expands. Checkout and fulfillment operate as one system, with consistent order status.
The platform can accept more products and more traffic without the transaction path becoming the first point of failure.