Skip to content
The platform

Ticketing,
Built As A System.

Most ticketing platforms stop at the point of sale. MINGO is designed around what happens after. From creation to entry, every ticket operates inside a structured system that keeps control, visibility and pricing consistent.

TKT · 0x4A7E92

Late Checkout · Cork

Valid
GA · €28 Cork Opera House Apr 19
01
Issued Sarah K. · €28.00 face
Mar 14
14:02
02
Held Sarah K. · 25 days
Mar 14
→ Apr 8
03
Transferred → Aoife B. · €33.60 within cap
Apr 8
11:47
04
Validated Aoife B. · scanned at door
Apr 19
20:14:07

Rules

Enforced by the system
Live
Cap resale price 120% face
Max per buyer 4 tickets
Commission 10%
Transfer Platform-managed
After the sale

Where Traditional
Ticketing Falls Apart.

The issue is not buying tickets. It is what happens next. Most platforms step out at checkout. That is where everything starts to drift.

// after the sale · comparison view same ticket · two systems
Traditional ticketing

Control ends at checkout.

Tickets move outside the platform onto channels nobody controls.

Resale becomes uncontrolled. Caps and limits stop applying.

Prices drift far past face value. Fans pay markup. Organisers see none of it.

Organisers lose visibility on who actually holds the tickets.

MINGO Ticketing

Control continues end to end.

Tickets stay inside the system, from issue through to entry.

Resale operates inside defined rules. Caps and limits travel with the ticket.

Pricing stays in range. Anything above the cap is blocked at the platform level.

The current holder is always visible. At sale, after transfer, at the door.

The lifecycle

From Creation
To Entry.

A single record. Five states. One continuous system.

// ticket.lifecycle 5 states · 1 record
01

Create

Organisers define ticket types, pricing and rules.

TIERGA · €28
QTY1,200
RULESSET
02

Sell

Tickets are issued directly to buyers.

BUYERSarah K.
PRICE€28.00
STATEISSUED
03

Own

Each ticket stays tied to a holder and remains visible.

HOLDERSarah K.
SINCEMar 14
STATEOWNED
04

Resale

Tickets can be transferred or resold within defined rules.

CAP120% face
NEW HOLDERAoife B.
STATETRANSFERRED
05

Entry

Tickets are validated based on their current state.

HOLDERAoife B.
SCAN20:14:07
RESULTVALID
Rules + control

Rules That
Actually Hold.

On most platforms, rules rely on behaviour.

On MINGO, they are enforced by the system.

System enforcement

Applied to every ticket, every transaction

Live

Price limits are applied. Anything above the configured ceiling is blocked at the platform layer.

Resale conditions are enforced. Caps, holder limits and transfer windows travel with the ticket.

Tickets cannot be duplicated or misused easily. Validity is tied to the ticket's current state, not a screenshot.

Configured once. Enforced everywhere.

For organisers

Control continues after the sale. Pricing stays in range. Visibility holds across resale. Revenue stays close to the event.

For fans

A clearer, more predictable experience. Fair prices, real tickets, transfers that actually work, and entry that is straightforward at the door.

For the event

Pricing, supply and access stay aligned with how the event was meant to run. Nothing drifts off-platform unaccounted for.

The abstraction

All The Tech.
None Of The Hassle.

MINGO is built on distributed ledger technology. Every account is paired with a Hedera wallet. Every transaction is settled on-ledger. Every state change is recorded.

It's all there. You just never have to deal with any of it.

Most Web3 Ticketing

What the user has to do.

01 Install a wallet extension.
02 Connect the wallet to the site.
03 Buy crypto. Pay gas in crypto.
04 Sign and approve every transaction.
05 Manage seed phrases. Lose them, lose tickets.
MINGO Ticketing

What the user actually does.

01 Sign in. Email and password.
02 Buy a ticket. Card, Apple Pay, Google Pay.
03 Use the ticket. Scan it at the door.
04 // nothing else.
05 // nothing else.
How it holds together

The Integrity Model.

Every ticket has a typed state, a defined set of transitions, and a verifiable record.

Rules are written into the ticket itself, at the moment it is issued.

// ticket.integrity · spec sheet 6 properties · enforced by the system
State Model

Every ticket holds one of four typed states at any moment: Issued, Owned, Transferred, or Validated.

4 states
Transitions

Deterministic. A ticket cannot skip states. A validated ticket cannot transfer.

enforced at protocol
Rule Binding

Caps, limits and windows are encoded into the ticket at issue time. They travel with it.

travels with ticket
Immutability

Each state transition is written to a distributed ledger. The history of a ticket cannot be edited or rewritten.

cannot be altered
Verification

Anyone with a ticket ID can independently confirm its state and history. Without going through MINGO.

independently checkable
Idempotence

A ticket cannot be validated twice. Duplicate scans are rejected at the protocol level, not the door.

single use
The substrate

Built On Hedera.

Finality 3-5s

State updates settle in three to five seconds. Transfers and door scans feel instant, not eventual.

Cost $0.0001

Fees pegged in USD, not in HBAR. Your fee stays the same when the token price moves. No gas spikes during a hot drop.

Energy <0.001kWh / tx

A fraction of the energy of proof-of-work. Sustainable at the scale of every ticket sold to every event run.


Consensus Hashgraph aBFT
Security Quantum-resistant
Compliance ISO 27001
Get started

Run Your Next Event
With Us.

Set the rules. Sell tickets. Keep visibility from creation through to entry.