Running events and payment links in Tixello
Tixello sells your tickets, takes your RSVPs and pays the money straight into your own bank account. If your website is one of ours, most of the setup has already happened before you log in. This guide covers what's already done for you, what you do yourself, and the handful of settings that are worth getting right the first time.
On this page
On this page
- Start here
- If your website is one of ours
- Signing in and finding things
- Creating an event yourself
- Ticket types, prices and capacity
- Making the event page look right
- Publishing and sharing the link
- Payment links for things that aren't events
- On the day: check-in and door sales
- Emailing everyone who's coming
- The money: Stripe, payouts and refunds
- Promo codes
- Numbers and exports
- Who can log in
- Questions
- Print the pre-flight card
Most venues start using Tixello for one event and then discover the other half of it: it will take a payment for anything at all. A bus trip, a members' raffle book, a deposit on a function room, a fundraiser plate. If you can describe the thing and put a price on it, you can have a link for it in about five minutes — and that link works from a Facebook post, a text message, or a QR code on a poster in the foyer.
If you only read one thing
- The money is yours from the moment it's paid. It goes into your own Stripe account and out to your bank — Tixello never holds it.
- If we built your website, your events are already in Tixello. You don't create them. Log in to see sales, names and numbers.
- Nothing is live until you publish it. A new event sits as a draft until you press the button, so it's safe to build it half-finished.
- Check the date, the time and the price before publishing. Prices in particular are awkward to change once tickets have sold — see ticket types.
- It isn't only for events. Anything you'd take money for can be a link — see payment links.
01 — The short versionIf your website is one of ours
Venues on a Caidence website get the setup done for them. When an event goes onto your site, the matching Tixello event, its ticket types and its payment link are created at the same time and the link is wired into the What's On listing. Nobody at your end has to build anything.
What that means day to day:
- You don't create the event. Send us the event the way you always do — poster, dates, prices, what's included — and it appears on the website and in Tixello together.
- You log in to look, not to build. Sign in when you want to know how many have sold, who's coming, or what's been taken so far.
- The Book now button on your site is the Tixello link. Same page, same checkout, whether someone arrives from your website, a Facebook post or a QR code.
- You can still edit it. Everything in this guide works on an event we created for you — change the description, add a ticket type, pause sales.
The link stands up by itself and can be pasted anywhere — Facebook, Instagram bio, an email, a QR code on a poster. A website that lists your events makes it easier for people to find, but it isn't required to sell a ticket. The rest of this guide is written for both.
02 — Getting inSigning in and finding things
Tixello lives at app.tixello.com.au. You sign in with your own email address and a password we email you — there's no shared venue login, because the whole point is being able to see who did what.
Once you're in, there are five things down the left-hand side and they do what they say:
| Where | What it's for |
|---|---|
| Dashboard | The quick glance — revenue this month and all-time, tickets issued, RSVPs, upcoming events and the most recent orders. |
| Events | Every event you've got, with how many have sold and whether it's published. This is where most of your time goes. |
| Orders | Every transaction, newest first. One order can contain several tickets. Filter by event, status or type. |
| Attendees | Every individual person holding a ticket, across all events. Searchable by name or email, and exportable. |
| Promo codes | Discount codes for paid events. |
An order and an attendee aren't the same thing, and the difference catches people out. One member buying four tickets is one order and four attendees. When you're counting chairs, use Attendees. When you're reconciling money, use Orders.
03 — Building oneCreating an event yourself
From Events, press New event. The first screen is deliberately short — it only asks for enough to create the thing, and everything else is added afterwards.
The New event screen
- Title
- What it's called. This is the heading on the public page and the subject people see in their ticket email, so write it the way you'd write it on a poster.
- Description
- The sell. Headings, bold, bullet lists and links all work. You can come back and add images and extra sections once the event exists.
- Location
- The venue name and street address, in full. It's printed on the ticket and it's what someone puts into their maps app.
- Timezone
- Defaults to your venue's. Worth a glance in the weeks either side of daylight saving if you're near the border.
- Starts / Ends
- Start is required, end is optional but worth filling in — "4:00pm–7:00pm" reads much better than a start time alone.
- Capacity
- Total heads for the whole event. Leave it blank for unlimited. You can also cap each ticket type separately — see below.
- Booking fee mode
- Absorb or Pass through — who wears the booking fee. See the note below.
- Cover image
- Optional, but the page looks half-finished without one. Use the event artwork, landscape, at full size.
Press Create event and it's saved as a draft. Nothing is public yet, and no ticket can be bought until you add ticket types and publish.
Absorb means the price on the poster is the price the member pays, and the fee comes out of your take. Pass through means the fee is added at checkout on top of the ticket price. Most clubs choose absorb, because "$20" that turns into $21.40 at the checkout is the single most common complaint about online ticketing. Pick one and use it for everything, so your members aren't guessing. Note that the booking fee only applies at all in pass-through mode.
04 — TicketsTicket types, prices and capacity
Open the event and go to the Tickets tab. Every event needs at least one ticket type, even a free one — that's the thing people actually select at checkout.
Press Add and you get five fields:
| Field | What to put | Notes |
|---|---|---|
| Name | Adult · Concession · Member · Child | What it says on the ticket. Be specific — "Child (with an adult)" saves a conversation at the door. |
| Price (AUD) | Leave at 0 for free | A free ticket type is how you run an RSVP. Free and paid types can sit side by side on the same event. |
| Booking fee (AUD) | Usually leave alone | Only charged if the event is set to pass through. |
| Capacity | Blank = unlimited | Caps this ticket type specifically — 40 members' tickets on a 100-seat night, for example. |
| Status | Active or Paused | Pause takes it off sale without deleting it or losing anyone who's already bought. |
Pause is the useful one. Early-bird finished, members' allocation gone, kitchen has capped the sit-down numbers — pause the ticket type and it disappears from the checkout while everything already sold stays exactly as it is. Deleting is almost never what you want.
Card prices can't be edited in place once they exist — behind the scenes a price change creates a brand new price and retires the old one. It works, and it's the correct behaviour, but it means people who bought at the old price stay at the old price, and your reporting now has two figures in it for one ticket. Far easier to check the number twice before it goes live than to explain the difference to a member who paid $25 when their mate paid $20.
Below the ticket types is Custom attendee fields. Name and email are always collected, so you only need this for extras — dietary requirements, table or group name, member number, a bus pick-up point. Add them before you publish; adding one halfway through means the people who booked early never answered it.
05 — The pageMaking the event page look right
Two tabs control what the public sees. Everything on both applies to the live page as soon as you save.
Content
Your description sits at the top. Underneath it, Page blocks let you add proper sections rather than one long paragraph — pick a type per block, fill in its fields, reorder with the arrows:
| Block | Good for |
|---|---|
| Highlights | The three or four things that sell it. The most-used block, and the one that most improves a thin page. |
| Agenda | Run sheets — doors 6:00, dinner 7:00, band 8:30. Answers the question everyone rings up to ask. |
| FAQ | Dress code, parking, courtesy bus, whether kids are welcome, what happens if it rains. |
| Gallery / Video | Photos from last year's, or the promo clip. Nothing sells a returning event like a picture of the last one. |
| Organizer | Who to contact and how — worth adding if the functions team, not the front desk, is fielding the calls. |
| Sponsors | Sponsor logos, when a sponsorship agreement says they'll be on the event page. |
| Map | Handy for anything off-site — a golf day, a bus trip, a partner venue. |
| Quote / Rich text / Divider | A testimonial, an extra block of free text, or a line to break up a long page. |
Design
Your club's colours, logo and fonts are already set once, centrally, and every event inherits them — so you shouldn't normally need this tab at all. It's there for the one-off: a themed night that wants its own accent colour, a dark background behind a light poster, or a page where the ticket panel reads better below the content than beside it. Leave a field blank and it inherits. If in doubt, leave it alone — a consistent look across every event is worth more than a bespoke one.
06 — Going livePublishing and sharing the link
Down the right-hand side of the event is the Publish panel. Press it and the page goes live and starts accepting bookings; Unpublish takes it straight back off sale without deleting anything.
Underneath is the Public URL with a Copy button. That's the link, and it's the only thing you need to share. Every event has its own — there's no single page listing all your events, which is exactly why your website's What's On page matters.
Where to put it:
- Your website's event listing — automatic if we built your site.
- The Facebook event and post, and your Instagram bio link.
- The members' newsletter — on the button, not typed out as raw text.
- A QR code on posters, table talkers and the screens. Send us the link and we'll send back a print-quality QR code, or put it straight onto the artwork for you. Generating them inside Tixello is on its way — until then, just ask.
Before it goes anywhere, tap the link on your own phone and read it the way a member would. Date right? Price right? Photo not cropped through somebody's head? It takes thirty seconds and it catches nearly everything. Don't complete a purchase to test it — if you want a genuine end-to-end test, ask us and we'll run one.
Holding the tickets back
By default a ticket is emailed the instant someone pays. On the event's Details tab, Tickets send date changes that: buyers still get an immediate order confirmation, but the ticket itself doesn't go out until the date you choose. Useful when the artwork isn't finished, when seat or table allocations are decided later, or when you'd simply rather the ticket land in someone's inbox the week of the event than three months before it.
07 — The other halfPayment links for things that aren't events
This is the part most venues don't realise they have. Tixello only really knows one trick — publish a page, take a payment, email a receipt — and nothing forces that page to be an event. Anything you'd otherwise take cash or an EFTPOS payment for at the desk can be a link instead.
Things clubs use it for:
| Instead of | Make a link for |
|---|---|
| Collecting cash for a bus trip | Seats on the bus, capped at the number of seats. The capacity does the counting for you. |
| Chasing a function deposit | A "Function room deposit" link, texted to the person booking. Paid before they hang up. |
| Selling raffle books behind the bar | A book of tickets, with a cap if there's a limited run. |
| Taking fundraiser donations | Fixed amounts — $10, $25, $50 — as separate ticket types. |
| Nominations for a comp | An entry fee, with the team name collected as a custom field. |
| Member merchandise | Shirt, cap, stubby holder — one ticket type each, capped at what you have in the cupboard. |
You build it exactly the same way: New event, give it a plain name people will recognise on their bank statement, put a date on it (use the closing date if there's no actual event), add a ticket type per thing being paid for, publish, copy the link. Then text it, post it, or hand it over as a QR code.
It's a payment page, not a shop. There's no stock control beyond the capacity number and no postage or delivery step, so it suits collect-at-the-club far better than anything you'd have to send.
Fundraising and raffles have their own rules. Trade promotions, raffles and public fundraising are regulated differently in NSW and QLD, and taking the money online doesn't change what permit you need. Check with whoever handles your compliance before you publish it — this guide is about the software, not the licensing.
08 — On the nightCheck-in and door sales
Checking people in
Open the event and press Check in at the top right. Point the camera at the QR code on someone's ticket and it checks them in; if the camera won't play or someone's turned up with a printout, type the ticket code into Manual entry instead. A running Checked in count sits on the same screen.
Practical notes for the door:
- Use a phone or tablet, not the office PC. The camera scanner needs a camera, and it needs you to allow camera access the first time.
- Sign in before the doors open, not while there's a queue. Have the check-in screen already up.
- Keep the Attendees list open on a second device. Someone will arrive having deleted the email, and finding them by surname is faster than arguing about it.
- Have a plan for no internet. Print or export the attendee list that afternoon. A paper list and a pen has saved more events than any app.
Someone who isn't on the list
Go to Attendees and press Add attendee. Choose the ticket type, put in their first name, surname and email, and they're added and issued a ticket. That covers the walk-up who paid at the door, the committee member who was always coming, the raffle winner, the sponsor's guests.
The one thing to be clear about: adding someone here doesn't take any money. It records that they hold a ticket. If they've paid cash at the door, that cash still has to go through your till the way it always has, or your Tixello figures and your takings won't agree.
The pencil beside each attendee corrects a name, email or phone number — worth doing rather than adding a duplicate, because a wrong email means the ticket never arrives. The paper-plane icon beside each attendee and each order resends the ticket, which answers the most common phone call you'll get.
09 — Telling themEmailing everyone who's coming
On the event page, under Communications, Email attendees writes to everyone holding a ticket or RSVP for that event. Give it a subject and a message and send.
It's the right tool for the things that come up between selling the ticket and the night itself:
- A reminder two or three days out, with the start time and where to park.
- A change of room, time or line-up.
- Weather calls for anything outdoors.
- A thank-you afterwards, with the date of the next one.
There's no draft, no preview and no test send. Write it somewhere else, read it back, then paste it in. Check the date and time in the message against the date and time on the event — a reminder email with the wrong start time is worse than no reminder at all.
And keep it to this event. People gave you their address to buy a ticket, not to join a mailing list; general club marketing belongs in your newsletter where members have opted in and can opt out.
10 — The moneyStripe, payouts and refunds
Card payments run through Stripe, connected to your club's own account. This is the bit worth understanding properly, because it's different from most ticketing platforms:
- The money lands in your Stripe account, not ours. Tixello never holds your funds and takes no cut of the ticket price.
- Stripe pays out to your bank automatically on a rolling schedule once payments start. The Payouts page shows what's available, what's still clearing, and the recent transfers.
- Free and RSVP events don't need Stripe at all. You only need it connected to sell a paid ticket — and a paid event can't be published until it is.
- Bank details, payout schedule and card disputes live in Stripe, not in Tixello. There's a link straight through to the Stripe dashboard on both the Stripe and Payouts pages.
Refunds
Because the money is sitting in your Stripe account, a refund is issued from your Stripe dashboard — Tixello shows the order's status rather than being the place you press the button. In practice: find the payment in Stripe, refund it there, and the order reads back as refunded, with the refunded total reflected in the event's report.
Two things worth deciding before your first refund rather than during it: whether you refund at all for a change of mind, and by when. Put whatever you decide in the event description so it's answered before someone buys. If you're not sure how your venue's Stripe access is set up, or nobody's done a refund before, ring us and we'll walk you through the first one.
11 — DiscountsPromo codes
Promo codes in the left-hand menu makes discount codes for paid events. New code asks for:
New promo code
- Code
- What people type. Short, upper case, no ambiguity — MEMBER10, not member-10%off.
- Type and value
- A percentage off, or a fixed dollar amount off.
- Event scope
- All events, or one specific event. Scope it to the event unless you genuinely mean everything.
- Max uses
- How many times it can be redeemed in total. The safety net on anything you post publicly.
- Expires
- The date it stops working. Always set one — an early-bird code with no end date is an early-bird price forever.
The discount is fixed at the moment you create it, so codes are paused or reactivated rather than changed. If you get the amount wrong, pause that one and make a new code — don't try to edit it. Which is a good argument for checking the number before you press create, and for not printing a code on anything expensive until you've tested it.
12 — NumbersReports and exports
Each event has a Report tab: tickets sold, net revenue, orders, capacity left, and a breakdown of gross ticket value, booking fees, discounts, what was collected, what was refunded and the net. Below that, a per-ticket-type table — how many Adult, how many Concession, how many free — with Export CSV for a spreadsheet.
The Attendees page has its own Export CSV, which is the one you actually want the week of the event: every name and email, filtered by event, ready to print as a door list or hand to the kitchen as a headcount.
Worth building the habit of exporting the attendee list the afternoon of the event. It's your fallback if the internet drops out at the front door, and it's the version of the list nobody can accidentally change.
13 — AccessWho can log in
Under Settings ▸ Team you can invite colleagues. Each person signs in with their own email and their own password — please don't share one login around the duty managers.
| Role | Can do | Give it to |
|---|---|---|
| Owner | Everything, including team and billing | The GM and one other person. Not everybody. |
| Manager | Events, orders, branding — but can't change who has access | Functions and marketing staff who build and run events. |
| Viewer | Read-only | Anyone who needs the numbers but shouldn't be editing. |
When someone leaves, deactivate them rather than deleting: their history stays intact and their sign-in stops working. The last remaining owner can't be removed, which is deliberate — it stops a venue locking itself out. Add Tixello to your staff access checklist so it's handled on someone's last day rather than remembered six months later.
Tixello comes in tiers, and features like team roles, QR check-in and automated emails sit on the higher ones. If something described here isn't in your portal, that's usually why rather than anything being broken — ask us and we'll tell you what you're on and what changing would involve.
14 — QuestionsQuick answers
Someone says they never got their ticket. What do I do?
Find them under Attendees, check the email address is spelled right — it usually isn't — and press the paper-plane icon to resend. If the address was wrong, fix it with the pencil first, then resend. Ask them to check their junk folder while you're on the phone.
Can we take cash at the door as well as selling online?
Yes, and most venues do. Put the cash through your till as normal, then add the person under Attendees ▸ Add attendee so your headcount is right. Just remember Tixello isn't taking that money — it's only recording the ticket.
We need to cancel the event. What's the process?
Unpublish it first so nobody else buys a ticket, then email everyone through Email attendees, then refund the orders through Stripe. In that order — the worst version of this is refunding people while the page is still selling tickets.
Can we sell tickets for someone else's event?
You can, but the money lands in your account and the tickets carry your name, so you're the one members will ring. Fine for a club-run fundraiser; think carefully about an external promoter's night.
How far ahead should we put an event on sale?
Four to six weeks for a regular night, longer for anything with a big spend attached. Have a look at the venue year for lead times across the whole calendar — the mistake is nearly always announcing too late rather than too early.
Do people need an account to buy a ticket?
No. They open the link, pick their tickets, pay and get the ticket by email. The login is your side only.
Can we change the date after tickets have sold?
Yes — edit the event and save, and the public page updates. But tickets already emailed carry the old date, so email everyone through Email attendees the moment you change it, and consider resending tickets.
15 — Print thisThe pre-flight card
Stick it on the wall of the functions office. It's the list of things that are annoying to fix after an event goes on sale.
Tixello — before you press publish
Cyberry Know-How · cyberry.com.au/know-how
Check on the event
- Title spelled the way it's on the poster
- Date, start time and end time correct
- Venue name and full street address
- Cover image added and not badly cropped
- Description says what's included
- Capacity set — or deliberately left unlimited
- Absorb vs pass through matches your other events
Check on the tickets
- Every ticket type the night needs exists
- Prices checked twice — hard to change later
- Free ticket types for anyone comped
- Per-type caps where the numbers are limited
- Custom fields added before going on sale
Before it goes public
- Opened the link on a phone and read it
- Stripe connected (paid events only)
- Refund position decided and written on the page
- Promo code tested, capped and given an expiry
Once it's live
- Link on the website What's On
- Link in the Facebook event and post
- QR code on posters and screens — ask us for one
- Link in the members' newsletter
Week of the event
- Reminder email sent to attendees
- Attendee list exported and printed
- Check-in device charged and signed in
- Door staff know how to add a walk-up
Last reviewed 2 August 2026. Written against the Tixello portal as it stands at that date; screens and wording change as the product develops, so tell us if something here doesn't match what you're seeing. Features vary by plan. Raffles, trade promotions and public fundraising are regulated separately in NSW and QLD — taking the payment online doesn't change what permit you need, so check with whoever handles your compliance. This guide covers the software, not your club's ticketing, refund or privacy policies.
Got an event coming up?
Send it through and we'll have it on sale.
Event page, ticket types, the link on your website and a QR code for the posters — set up properly the first time, so your team only has to log in and watch it sell.