Transfers, cancellations and refunds
Somebody else takes a place, or nobody does. Either way the gate always knows, and a child is never left outside because an adult cancelled.
Two things happen to a place after registration: transfer (somebody else takes it) and cancel (nobody does). Registrants can do both from My registration until the event starts; organizers can do both at any time from the person's page. Money, where there is any, is a separate step you see before confirming.
Step by step
- 1
Transfer a place
Attendees → person → Transfer. The new person is created in the same registration and household, with the same type, group, days, guardian and companion links. Every live ticket is reissued to them (new codes; the old ones scan as void and name the replacement). The count of people does not change.
A place already used at a gate cannot be transferred.
You see what happens to every ticket before you confirm. - 2
Cancel a person
Attendees → person → Cancel. Their tickets are voided and the place is given back to capacity. If they were admitted on someone else's shared ticket, they come off it.
If other people are admitted on their ticket, EntryWick does not simply void it. The ticket moves to another household member of the right type registered for that day. If nobody fits, the cancellation is refused with the names — and cancelling the whole family together is offered instead.
Refused, or moved to another adult — never a child without a ticket. - 3
Let registrants do it themselves
The confirmation email links to My registration. There a registrant can fix a typo, change a day where the event allows it, say "Someone else is coming" (transfer) or "Can't come" (cancel) — for one person or the whole household — until the event starts, or until you close the page for changes.
Changes before the event happen without an email to you. - 4
Refunds on paid tickets
Paid tickets are charged through your Stripe account (connected under Settings → Payouts). A cancellation shows the refundable amount according to your event's refund rule — full, partial by date, or none — and you confirm. The refund is issued by Stripe; payments are a financial record and are kept even if the person later asks for their data to be erased.
Refund rules are set per event. Stripe does the money. - 5
Everything is on the audit log
Every transfer, cancellation and refund — who, when, from where (admin, self-service, API, import) — is a row in Settings → Audit log. Check-in rows are never touched by any of this; a cancelled person who was already scanned keeps that scan in history, marked.
Who did what, from where — including the registrant.
When you are done
What should be true now
- You have transferred a test place and seen the old ticket scan as replaced.
- You have tried to cancel a guardian with a companion and seen the refusal or the move.
- Your refund rule is set on the event (or the event is free).
- You know where the audit log is.