Sell event tickets with your own Stripe account
fullhall sells tickets from the same public page people already use to RSVP. The money settles in your organisation's own Stripe account, not ours, and fullhall adds no fee on tickets. The only cost is Stripe's card fee, and the shoebox of cash at the door gets to retire.
The money never passes through us
Your organisation connects its own Stripe account, and every ticket payment is a direct charge to it. fullhall never holds ticket funds, so there's no platform balance to wait on and no second business between your buyer and your bank account. Card numbers go from the buyer's browser to Stripe's checkout page and never touch our servers.
The cost is Stripe's card fees, about 1.7% plus 30 cents for Australian cards, and nothing else. A $20 ticket puts roughly $19.36 in your account. That posture is deliberate: the software has a price, the tickets don't.
How it runs
- 1
Bring your own Stripe
Your organisation keeps its own Stripe account; fullhall never holds the money. Create a restricted key in your Stripe dashboard and paste it in; the Payments page lists the exact permissions to tick. No Stripe account yet? Setting one up takes about ten minutes and Stripe verifies you, not us.
- 2
Add ticket types to an event
General, concession, early bird. Each type has its own price and allocation. A discount code takes a set amount or percentage off the order, and a reveal code shows a hidden type (committee pricing, say) to the people you give it to.
- 3
Share the page
The same public event page people already know. They pick tickets, pay on Stripe's checkout, and get a QR ticket by email with a calendar invite attached.
- 4
Run the door on a phone
Open the scanner in the browser and point the camera at the ticket. Scanned tickets tick off the door list live, walk-ins can be added by name, and a ticket scanned twice says so instead of letting two people through. On a browser without camera scanning, the door list's name search does the same job.
Refunds without a support ticket
Refund a whole order or part of one from the event's orders page; the money goes back the way it came and the seats reopen. You publish a refund policy once, and it appears on every ticketed event page and order email, so nobody has to ask where you stand. Capacity stays honest throughout: a refunded ticket frees its seat, and a sold-out event with a waitlist promotes the next person waiting.
You can see whether it worked
Every event has a report: page views and where they came from, tickets sold by type, revenue net of refunds, and who actually turned up. The attendee list and the order list export as CSV for the committee meeting.