Ticketing
Set up ticket sales or RSVPs from Setup → Ticketing.
Ticketing providers
Choose how attendees register for your event. You can only have one active provider at a time.
| Provider | Best for |
|---|---|
| Stripe | Paid tickets — card, Apple Pay, Google Pay |
| Free RSVP | Free events with optional capacity limit |
| Zeffy | Sync registrations from an existing Zeffy campaign |
| Manual | Redirect to Zelle, bank transfer, or any external flow |
| External embed | Embed a third-party registration iframe on your event site |
| External link | Redirect attendees to any external URL to register |
Stripe (paid tickets)
Connect your Stripe account first — click Connect Stripe and complete the onboarding. You only need to do this once.
Once connected, you can:
- Create multiple ticket types (General Admission, VIP, Early Bird, etc.)
- Set a price, capacity, and sale window for each type
- Enable discount codes
- Set a fee structure (absorb fees or pass them to attendees)
Attendees pay by card, Apple Pay, or Google Pay. Funds go directly to your connected Stripe account.
Free RSVP
Select Free RSVP as your provider. You can optionally set a capacity limit and a custom confirmation message that attendees see after signing up.
RSVP submissions are listed in Registrations → RSVPs and can be exported as CSV.
Zeffy
If you already sell tickets through Zeffy, you can sync those registrations into Confexo for check-in, ticket emails, and wallet passes.
- Enter your Zeffy API key in the ticketing setup.
- Select the Zeffy campaign to import registrations from.
- Map each Zeffy rate to a ticket type in Confexo.
- Click Sync now in Registrations to pull the latest data. Re-sync any time.
Wallet passes
Every ticket issued through Confexo (Stripe, RSVP, or Zeffy) includes links to add the ticket to Apple Wallet or Google Wallet.
- Passes show the event name, date, venue, and a QR code for check-in.
- If your venue has coordinates set, passes can send a lock-screen notification when the attendee is near the venue.
- Passes are automatically marked as expired after the event ends.