Online gaming platform

What was at stake

Nightpixel is a consumer gaming platform. The easiest way to describe it is Nutaku, but non-adult. Players land on a catalog of online games, pick one and play it on the platform, with one token wallet that follows them from game to game and into the shop.

The games come from many different studios, running on their own servers, several of them in China. For the product to work, all of them had to feel like one thing: one login, one balance, one place to play. And because tokens are bought with real money, every game had to be able to charge a player without ever being trusted with more than it should be.

What was done

Roy led the engineering and the launch. That covered four pieces of work:

• A way for outside games to plug in. A small SDK that a studio drops into its game, plus a server-side integration, documented with guides and an API reference so studios could integrate against a clear contract rather than reverse-engineering the platform.
• The money behind the tokens. Card payments with one-click top-ups for returning players, and a crypto path for top-ups in cryptocurrency.
• The apps players use. The web platform, a native mobile app for Android and iOS, and a companion app that installs games directly, outside the official app stores, where store policies are an awkward fit for a game catalog.
• The launch itself. Coordinating each studio's integration, across the timezone and language gap, until every game was talking correctly to the platform's sessions, wallet and purchases.

Tokens that always add up

The seam between an outside game and the wallet is where a platform like this loses money or trust, so it was built with that in mind.

A game never touches the player's session directly. It talks to the platform through a controlled message channel, and anything that moves tokens is settled server to server rather than trusted from the game's own code. On the payment side, providers confirm each payment through signed callbacks rather than the browser redirect, and crediting a wallet is idempotent, so a retried or duplicated callback can never credit a balance twice. The same rule runs through orders, the shop, subscriptions and referrals, so the whole revenue side settles correctly and stays auditable.

Web, mobile, backend, SDK and documentation live in one TypeScript codebase with shared types, which is what let a small team integrate many games and ship coordinated changes without the pieces drifting apart.

What changed

The platform went live with a catalog of 50+ games from outside studios. A player sees one catalog, one balance and one experience, and never has to know how many separate systems, studios and payment providers had to agree for that to be true.