Everything on Teeckets, explained step by step. Written for an organiser selling tickets for the first time.
Teeckets is a South African ticketing platform. You create an event, set up the tickets you want to sell, and share one link. People buy from that link, get a ticket with a QR code by email, and you scan them in at the door.
There is no upfront charge to create an event. Teeckets deducts 3.6% processing and the selected capacity-package fee from eligible sales before paying the organiser's net balance. If sales revenue is below the package fee, the proceeds are forfeited and no payout is made.
Create an account and add the bank details Teeckets should use for eligible payouts.
Create the event, choose a capacity band, add your ticket types and prices.
Publish and share the link. Buyers pay by card or EFT and get a QR ticket.
Give your door staff a PIN, scan tickets in, and reconcile the sales record afterwards.
Teeckets handles concerts, festivals, summits and conferences, expos, sports fixtures, gala dinners, comedy and theatre, church and community gatherings, workshops and training. If your event is not on the list, choose Other and type your own description - it appears on the public page exactly as you write it.
There is no password to choose, forget, reuse or leak. You sign in with a six digit PIN sent to your email address, and each PIN works once. If somebody gets hold of your old email, they still cannot get in without access to your inbox right now.
Open the login page and switch to the sign-up form.
Full name or trading name, email address and mobile number.
A six digit PIN arrives by email within a minute.
Type the PIN and your account is created and signed in.
Enter your email address and choose Email me a PIN. The email that arrives gives you two ways in:
A PIN and its sign-in button are valid for 10 minutes. After that, ask for a new one.
Using either the digits or the button retires both. Requesting a new PIN also kills the button in the older email.
Five wrong entries and the PIN is discarded. Request a new one - nothing is locked permanently.
One minute between sends, and five requests per 15 minutes. This protects your inbox from being flooded.
Check the spam or promotions folder first - automated mail lands there more often than anywhere else. Confirm the address you typed has no typo. If a minute has passed and there is still nothing, request another. If two requests produce nothing, contact support rather than requesting a third.
New organiser accounts are ready to create events immediately. Identity verification is currently disconnected while Teeckets Collect is the active public payment model.
Buyers pay Teeckets and eligible organiser funds are settled after the event. Keep your organiser contact and bank details accurate so a payout is not delayed.
There are two arrangements, and the difference is simply whose merchant account the buyer's card is charged by. Set yours up under Admin → Payment methods.
| Arrangement | Who the buyer pays | When you get the money |
|---|---|---|
| Collected by Teeckets the default |
Teeckets, into the platform account | From 24 hours after the event ends, on request from your Sales Record |
| Direct to you | You, straight into your own gateway | Immediately, on your gateway's own settlement cycle. The money never touches Teeckets |
New organisers start on Collected by Teeckets. Direct is granted by a Teeckets super administrator, because it requires you to hold live gateway credentials and to be trusted with money for an event that has not happened yet. Neither is something to hand out by default. Ask support if you want to be moved across.
Card and instant EFT. Paste your merchant ID, merchant key and passphrase, then copy the notify URL Teeckets shows you into your PayFast settings.
Card. Paste your secret key, then register the webhook address Teeckets shows you in your Yoco dashboard.
Your banking details are shown at checkout and the buyer uploads proof of payment. You approve it and the ticket is issued.
Each one carries your organiser number, so an incoming payment notification is matched to the credentials that signed it. Copy the address exactly as the screen gives it to you. If you paste somebody else's, or trim the part after the question mark, payments will not be recognised.
Teeckets deducts 3.6% processing from the event payout. If you are VAT registered you can switch VAT on, set your rate, say whether your prices already include it, and add your VAT number so it prints on the buyer's receipt.
The dashboard is the first thing you see after signing in. The menu has four places to go:
Create an event. This is where a new event and its ticket types are set up together.
Every event you have created, published or not, with a link into each one's Event Operator.
Your referral link, earnings, banking details and withdrawals. See section 14.
Your profile, verification, payment methods and account settings.
A badge appears on the Events header when something needs you - most often a proof of payment waiting to be approved.
On a phone, the menu collapses behind the button in the top corner. Everything works on a phone, including the door scanner, which is designed for it.
Choose New Event and work down the form. Select the correct capacity package; there is no payment step when the event is created.
What kind of event it is, and what it is called.
Date, start and end time, venue name and address.
How many tickets you intend to sell. This sets the fee - see section 16. Choose R0.00 Tickets / Free Event if nothing is being sold.
Your price bands, set up here rather than afterwards.
Cover image and a colour theme for the public page.
Create the event without an upfront charge. Its link starts working as soon as it is published.
The package is checked against what you are actually selling, not taken on trust, and it is checked continuously - not only on this form. Adding a ticket type later, enlarging one, putting a draft on sale or drawing extra seats on a map are all measured against the band, so an event cannot quietly outgrow the package it was created under. Only tickets that are on sale count; drafts do not.
Its fee is deducted from payout, so select the band that covers the full ticket inventory. If you get it wrong you are not stuck with it - the band can be changed later from Event Details, and section 16 explains what that does and does not affect. The largest published package covers 10 000 tickets; contact Teeckets for a larger event.
Refresh your events list once. If the event is still missing, correct any validation message on the form or contact support; event creation no longer waits for a payment confirmation.
Open any event from My Events and you land in the Event Operator - one screen with a row of tabs, each doing one job. This is where you spend nearly all of your time.
| Tab | What it does |
|---|---|
| Overview | The state of the event at a glance, and its public link |
| Ticket Manager | Create and edit ticket types, prices, quantities and sale status |
| Reserved Seating | Seat maps and numbered seats. See section 9 |
| Ticket Sales | Every order, who bought it, what they paid and its state |
| Ticket Coupons | Discount codes for this event. See section 10 |
| Proof of Payment | EFT payments waiting for you to approve or decline |
| Attendants | Door staff and their scanning PINs. See section 12 |
| Scanner | Scan tickets at the door, and see what has been scanned |
| Sales Record | What you have taken, and where to request a payout |
| Refunds | Refunds you have granted and their banking details |
| Custom Links | Your own sections on the public page - links, files, embedded media and images |
| Short Link | A short, memorable address for the event |
The rest of the tabs fill in what people see before they buy. Use as many or as few as suit your event - anything you leave empty simply does not appear.
The tabs above cover what most events need. Custom Links covers everything else: it adds your own sections to the public page, in your own words, and each one appears alongside the built-in sections.
Sections can be reordered, edited and removed at any time, and anything you leave out simply does not appear. There is no limit on how many you add.
The Venue and Food sections take a picture of their own, on top of their text - the room, the stage, the menu. Every photograph on the public page, including the gallery and your custom sections, opens full size when a visitor taps it, so a floor plan or a menu can actually be read on a phone.
Teeckets grew out of an earlier product, and one or two tabs from that era may still be visible on your event. They are being retired and are not part of selling tickets. If a tab is not described in this guide, you do not need it.
A ticket type is one price band - Early Bird, General, VIP, Top Deck. You can have as many as you need, each with its own price, quantity and rules.
| Status | What buyers see |
|---|---|
| Draft | Nothing. Hidden completely while you set it up |
| On sale | Visible and buyable |
| Paused | Visible but not buyable. Use this to hold a tier back without hiding it |
| Ended | Visible and closed. Use it for an Early Bird that has run its course |
The moment a ticket type has sold a single ticket, its price can no longer be changed. Every order already placed recorded what it charged, and your wallet, the payout split and any refund all work from those stored amounts - so editing the price afterwards would not change a cent that was collected, it would only make the tier disagree with its own history. The same applies to switching a sold type between paid and complimentary.
Running a price change is still straightforward: set the current type to Ended and add a new one at the new price. Buyers who already paid keep exactly what they bought, and your records stay readable. A sold type cannot be deleted either, and its quantity cannot be set below the number already sold.
A draft costs you no capacity. It is not on sale, holds no seat and sells nothing, so you can build next month's tier at any quantity you like without the capacity band objecting to work in progress. The Ticket band card on Event Details shows drafts separately, marked as not counted.
The band has its say when you put the draft on sale. If opening it would take the event past what your package covers, Teeckets refuses and tells you both ways out - the quantity that would fit, and the package that would cover it, with its fee. Nothing is changed until you choose one.
Two people buying the last ticket at the same moment is the normal case at an on-sale, not an edge case. Teeckets locks the count while a purchase completes, so the second buyer is told it has gone rather than both being sold the same ticket.
An unpaid card order holds its tickets for 20 minutes and then releases them, which is long enough to finish a payment without an abandoned checkout keeping seats off sale all day. EFT orders do not expire on a timer - a transfer can take a day to clear - and are released when you decline the proof of payment.
For events where people buy a specific seat rather than general admission. Buyers pick their seats off a picture of your venue, and each ticket carries its section, row and seat number.
A picture of your venue layout, attached to the ticket type it belongs to.
Name it, pick its ticket type, and give it rows - for example A:18, B:20, C:14.
Drag the markers onto the printed seats, or let the detector find them for you.
Enable seating for the event and the seat picker replaces the quantity box.
A section can be drawn three ways, so one venue can mix them: seat for individual numbered chairs, table for round tables of seats at a gala or banquet, and section for a whole standing or terrace area sold as a block.
While somebody is choosing, their seats are held so nobody else can take them. A buyer gets one selection window per event, and seats go back on sale automatically if they walk away. Seats attached to a completed sale are marked sold, and seats on a refunded ticket return to the map by themselves.
Create codes under Ticket Coupons in the Event Operator. A code can take off a percentage or a fixed rand amount, and you can limit how many times it is used.
Buyers type the code on the event page before checking out and see the new total immediately, so there is no surprise at the payment step. A code that is expired, used up or simply wrong is refused there and then with a plain explanation.
The discount is recalculated from your settings when the order is created, never taken from what the browser claims. A code cannot be edited in a page to make a ticket cheaper.
A ticket buyer never signs up for anything. There is no account, no password and no PIN to create - they should not have to become a Teeckets user to come to your event.
Every price on the checkout is worked out on the server from your settings. Nothing the browser says about money is trusted, so a form field claiming a price of R1 is simply ignored.
A buyer who refreshes the page, loses signal or comes back later that day finds their cart still there, with the same types and quantities. It is kept in their own browser for 24 hours - nothing is reserved and no stock is held, so it costs you nothing.
It is cleared at one moment only: when they go through to the payment gateway. A declined card or a closed payment window brings them back with their cart intact, so they can try again without rebuilding the order - which is exactly when losing it would cost you the sale. Reserved seats work differently: those come back from the seat hold on the server rather than from the browser, so if the hold has expired the seats are honestly gone rather than reappearing when somebody else has them.
The buyer gets an email with their order reference and a PIN. Those two open their ticket page, where each ticket has its own QR code, ready to show at the door or print. If they lose the email, the same reference and PIN get them back in - you can find the reference for them under Ticket Sales.
When an EFT buyer has made the transfer, they upload proof from their order page. It lands in your Proof of Payment tab with the order beside it. Approve it and the tickets are issued and emailed. Decline it and the buyer is told why and the tickets go back on sale.
If your sales are collected by Teeckets, the money lands in an account you cannot see, so proof of payment is confirmed by a Teeckets super administrator rather than by you, and the tab will not appear on your event. If you are paid directly, it is your own bank account and your own call, and you approve it yourself.
The door scanner is a web page. There is no app to install and nothing for your staff to sign up for - it works on any phone with a camera.
Under Attendants, add each person working the door. Each gets their own PIN, emailed to them, which is all they need to open the scanner. They never see your dashboard, your sales or your banking details - only the scanner for the one event.
Every scan is logged with the attendant and the time, so a dispute at the door has an answer. You can see the running count and the full list from the Scanner tab while the event is on.
Sharing one PIN between the whole door team costs you the only record of who let which ticket through, and means removing one person's access removes everybody's. Adding an attendant takes a few seconds.
A per-event log of what you have taken: every order, what it was worth, and how it was paid. If you are paid directly by your gateway, this is the record you reconcile against your own gateway statement - it is a log, not a balance you draw down.
Funds are held until 24 hours after your event ends, then you request a payout from the Sales Record and it is paid to the bank account on your file. The 24 hours exist so that anything that goes wrong on the night can still be put right before the money moves.
Refund an order from the Ticket Sales tab. The tickets are cancelled, any reserved seats go back on the map automatically, and the buyer is emailed a private link to claim the money.
The buyer opens that link and enters their banking details themselves. That is deliberate: you should not be collecting and storing somebody's bank account over email, and the person owed the money has no Teeckets account to sign into. Their details appear in your Refunds tab when they submit them, and you mark the refund as paid once you have sent it.
The Event Operator has a field for it and it appears on your public page. Saying up front what happens if somebody cannot come, or if the event moves, prevents most refund arguments before they start.
Bring other organisers to Teeckets and earn commission on what they pay to create events. It costs nothing to join and there is no approval to wait for.
Open Affiliate from the dashboard menu and become a partner. It is active immediately.
You get a short referral link and a code. Anybody arriving through it is attributed to you for 30 days.
Enter the account your commission should be paid into.
Request a withdrawal whenever you have a balance. There is no minimum.
Your affiliate screen shows clicks, the organisers you have signed up, every commission you have earned and the history of your withdrawals.
You are signed out after 30 minutes without activity. A minute before it happens a warning appears with a countdown and a Stay signed in button - one tap and you carry on. If nobody answers it, you land on a page that says your session expired, with a button straight back to sign-in.
Your own events and nobody else's. Every screen checks the event belongs to you before it shows you anything.
The door scanner for one event. No dashboard, no sales figures, no banking details.
Teeckets staff. They see the platform to approve verifications and settle payouts.
Under Admin you can change your display name and contact number yourself. Your email address is the login identifier and the owner key on every event, so it is changed by support rather than in the form.
Select a capacity package when creating the event. No payment is taken then; the package fee and 3.6% card processing are deducted from eligible proceeds at payout.
| Capacity | Fee |
|---|---|
| R0.00 tickets / free event | No fee |
| 1 - 500 tickets | R2 000 |
| 501 - 1 000 tickets | R5 500 |
| 1 001 - 3 000 tickets | R18 500 |
| 3 001 - 5 000 tickets | R33 800 |
| 5 001 - 7 000 tickets | R47 400 |
| 7 001 - 10 000 tickets | R55 000 |
Choose R0.00 Tickets / Free Event as the capacity band and the event costs nothing, start to finish - no package fee and no processing, because nothing is being processed. The trade is that every ticket has to stay at R0.00: a free event cannot put a price on a ticket. If you decide to start charging, change the band first (see below) and the price fields open up.
Teeckets deducts the selected package fee plus 3.6% card processing, then pays the organiser's net balance. If eligible ticket-sale revenue is below the selected package fee, all sales proceeds are forfeited and no organiser payout is due.
Card processing is the payment gateway's own charge and is passed through in full - Teeckets keeps none of it. The gateway currently levies 3.69%, so that is the figure you will see itemised on your payout breakdown and on each order in the wallet ledger.
The band is not locked in at creation. Open Event Details on the Event Operator and you will find a Ticket band card showing the current package, how many tickets are on sale against it, and what will be deducted at payout. Move up or down and the payout figure follows immediately.
Nothing else moves. Ticket prices, existing orders, what buyers paid and everything already recorded in the wallet stay exactly as they are - only the fee deducted at payout changes. A band that will not fit what you are already selling is shown greyed out with the reason, so you can see at a glance which packages are available to you.
Because no creation payment is taken, creation-fee coupons no longer apply.
The button works once. This also happens if you requested a newer PIN, which retires the button in the older email. Ask for a fresh PIN and use the newest email.
Check the ticket type's status in Ticket Manager - Draft and Paused both stop a sale. Then check the quantity has not run out, and that any sale window you set has not closed. If seating is on, all the seats in that section may be held or sold.
Confirmation arrives from the gateway separately from the buyer's browser and can take a minute. Refresh Ticket Sales first. If it is still missing, check that the notify or webhook address in your gateway matches exactly what the Payment Methods screen shows, including everything after the question mark. Contact support with the order reference and nothing will be lost.
Open the layout editor and zoom to the block you are placing. Drag the markers onto the printed seats, using Box select to move a whole row at once, and Undo move if a drag goes wrong. Save when it looks right - nothing is stored until you do.
The warning names the attendant and the time of the first scan. Usually the ticket was scanned twice at the same door, or the buyer forwarded their ticket to somebody who arrived first. The scan log in the Scanner tab has the full history.
Your sales are collected by Teeckets, so the money is in an account you cannot check and a Teeckets super administrator approves EFT proof instead. If you would rather handle it yourself, ask support about being paid directly.
Sessions end after 30 minutes without activity. A warning with a Stay signed in button appears a minute beforehand. Sign in again and continue - nothing you saved is lost, though anything typed and not saved will need redoing.
Have a question this guide didn't answer? Reach out - we're here to help you succeed.
%20logo.png)