Frequently asked questions

Get in touch via our contact page or click "Get Started" and we'll set up your organiser account. You'll receive login credentials and can start configuring your rides and kiosks immediately.

For each kiosk, you'll need an Android tablet (8" or larger), a Stripe-compatible card reader, and optionally a thermal receipt printer (58mm or 80mm). For scanning, ride operators just need a smartphone or a handheld laser scanner. You'll also need WiFi or a mobile hotspot.

Most operators are up and running in under 30 minutes. Creating your account takes 5 minutes, connecting Stripe takes another 5, adding your rides and pricing takes 10–15 minutes, and pairing a kiosk takes under a minute.

Yes. Stripe requires an Australian Business Number (ABN) to verify your business for card payments and bank payouts. This is a standard requirement for accepting card payments in Australia.

Yes. Customers can buy coupon packs ahead of time on our Buy Coupons page — pick the show, pay by card, and get wallet codes to use at the rides. They can also buy at the self-service kiosk on the day.

Each coupon is assigned a unique QR code, printed on the receipt or shown on screen. At the ride, an operator scans the code — the system checks it's valid and marks it redeemed. Each coupon can only be used once.

All major credit and debit cards via tap-to-pay, chip, and contactless through the Stripe Terminal card reader. Apple Pay and Google Pay work too. The system is fully cashless — no cash needed on site.

Pricing is for ride operators running self-service kiosks. We charge a flat $0.15 per coupon sold at the kiosk, plus a $25/month platform fee. Stripe charges its own processing fee (1.7% + $0.10 per in-person transaction), deducted separately. No setup fees, no lock-in. See the pricing page for a calculator.

No. There are no setup, onboarding, or activation fees. You only pay the $0.15 per kiosk coupon service fee and the $25/month platform fee. Stripe's processing fees are charged separately by Stripe.

Refunds are handled through the organiser portal. When you issue a refund, Stripe reverses the charge and the platform fee on that transaction is also refunded. Stripe's own processing fee may or may not be refunded depending on timing.

Any modern Android tablet running Android 10+ with an 8"+ screen — e.g. Samsung Galaxy Tab A or Lenovo Tab M series. The kiosk app runs full-screen in locked-down mode, so the tablet doesn't need to be high-end.

Optional but recommended. It prints each coupon with a QR code to scan. Without one, customers can show the QR on-screen. We support standard 58mm and 80mm ESC/POS thermal printers (USB or Bluetooth).

Yes. Deploy as many kiosks as you need, all managed from one organiser portal. Each pairs in seconds via QR code and inherits your rides, pricing, and branding. All sales appear in the same dashboard.

Card payments need an active connection — if WiFi drops, the kiosk pauses new sales until it returns. We recommend a 4G hotspot as backup. The scanner can validate recently synced tickets offline briefly.

About 2 minutes. Generate a 6-digit scanner code from your portal, give it to the operator, and they open the scanner on a phone or handheld laser scanner. Enter the code and scan — green means valid, red means rejected.

Yes. Generate multiple scanner codes — one per operator if you like. They all work simultaneously and the system handles concurrency, so two operators can't double-scan the same ticket.

Expiry is configurable in your organiser portal. By default tickets are valid until redeemed; you can set them to expire at the end of a day or event if needed.

Stripe processes payouts daily. After a customer pays, funds typically arrive in your bank account within 1–2 business days. View your payout schedule in the Stripe dashboard, linked from your portal.

Email hello@ridetickets.com.au or use the contact form. We aim to respond within one business day. The portal also has a built-in knowledge base.

Yes — no lock-in contracts. Cancel any time and your account stays active until the end of the current billing period. Any outstanding payouts are still settled to your bank.

Yes. Passwords are hashed with bcrypt, sensitive config is encrypted with AES-256-GCM, API access requires JWT auth, and we enforce rate limiting. Card payments are processed by Stripe (PCI DSS Level 1).