From ticket type to money in the account, in one place
Ticket types and prices, a basket for a team, promo codes, payment by card or bank transfer, refunds, a fiscal receipt and the ticket on the buyer’s phone. One sale, one set of data, from offer to receipt.
A ticket for all days or selected ones — with phased prices
Standard, VIP, student: you describe the ticket types, and the buyer sees them side by side and compares what each includes. The price moves to the next phase on its own when the previous phase sells out or its date passes.
- Price phases for every ticket type
- A ticket for all days of the event or only selected ones
- Quantity and sales period for every phase
A company buys tickets for the whole team in one order
The team lead puts as many tickets as needed into one basket — of one type or several — and pays once. Every ticket gets its own link: a colleague registers themselves and gets their own QR at the entrance.
- Quantity discount: from three tickets, from five, from ten
- A separate registration link for every ticket
- A reminder when someone on the team hasn’t registered yet
A promo code for a partner, a community or a newsletter
One shared code with a usage limit — or a batch of single-use codes to hand out to partners and communities one by one. The code applies on top of the quantity discount.
- A percentage or fixed discount, with a validity window
- Only for selected ticket types or partner packages
- For performances of a series — also for specific hall zones and dates
Card, monobank, LiqPay, WayForPay or bank transfer
The buyer pays by card through a connected provider. A company pays by bank transfer: it enters its details and gets a PDF invoice straight away, and a manager confirms the payment with the “Money received” button.
- Payment on the platform page or on the organizer’s site
- A transfer from a person or a company — with a PDF invoice
- Its own set of payment methods for every event
Card payment works once a payment provider is connected
- Stripe
- monobank
- LiqPay
- WayForPay
- Bank transfer
The fee is visible before payment, and a manager starts refunds
The service fee sits in the basket as a separate line before payment. The refund rule — the share or amount the event keeps, and the deadline — is shown to the buyer in advance too. A manager starts a card refund from the order card, and the system calculates the amount.
- A fee as a percentage, a fixed amount or both
- A refund rule and deadline for every event
- For performances of a series — refunds for individual tickets of an order
Several sellers in one organization — with invoices and settlements
Each seller is a separate legal entity with its own details, VAT rates and payment accounts. Invoices follow the seller’s details, and the settlement ledger records every sale, refund and fee.
- Seller profiles and their payment accounts
- PDF invoices in the document language
- A settlement ledger exported without buyer data
A fiscal receipt through Checkbox and the offer next to payment
The receipt for a card payment is issued automatically and stays with the order, and a return receipt follows a refund. The buyer sees the offer, refund rules and privacy policy next to the pay button — in the current version.
- The service fee as a separate line on the receipt
- Seller documents with versions and an archive
- The version the buyer saw is recorded
Receipts work once Checkbox is connected
- Checkbox
A performance ticket — on the phone, as a PDF or in Wallet
For performances of a series every ticket has its own page with a QR, date, hall and seat. The buyer downloads a PDF to print or forward, or adds the ticket to Apple Wallet or Google Wallet. At a conference the participant badge is the entry document.
- A ticket page: performance, hall, row, seat and QR
- A PDF to print or forward
- Apple Wallet and Google Wallet
A guest without a ticket? The desk operator sells one
A guest comes to the desk without a ticket — the operator sells one at the current price, takes cash or a card terminal payment and prints the badge straight away. The quota applies here too: nothing sells beyond it.
- A sale at the current phase price, with a promo code
- Cash or card terminal payment — with a receipt
- Registration and badge right after payment
Questions and answers
Which payment methods are there?
Card through Stripe, monobank, LiqPay or WayForPay, and bank transfer. Card payment works once a payment provider is connected; you choose the set of methods for every event.
Can a company pay?
Yes. The company chooses bank transfer, enters its details and gets a PDF invoice straight away. When the money arrives, a manager confirms the payment on the order card.
How do refunds work?
The refund rule is set for the event, and the buyer sees it before paying. A manager starts a card refund from the order card — one order at a time, with the amount calculated by the system. For performances of a series you can refund individual tickets of an order.
Do I need a fiscal register?
Aditum issues fiscal receipts through Checkbox, so it needs to be connected. A bank transfer gets no receipt — an invoice is issued for it instead.
Can I sell on my own website?
Yes. The buyer pays on the platform page or on your site’s payment page, depending on how the event website is connected.
What sits next to ticket sales
Tell us about your event — we’ll show it on yours
A 30-minute call: we set the demo up for your event — your categories, approvals, zones and desks. We reply within one business day.
Tell us about your event — we’ll show it on yours
A demo is a 30-minute call with the team that develops Aditum. Not slides but your scenario: we set up categories, approvals, zones and desks for your event.
- Fill in the form: event type, number of participants, a few words about it
- Within one business day we email you to agree a time
- On the call we show Aditum configured for your event and answer your questions