Events & ticketing case study

myTickets.africa

The whole organiser ecosystem: sell tickets, run the gate and get paid, from one platform.

The problem

African event organisers were stitching together a ticket site, a spreadsheet of buyers, a gate list, an SMS tool and a mobile-money till, and reconciling it all by hand after every event.

Who myTickets.africa serves

Four sides, each with its own app, all running on one shared core.

Ticket buyers

Web and mobile app

Discover events by category and date
Pick seats on a live stadium map
Pay by M-Pesa or card, with a multi-tier cart
Find tickets and orders without an account

Organisers

Organiser dashboard and mobile app

Create events, ticket types and inventory
Invite a team with owner, manager and gate roles
Run promoters, nominations and custom forms
See sales analytics and request payouts to M-Pesa, till, paybill or bank
Message buyers with bulk SMS

Gate staff

Scanner app

Scan tickets at the door, one entry per ticket
Every scan logged for disputes
Door reports per gate and device

Operations

Back office

Reconcile every payment daily
Ledger of every money movement
Commission rules per organiser
Approve payouts with a second approver
Refunds, organiser verification and audit trail

Shared core

Go ticketing API
Payments service: M-Pesa, Airtel Money, card
Message queue for payments and SMS
Postgres ledger
Poster and media storage

Outcome

One platform covers the whole event, from discovery to payout. It was load-tested in August 2026 ahead of tournament-scale demand.

Stack

Go, Next.js, Expo, Bun, Postgres, RabbitMQ, M-Pesa, Airtel Money, Paystack

Build something like this Visit the live site