Tickets and pricing

Ticket types

You can create as many ticket types for one event as you like. Each type has its own name, price, capacity, sales period and restrictions.

• Free ticket: registration without payment
• Paid ticket: a fixed price in hryvnias
• Pay-what-you-want: the attendee chooses the price, from the minimum to the recommended one
• Pass: for an event series, one ticket gives access to all dates
• Hidden ticket: not shown on the event page, unlocked only with a coupon or access code

How to turn on paid tickets

To sell paid tickets, you first need to connect payments, otherwise only the free option is available in the ticket dialog. Here's what to do:

1. Open Payments in your organization settings (or in the "Payments" section of your profile).
2. Verify the payout recipient: enter the sole proprietor (FOP) details, IBAN and full name. We send them to the payment system to connect a sub-merchant.
3. Wait for confirmation. While the status is "Awaiting verification", you can't create paid tickets: this protects the money from going "nowhere".
4. Once confirmed, the "Paid" option with a price field becomes available in the ticket type dialog.

You can accept payments through Monobank (direct integration, Split Settlement) or LiqPay. One of them is enough to start selling.

How paid tickets work

• Payment = automatic confirmation. A successful payment confirms attendance and issues the ticket right away. Manual approval can't be turned on for paid tickets (unlike free ones).
• The spot is held during payment. While the guest is paying, their ticket holds a spot. If the payment isn't completed, the spot is released automatically, so capacity doesn't get "stuck".
• Money goes straight to the recipient. With Split Settlement, ticket revenue goes to your account and the platform fee is withheld separately: you don't need to transfer anything manually.
• Refunds are made from the same dashboard, and the money goes back the same way it came.
• A donation on top of the price. You can attach a Monobank jar to a paid ticket so the guest can add a voluntary contribution (see below).

Sellers: payouts to different sole proprietors (AOA Plus)

Sometimes money for different tickets of one event needs to go to different recipients: for example, the artist's fee to their own FOP and the rest to the organizer. For this, an organization has a list of sellers.

• The main seller receives payments for all tickets without a separately assigned seller and becomes the default recipient for new events.
• Inviting a seller. In the organization's "Payments" section you can invite someone as a seller by email. They accept the invitation in their own "Payments" and verify as a payout recipient.
• Assigning a seller to a ticket. In the ticket type dialog, a "Payout recipient" choice appears under the price: you can keep the main seller or choose another verified one.
• One payment, several recipients. If a guest buys tickets from different sellers in one order, the money is split between them automatically. This only works with Monobank; LiqPay supports one seller per payment.
• If a seller leaves, their tickets for future events automatically move to the main seller, while payouts already made and the sales history are kept.

This feature comes with an AOA Plus subscription. Without it, the regular single-recipient setup works: the organization's main seller.

Dynamic pricing (Early Bird to Last Call)

A ticket's price can change automatically as the event gets closer. You set up the ladder:

• Early Bird: the starting price, valid until a set date
• Standard: the main price after Early Bird ends
• Last Call: a higher price for the last days before the start

You can add as many tiers as you like. Each one has a price and a start date, and the system switches between them automatically, with no action from the organizer.

Capacity and sales

• Ticket capacity: a separate limit for each type (for example, only 20 VIP)
• Total event capacity: a shared limit across all tickets
• Sales start: the date and time the ticket becomes available
• Sales end: the date and time the ticket disappears from the form
• Approval: you can require manual approval for a specific ticket type

Event series

If an event has several dates, tickets can be tied to specific days or you can make a Pass for all of them. In the form, the attendee sees which dates each ticket is valid for.

Donation jar (a Monobank jar)

You can attach a link to a Monobank jar to a ticket, and the attendee will see an option to make an extra donation on top of the ticket price. This is especially useful for charity events.

Apple Wallet and calendar

After payment or registration, the ticket is automatically available to the guest in several formats:

• Apple Wallet: a signed .pkpass file with a QR code. The guest adds the ticket to their iPhone and uses it straight from Wallet at the door
• An .ics calendar file: the "Add to calendar" button adds the event to Google Calendar, Apple Calendar or Outlook in one tap; the .ics file also comes as an attachment in the registration email

These options are available automatically: there's nothing extra to set up.

Promo codes, coupons and referral discounts

Discounts and closed sales are handled by separate tools. Read more in Promoting events.

Platform fee

• Free events: no fee
• Paid events on the Free plan: a 5% platform fee on each ticket sold
• Paid events on the Plus plan: a 1% platform fee

Separately, Monobank internet acquiring charges 1.3% per transaction, and this fee is the same on both plans. Details and a calculator are on the for organizers page.