Ticketing

4.5 out of 56 sold

The ticket itself: issued to a person, transferable on your terms, refundable on your policy, and valid when the venue wifi is not.

From$799

Open the preview Request a quote

Function: 22
User types: 2
Platform: iOS & Android

React Native
TypeScript
PostgreSQL
Expo

Inside the app

What it does out of the box

22 connected functions on one schema across 2 user types. Everything below is in the template before a line of customisation.

Wallet
Every ticket on the phone and valid offline. A door queue does not wait for connectivity, and a flat battery is the holder’s problem you should still solve.
Named tickets
Issued to a person rather than to a code, which is what makes transfer controllable and touting harder.
Transfer
To a named recipient on your rules, with the chain recorded. Blocking transfer entirely just moves it to a car park.
Refunds
Against the policy you set, shown before purchase rather than discovered at the point of asking.
Void
One ticket, individually, with a reason. A system where the only remedy is cancelling an order is a system that punishes the wrong person.
Audit
Issue, transfer, refund and void all recorded against the ticket. Disputes at a door are settled from a record rather than a memory.

User types

Two apps, one ticket.

A ticket is a small contract. The holder needs it to work at a door with no signal, and the organiser needs to be able to void exactly one of them without touching the rest.

User
2 of 4 screens
The holder
Holds their tickets, transfers one to a friend on your rules, and requests a refund without emailing anybody.
Preview as the user
- Every ticket on the phone, offline
- Transfer to a named person
- Refund request with the rule shown
- Ticket stays valid if the phone dies
- History of what was transferred
Event owner
2 of 4 screens
The organiser
Controls issuance, transfer and refund policy, and can see and void an individual ticket when something goes wrong.
Preview as the event owner
- Issue, reissue and void individually
- Transfer rules you set
- Refunds against your policy
- Duplicate and fraud attempts flagged
- Every action recorded against the ticket

The limits

What this is not.

The same list we give for every app in the catalogue, because the fastest way to a bad project is a promise made in a meeting that nobody wrote down.

It carries no audience
A ticketing platform’s fee partly buys discovery. This sells to people you can already reach.
We do not process payments
Ticket money runs through your own payment provider account, which is what removes the per-ticket cut.
It is not a resale marketplace
It transfers a ticket between named people. A secondary market with pricing and settlement is a much larger build with its own regulation.
It does not replace door hardware
Scanning works on standard phones. Turnstiles and access control are integrations we scope rather than assume.

Questions

Questions, answered plainly.

If yours is not here, ask it on the call rather than guessing from a pricing page.

Not covered here?

Ask a consultant directly. No form to fill in first, and no follow-up sequence.

Book a consultant All questions

Do tickets work without a signal?

Yes. The ticket is held on the device and validated locally at the door. A venue with poor signal is the normal case, not the exception.

Should we allow transfers?

Usually yes, on your rules. Blocking transfer entirely does not stop it happening, it just moves it somewhere you cannot see or control.

Can we void a single ticket?

Yes, individually and with a reason recorded. Cancelling a whole order to deal with one bad ticket punishes people who did nothing wrong.

What if somebody turns up with a dead phone?

The door list holds the named attendee, so they can be found and admitted manually with the ticket marked used. That path exists because it always happens.

Do I get the source code?

Yes. Both apps, API, schema, migrations and deployment configuration transfer on delivery.