Events & Tickets

Your own registration page, QR-code tickets and phone-based door checks — workshop to show, your event in one place.

Events & Tickets handles registration, tickets and the door for a business that runs workshops, seminars or small and mid-size shows. You set up the event and ticket types; attendees register on your own page without logging in and open their ticket on their phone. Door staff scan the QR code with a phone and entry is counted on the spot. Payments are taken manually (cash, card, bank transfer); the money goes straight to your account. It is not a marketplace: you publish your events on your own page with your own link.

Open account Write to us

Your account opens with Events & Tickets. It stays open for 15 days, no credit card needed.

How it works

01
Set up the event and ticket types
Enter the date, venue, capacity and registration cut-off; add free or paid ticket types and publish.
02
The attendee registers
You share the registration page link; the attendee registers without logging in, accepts the privacy notice and gets the ticket.
03
Record the payment by hand
For paid registrations you enter the cash, card or bank-transfer payment; once the total is covered the registration is confirmed and the QR code appears.
04
Scan at the door
Staff scan the QR code with a phone; the screen says admitted, already in, or invalid, and the counter updates live.

Who it’s for

Studios and businesses that run workshops and classes
Organisers of seminars, talks and training days
Venues running small and mid-size shows, concerts and private screenings
Anyone who wants to take registrations and sell tickets from their own page

Example

A pottery workshop

An illustrative flow; it does not describe a real business.

3 weeks before
The studio owner sets up a weekend workshop: capacity of 12, with “Single” and “Pair” (2 people) ticket types. They share the registration page link over WhatsApp.
2 weeks before
An attendee registers for a “Pair” ticket and enters both names; the registration waits for payment and the ticket page shows the transfer details and a reference code.
1 week before
When the transfer arrives the owner enters the payment; the registration is confirmed and the QR code appears. They remind the attendee about the ticket over WhatsApp, one person at a time.
Event day, 10:00
The person at the door scans the QR code with the phone camera on the door screen; two people are admitted and the counter updates. If the same code is scanned again it shows “already in”.
After the event
The report shows how many registered, how many came and the amount collected; an authorised person downloads the attendee list as CSV.

Live today

Events and ticket types

Event record: date and time, venue and map link, capacity, registration cut-off, cover image, title in three languages
Ticket types: free or paid, quota per type, sales start and end, limit per order
Attendee mode for multi-person tickets: one name and one QR code, a name per attendee, or a separate QR code per person
Draft, published, cancelled; at least one ticket type is needed to publish
One extra question per event: size, diet and so on
A finished or cancelled event is archived, not deleted

Registration page

A public registration page per event: no login, opens on the phone, with an address and QR code to share
The ticket price and the total (quantity × price) are shown up front; no fees added later
Acceptance of the privacy notice is required; you write the cancellation and refund terms yourself and they show on the page
A waiting list once the event is full (if you turn it on); you give a seat when one opens up
Bot protection and rate limiting; capacity and quota hold even with simultaneous registrations
Registration by hand from the panel and at the door

The attendee’s ticket

A no-login ticket page: large QR code, event details and registration code; opens on the phone
Add to calendar, open on the map, share over WhatsApp
For tickets awaiting payment the IBAN and a transfer reference code are shown; the QR code appears once payment is complete
With separate-QR tickets each attendee’s QR code is on its own card, so it can be passed to each person
Attendees can cancel their own registration within the window you allow
If the company’s Telegram bot is connected, the ticket page has a “Connect to Telegram” button

Door screen

Phone screen: scan the QR code with the camera; the result is green “admitted”, yellow “already in” or red “invalid”
Awaiting payment, cancelled, waiting list and another event’s code each show their own message
Manual search by name, registration code or the last 4 digits of the phone; door staff do not see contact details
A live entry counter; several staff can work at the same time
A yellow warning for codes scanned outside the event day: entry is not blocked and is recorded
An authorised user can undo a wrong entry

Payments, cancellations and refunds

Manual payments: cash, card or bank transfer; recorded on the shared sales receipt, partial payments allowed
A registration past its payment deadline is flagged in the list; you cancel it yourself (it does not drop automatically)
Voiding a receipt requires a reason; a voided receipt stays on record with its reason
When you cancel an event every paid registration goes to the “refunds due” list; the money is returned by hand
On an attendee or staff cancellation, a “no refund” decision requires a note

Messages, report and personal data

One-to-one messages: a ready-made WhatsApp message (from your own phone), email or a connected Telegram chat; no bulk sending
The message text is not stored; only when and through which channel it went is kept
Event report: occupancy, confirmed, awaiting payment, waiting list, admitted, no-shows, collected, refunds due; by ticket type
The attendee list downloads as CSV; only someone with export permission can do it, and the action is logged in the audit trail
The new-registration notification goes to the single user you choose (off by default)
No ID number is collected; IP addresses are not stored; door staff see only name, code and status; the viewer role sees phone and email masked
Roles: Events Admin, Staff, Door Staff, Viewer

Good to know

The ticket is an information ticket, not a tax document or e-Ticket. The payment receipt is not a tax document either. The ticket carries a note saying so.
There are no online card payments: payments are entered by hand (cash, card, bank transfer). The money goes straight to your account.
This is not a marketplace or an events showcase: your event appears only on your own registration page and the link you share. There are no seat maps.
Door checks need an internet connection; they do not work offline.
There is no bulk or scheduled messaging, and no automatic message when a waiting-list seat opens. Staff send each message to one person with a button.
An event can last at most 24 hours; there are no multi-day or recurring events. Capacity and venue permits are the organiser’s responsibility.
There is no retention period or automatic deletion for attendee records yet; records are not deleted, only cancelled or archived.

The shared core underneath

The same in every block: users, permissions, security and records.

Your own company space: Each company’s data is isolated from others and lives at its own address.
Roles and permissions per app: A separate role per user per app; managers see only their team.
Two-factor authentication: A code sent by email; turned on per company.
Audit log: Who changed what, and when — recorded.
You choose where your data lives: AWS Frankfurt (EU) by default; on request, your own servers (on-prem).
Interface in three languages: English · Turkish · Azerbaijani. Arabic can be added on request.

Next up

Planned, not live yet.

Online card payments
Multi-day and recurring events, coupons
Offline door checks