Tikkit X — offline-first event ticketing for Pakistan.
Pakistan's venues don't have reliable internet. Standard ticketing systems fail at the gate. We built the offline-first alternative — with cryptographic QR verification and local payment methods.
Pakistan's venues don't have reliable internet.
Standard digital ticketing assumes a cloud connection at the gate. For events in Pakistan — outdoor festivals, private halls, stadium entrances — that assumption is wrong. Network congestion when 5,000 people arrive simultaneously makes cloud-lookup QR verification unreliable.
The existing alternatives: paper tickets (easily forged), WhatsApp-based lists (unscalable), or international platforms with no local payment support and high foreign exchange fees.
Cryptographic verification. No internet required.
Each Tikkit X QR code contains an HMAC-SHA256 signature generated at ticket issuance. The gate scanner validates this signature locally — no network call required. If the signature is valid and the ticket has not been scanned before, entry is granted.
JazzCash and EasyPaisa integration means attendees pay with the wallets they already have. No credit card required. No foreign exchange fees. Funds settle in Pakistani rupees to the organiser.
Why we made the choices we made.
HMAC-SHA256 offline verification
Pakistani venues — particularly outdoor events, private halls, and stadium gates — have unreliable 4G coverage. Standard cloud-lookup QR verification fails under load when the network drops. HMAC-SHA256 embeds a cryptographic signature in the QR code that can be validated locally without a network call. The gate scanner app pre-caches the event's secret key and validates every ticket cryptographically, offline. This eliminates gate queues caused by network timeouts.
JazzCash and EasyPaisa (not Stripe)
Pakistan's two dominant mobile money platforms cover 80%+ of the addressable market for events. Credit card penetration in Pakistan is low — mobile wallet penetration is high. Building for Stripe would have been technically easier but commercially wrong. We integrated both payment gateways via their respective APIs and unified them behind a single internal payment interface.
React Native (not web-only)
The gate scanner use case requires a native mobile experience. A web app running in a browser cannot reliably access the camera, process QR codes at speed, or function offline in the way required. The organiser dashboard and attendee ticket wallet were also built as native screens, providing a consistent experience across the full product.
Freemium model with per-ticket fees
Charging organisers a monthly SaaS fee creates friction for first-time event organisers who may only run one event. A freemium model with per-ticket transaction fees aligns our revenue with our customers' success. As they sell more tickets, we earn more. This removes the upfront commitment barrier and accelerates adoption.
Multi-organiser Supabase schema
From day one, the data model supports multiple independent event organisers in the same database, isolated by Row-Level Security. This is not a feature added after launch — it is designed into the schema. A single-tenant design would have required a breaking migration to support the business model at scale.
Six weeks from concept to App Store.
Ready to build your SaaS?
We apply the same engineering discipline to every build. Book a scope session and we will map exactly what ships for your product.