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 their own smartphone. 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, the kiosk needs an internet connection to process card payments and sync ticket data. A standard WiFi connection or 4G mobile hotspot works fine. If connectivity drops briefly, the scanner can still validate recently synced tickets.

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.

Ride Tickets charges a flat $0.20 per ticket sold as our service fee, plus a $25/month platform fee. Stripe also charges their own processing fee (1.7% + $0.10 per in-person transaction) which is separate and deducted by Stripe directly. There are no setup fees, no lock-in contracts, and no hidden costs. See our pricing page for full details and a calculator.

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

No. There are no setup fees, onboarding fees, or activation fees. You only pay the $0.20 per ticket service fee and the $25/month platform fee. Stripe's processing fees (1.7% + $0.10) are charged separately by Stripe.

Refunds are handled through the organiser portal. When you issue a refund, Stripe reverses the charge to the customer's card. The platform fee on that transaction is also refunded. Stripe's own processing fee may or may not be refunded depending on timing — check Stripe's refund policy for details.

The kiosk accepts all major credit and debit cards via tap-to-pay (contactless), chip insert, and swipe through the Stripe Terminal card reader. Apple Pay and Google Pay are also supported via contactless. Cash is not supported — the system is fully cashless.

Any modern Android tablet running Android 10 or later with an 8"+ screen. Popular choices include the Samsung Galaxy Tab A series and Lenovo Tab M series. The kiosk app runs as a full-screen WebView in locked-down mode, so the tablet doesn't need to be high-end.

A thermal receipt printer is optional but recommended. It prints each coupon with a QR code that ride operators scan. Without a printer, customers can still display the QR code on-screen, but printed tickets are more practical at busy events. We support standard 58mm and 80mm ESC/POS thermal printers (USB or Bluetooth).

Yes. You can deploy as many kiosks as you need, all managed from your single organiser portal. Each kiosk pairs in seconds via a QR code and automatically inherits your rides, pricing, and branding. All kiosk sales appear in the same dashboard.

Card payments require an active internet connection — if WiFi drops, the kiosk can't process new sales until connectivity returns. For events in remote locations, we recommend a 4G mobile hotspot as a backup. The ticket scanner can validate recently synced tickets offline briefly.

Yes. You can configure the kiosk's welcome message, business name, colours, and branding through your organiser portal. The kiosk displays your rides with the emoji icons and ordering you set up.

When a customer buys coupons, each coupon is assigned a unique QR code. This is printed on the receipt (if a printer is connected) or displayed on screen. At the ride, an operator scans the QR code with the scanner app on their phone. The system checks if the ticket is valid and marks it as redeemed — each coupon can only be used once.

Ticket expiry settings can be configured in your organiser portal. By default, tickets are valid until redeemed. You can set tickets to expire at the end of a day or event if needed.

It takes about 2 minutes. Generate a 6-digit scanner code from your portal, give it to your ride operator, and they open the scanner page on their phone's browser. Enter the code, point the camera at QR codes — green means valid, orange means already used. That's it.

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

Email us at hello@ridetickets.com.au or use the contact form. We aim to respond within one business day. The organiser portal also has a built-in knowledge base with guides and troubleshooting articles.

Yes. There are no lock-in contracts. You can cancel at any time and your account stays active until the end of your current billing period. Any outstanding payouts will still be settled to your bank.

Yes. We take security seriously. Passwords are hashed with bcrypt, sensitive configuration is encrypted with AES-256-GCM, all API access requires JWT authentication, and we enforce rate limiting to prevent abuse. Card payments are processed by Stripe, which is PCI DSS Level 1 certified — the highest level of security certification.

Yes. Your organiser portal shows a full transaction history with filters for date range and transaction type. Each entry shows the amount paid, platform fee deducted, net amount, and payment method. You also get a monthly invoice with a complete breakdown.