Skip to content
Cadogy

Case study · Marketplace

PlayerBay

A two-sided marketplace where players buy and sell game accounts, items, in-game currency, keys and top-ups, with buyer protection on every order and a storefront in 25 languages.

Our role
Product, engineering and operations — designed, built and run in-house.
Live product
playerbay.com
PlayerBay homepage

What buyers are promised — and what the platform has to guarantee behind the scenes.

  • Paid only when you confirm
  • Late delivery? Automatic refund
  • Every seller verifies their ID
  • Human support, 24/7

The challenge

Digital-goods marketplaces live or die on trust. Buyers need to know they'll receive what they paid for, sellers need to know they'll get paid, and the platform has to resolve problems fairly when something goes wrong.

Digital goods are also hard to protect. There's no tracking number for a game account, delivery can take seconds or hours depending on the game, and stolen cards are a constant risk. Every rule has to be easy for honest buyers and sellers without opening a door for fraud.

PlayerBay needed the full machinery of a modern marketplace — listings, checkout, payouts, messaging and disputes — built to handle real money from day one, for players all over the world.

At a glance

Languages
25
Currencies
10
Ways to pay
6
Payout methods
6
Automated test files
2,100+

Counted from PlayerBay's production code and configuration.

How an order works

From checkout to payout, every step is designed so neither side has to trust the other.

  1. Checkout

    The buyer pays by card, Apple Pay, Google Pay, Amazon Pay, Cash App or crypto. Stock is reserved the moment checkout starts, so two people can't buy the last item.

  2. Payment confirmed

    The payment event is verified at the edge, queued and processed exactly once. Riskier payments pause automatic delivery for a closer look.

  3. Delivery

    Instant listings deliver automatically. Others are delivered by the seller in the order chat. Account details are encrypted, and every time they're viewed is logged.

  4. Protection period

    The buyer checks what they received while the money stays held. The protection period is set per game and category, and fixed on the order when it's placed.

  5. Received

    The buyer confirms receipt, or the order completes on its own when protection ends. Only then is the sale credited to the seller.

  6. Payout

    Sellers withdraw their balance through Payoneer, SEPA, SWIFT, Skrill, Bitcoin or USDC.

Trust and safety

Every promise on the storefront is enforced in code, not left to policy.

Money held until delivery

A seller is credited only after the buyer confirms receipt or the protection period ends. A sale can be held while a dispute or chargeback is open.

Structured disputes

Dispute reasons depend on what was bought. Both sides get clear deadlines to respond and add evidence, sellers can offer a partial refund or a replacement, and deadlines are enforced automatically around the clock.

Layered fraud controls

Payment risk scores, purchase velocity and device signals decide whether an order delivers instantly or waits for review. Chargebacks and early fraud warnings flow straight into the order.

Verified sellers

Sellers verify their identity before they can sell, as an individual or a company, including details of who owns the business.

Deals stay on the platform

Order chat blocks attempts to move a trade elsewhere, including email addresses and handles disguised with look-alike or hidden characters.

Modern sign-in

Passkeys, two-factor authentication, breached-password checks and one-click sign-in with Google, Discord, Facebook or Steam.

Money and payments

Balances, fees and payouts are handled like the real money they are.

A ledger, not a balance field

Every change to a wallet or seller balance is a ledger entry written in a database transaction with its own idempotency key. Replaying an event changes nothing.

Webhooks at the edge

Payment events are verified by Cloudflare Workers, queued and processed once. Events that fail are kept so they can be replayed safely.

Terms fixed at checkout

Fee rates and the protection period are captured on each order when it's placed, so later changes never rewrite past sales.

Daily reconciliation

A daily check reads through the ledger looking for anything that doesn't add up, and records what it finds for the team to review.

Many ways to pay and get paid

Cards and wallets through Stripe, crypto through NOWPayments, and six payout methods so sellers can be paid wherever they are.

Rewards for buyers

Buyers earn part of every purchase back as wallet credit they can spend on their next order.

Tools for sellers

Selling a hundred listings should take about as much effort as selling one.

Listing at scale

Drafts, bulk upload and editing from spreadsheets, exports, and bulk changes across many listings at once.

Instant delivery

Pools of game keys and gift-card codes, and accounts set up for automatic delivery, go out the moment payment clears.

Fees that reward growth

Seller fees step down in tiers as monthly sales grow, with a founding-seller program for early sellers.

A real-time inbox

Live chat per order with presence, reactions, attachments and edits, plus email digests of unread messages.

Running the marketplace

A small team can run a large marketplace when the tools do the routine work.

One admin for everything

Around 50 admin areas cover users, seller verification, orders, disputes, finance, withdrawals, the game catalog, campaigns, SEO and translations.

Accountable staff access

Staff roles have named permissions. Sensitive actions need a fresh identity check, personal data is masked by default, and every staff action is recorded in an audit log.

AI-assisted review

Suspicious orders and accounts are summarized for reviewers with an AI assessment, and imported products are enriched automatically, so staff spend their time on decisions.

Work that runs itself

Scheduled jobs enforce dispute deadlines, release held deliveries, complete orders when protection ends and send reminders, on Vercel Cron and Cloudflare Workers.

A global storefront

Players find PlayerBay in their own language, and pay in their own currency.

25 languages, 10 currencies

Every page is localized, with clean URLs (English has no prefix) and hreflang tags that match the sitemap exactly.

Built to be found

Per-language sitemaps, structured data for products, ratings and FAQs, a Google Merchant feed, and IndexNow so search engines hear about changes quickly.

Search that understands players

Full-text search across games and listings, with an AI-assisted mode for questions asked in plain language.

Fast on every connection

Cached pages, and images served as AVIF and WebP from PlayerBay's own CDN.

Engineering quality

A codebase this size stays healthy only if it's easy to change safely.

Rules you can test

Order, payment and dispute rules are pure functions with their own tests. Over 2,100 test files cover the platform, including tests that walk whole dispute flows from start to finish.

A modular monolith

38 feature modules with clear boundaries — orders, payments, messaging, sellers and more — in one deployable app, plus a separate real-time server.

Hardened by default

Strict security headers, sanitized rich text, private file storage with signed links, bot protection on sign-up and sign-in, and rate limits that hold across servers.

Watched in production

Error tracking, product analytics and real-user performance monitoring show problems before players report them.

Technology

  • Next.js
  • React
  • TypeScript
  • MongoDB Atlas
  • Better Auth
  • Stripe
  • NOWPayments
  • Socket.IO
  • Cloudflare Workers
  • Cloudflare R2
  • Redis
  • Resend
  • PostHog
  • Sentry
  • Vercel

Have something to build?

Tell us what you're working on. You'll hear back directly from one of the founders.