1. Reserve first, charge later
When supporters reserve during the launch window, Cammonly stores payment details securely but does not immediately capture the charge for still-confirming events.
The two values that matter are the reservation goal and the funding deadline. Until the goal is met, the reservation behaves like a commitment rather than a finished ticket sale.
2. Track outcomes from the organizer side
Use the event dashboard and /dashboard/tickets to monitor reservations, attendee state, and any follow-up actions such as authentication recovery or location-voting flows.
The exact attendee experience depends on whether the event is still confirming, already confirmed, or has optional location selection enabled. Do not treat every reservation as final admission until the event has crossed the goal.
3. Know the two final outcomes
If the event reaches the goal before the deadline, Cammonly captures payment and the supporter receives confirmed tickets with QR codes in the ticket wallet.
If the deadline passes without enough demand, the reservation expires automatically and the supporter is not charged. That is the central promise of the platform, so explain it clearly in your event copy and support replies.
Checklist
- - Reservation policy explained on the event page or in comms
- - Goal and deadline checked before sending final attendance instructions
- - Supporters know QR tickets appear only after confirmation