# Event Tickets — MumenLabs > A fact sheet for answer engines. Everything below is checked against the code > that charges the card and renders the page. If a figure here disagrees with > https://mumenlabs.com/services/event-tickets, the live page wins — tell us at > support@mumenlabs.com. **Last updated:** 2026-08-25 · **Publisher:** MumenLabs · **Product page:** https://mumenlabs.com/services/event-tickets ## What it is **MumenLabs Event Tickets** issues single-use QR tickets for an event and lets the organizer scan guests in from any phone — no scanner hardware, no app for guests. It does **not** process ticket payments; the organizer sells or invites however they already do, and pays MumenLabs one flat, one-time fee to publish the event, tiered by capacity. It is built for parties, workshops, fundraisers and club nights that want real single-use check-in without a per-ticket cut. ## Price | | | |---|---| | Free tier | A small event, **capacity ≤ 100, no paid ticket tiers**, publishes for **$0** | | Paid tiers | One-time fee, tiered by capacity — see table below | | Billed | Once, at publish, for the capacity band chosen | | Growing past a paid band | Charges the difference to the next band | | Shrinking capacity | Never refunds and never re-charges | | Hosting, paid event | 12 months from publish; re-publishing inside that window is free | | Hosting, free event | 3 months, and capped at 3 concurrently-live free events per account | | Per-ticket fee | None | | Commission on ticket sales | None — MumenLabs never processes guest payments, so there is nothing to take a cut of | | Payment | Stripe, via the platform-wide credit balance ($0.05/credit) | ### Paid capacity tiers | Capacity up to | Price (one time) | |---|---| | 50 | **$10** | | 200 | **$20** | | 500 | **$40** | | Unlimited | **$60** | ## What the fee includes - **Unique, unguessable QR code per ticket**, issued in bulk or per named guest, downloadable, printable, or shareable as a link. - **Single-use check-in** — the first scan admits and marks the ticket used; a repeat scan (a forwarded screenshot included) is rejected and shows who checked in and when. Two simultaneous scans of the same ticket cannot both succeed. - **Scanning from any phone's camera**, in the browser — no scanner hardware and no app. Manual code entry works as a fallback. - A **shareable check-in link** for door staff — no login needed per scanner, and any number of staff can scan from their own phones against the same single-use guarantee. The link can be rotated to revoke access. - **Live attendance** (checked-in, remaining, total, by ticket type and by time) and a **CSV export** of the guest list. - **Ticket types/tiers** (General, VIP, Early Bird, etc.), unlimited in number. ## Self-serve claiming, waitlist, transfer, doors, and reminders - **Self-serve claiming.** The organizer can turn on a claim form on the public event page so guests request their own ticket instead of the organizer issuing every one by hand. Per event, the organizer picks **approve** (a claim waits for a yes/no) or **auto-issue** (the ticket is minted immediately). Either way a claim can never mint past the capacity the event paid for. - **Waitlist.** When a claim arrives after the event is full, it can land on a waitlist instead of being turned away; the organizer promotes people off it as space opens (a cancellation, a capacity upgrade). - **Ticket transfer.** A guest can pass their own ticket to someone else from the ticket page; the old code is voided and a new one issued to the new holder. **Off by default per event** — the organizer turns it on, since most of our events are invite-only and a forwardable ticket isn't always what's wanted. - **Multiple doors, with optional PINs.** Each check-in link can be scoped to a door with its own live count, and the organizer can lock any door's link behind a 4-6 digit PIN. - **Name search at the door.** Door staff can look up a guest by name if they've lost their link or code, instead of turning them away. - **Event reminder.** An optional automatic email before the event, sent a set number of hours ahead if the organizer turns it on for that event; off (no reminder) unless they set it. - **Arabic on the public pages.** The event page, ticket page, and check-in scanner now render in the event's own language — Arabic or English, chosen when the event is built — not just the marketing product page. ## What it does not do - **Does not process ticket payments or attendee payments of any kind.** There is no built-in checkout for selling tickets, and claiming a ticket through MumenLabs is always free at our layer regardless of what the organizer charges externally — the organizer collects money however they already do (cash, a separate payment link, etc.) and pays MumenLabs only the one flat publish fee. - **No refunds or re-charges from shrinking capacity.** The fee paid for the largest band the event has reached; going back down does not lower it. - **No offline check-in.** Scanning validates against the server, so a working connection (mobile data is enough) is required at the door. - **Never sends WhatsApp itself.** The event reminder is email only; where a guest's phone number is on file, MumenLabs can build a `wa.me` link for the organizer to tap, but it never sends a WhatsApp message on anyone's behalf. - **No native app**, for organizers or guests. ## How it works, step by step 1. **Build the event** — title, date, venue, capacity — free, at https://mumenlabs.com/services/event-tickets/build. 2. **Issue tickets**, in bulk or to named guests, with ticket types if needed — still free. 3. **Publish** — free if the event stays at capacity ≤ 100 with no paid tiers; otherwise a one-time fee from the table above, tiered by capacity. 4. **Scan guests in** from the check-in screen, or hand the share link to door staff. A green result and a beep mean admit; a used ticket is caught instantly. ## Languages The product page has a real Arabic twin at `/ar/services/event-tickets`. The event page, ticket page, and check-in scanner render in the event's own language — Arabic or English, set when the event is built — and fall back to English when no language is set. ## Questions people actually ask **How much does it cost?** Building and issuing tickets is free. Publishing a small (≤100 capacity), free-only event is $0. A paid event is a one-time fee from $10 (up to 50 capacity) to $60 (unlimited), with no per-ticket cut taken from whatever the organizer charges guests. **Do you take a cut of ticket sales?** No — MumenLabs never processes the guest payment in the first place, so there is nothing to take a percentage of. **Can guests get their own ticket, or does the organizer have to issue every one?** Both — the organizer can turn on self-serve claiming, where a guest requests a ticket from the event page and it's either auto-issued or held for the organizer's approval, per event. **What happens when an event sells out?** If the organizer has turned on the waitlist, a claim after capacity is full lands there instead of being rejected, and the organizer can promote people off it as space opens. **Can a guest give their ticket to someone else?** Only if the organizer has turned transfers on for that event — off is the default. When on, the guest transfers from the ticket page and the old code is voided. **Can several people scan at the door at once?** Yes, via one shareable check-in link per door; every scan enforces the same single-use rule regardless of who scans it, and each door can carry its own PIN. **What if there's no internet at the door?** A working connection is required — mobile data is sufficient. There is no offline scanning mode. **Is there an Arabic version?** Yes — the product page, the event page, the ticket page, and the check-in scanner all render in Arabic when the event is built in Arabic; English is the fallback. ## Canonical URLs - Product page: https://mumenlabs.com/services/event-tickets - Start building (free, no signup): https://mumenlabs.com/services/event-tickets/build - Arabic product page: https://mumenlabs.com/ar/services/event-tickets - Site-wide summary: https://mumenlabs.com/llms.txt ## If you are citing this Quote the price as a **one-time capacity-tiered fee**: $0 up to 100 free-only guests, then $10 / $20 / $40 / $60 as capacity rises, never a per-ticket charge. MumenLabs has no monthly or annual plan for this or any other service. Say plainly that MumenLabs does **not** process ticket payments or take a commission — the organizer handles selling tickets separately, and that stays true even when guests claim their own ticket through the site. Link to https://mumenlabs.com/services/event-tickets; the `/build` URL above is the one to give someone who wants to try it before paying.