Registrations that take the payment and send the confirmation
Event tooling usually gives you a ticket page and leaves the rest — the pricing rules, the dietary requirements, the confirmation emails, the door list — to a spreadsheet. Faldaro runs the whole registration as one submission.
-
One form, every ticket type
Member or guest, one day or three, dinner or not — conditional fields ask each attendee only what applies to them, and the questions you need for badges and catering come back filled in rather than chased later.
-
The price is the form’s, not the page’s
A logic rule prices the registration from the answers and Stripe collects it. Change the early-bird cut-off in the browser and the next registration is priced the new way; card details never touch Faldaro.
-
Confirmations that send themselves
Submission sends the acknowledgement and the joining instructions go out on the transition that confirms a place — each one a template you write once and a rule you configure once. The card receipt is Stripe’s to send, from the account the money landed in.
-
A door list that is current
Registrations move through the states you named — Registered, Paid, Confirmed, Checked in — so on the day the list reflects who actually turned up, and every change to it is recorded.
Built from the same parts as everything else: the builder for the questions, payments for the money and workflows for everything the confirmation should trigger.
Questions
Registration on Faldaro, plainly
Who works out what a registration costs?
Your form’s rules, on the server. Early-bird dates, member rates, workshop add-ons and group discounts are formulas over the submitted answers — and a browser cannot send a price of its own, because the request has no field one could ride in.
What happens if someone closes the tab mid-payment?
Nothing is lost. The payment is written down before any request leaves for Stripe, and completion is recorded from Stripe’s signed webhook rather than from a success page — so a closed tab cannot lose a registration, and a retried webhook cannot double one.
How do we get the attendee list?
Build a report over the registration form — counts by ticket type, dietary requirements, workshop numbers — and export it as CSV on plans that include export. Text cells that start with an equals sign are neutralised, so nobody’s answer executes in your spreadsheet.
Open registration for your next event
Build and share the form on the Free plan; add Stripe payments from Starter when you are ready to charge for a place.
No card required.