# Handle event cancellations and refund expectations

## Public help

If an event is cancelled or materially changed, attendees need clear information about what happens next.

1. Confirm the event status and reason for the change.
2. Pause ticket sales before announcing the cancellation if needed.
3. Prepare a clear message for attendees.
4. Review refund rules for the event and payment method.
5. Coordinate with LinkUp support or admin for refund processing. `[VERIFY: confirm organizer refund controls]`
6. Keep a record of decisions, messages, and refund requests.

## Expected LinkUp behavior

LinkUp should prevent further sales for cancelled events, preserve order history, and support a clear refund process for affected attendees.

## Implementation status

<table id="bkmrk-expected-behaviorsta"><tbody><tr><th>Expected behavior</th><th>Status</th><th>Surface</th><th>Manual check</th></tr><tr><td>Admin refund audit exists for Stripe.</td><td>Implemented</td><td>Admin / Backend</td><td>Confirm Stripe refund audit tables and admin visibility.</td></tr><tr><td>Organizer self-refund controls exist.</td><td>Planned</td><td>Organizer panel</td><td>Do not publish as live unless controls are confirmed.</td></tr><tr><td>Cancelled event stops future checkout.</td><td>Needs Verification</td><td>Public web / Checkout</td><td>Cancel a test event and attempt checkout.</td></tr><tr><td>Attendee communication workflow exists.</td><td>Needs Verification</td><td>Notifications / Admin</td><td>Check notification templates and event messaging options.</td></tr></tbody></table>

## Verification checklist

- Cancel a test event.
- Confirm public checkout is blocked.
- Inspect affected orders.
- Attempt a test refund path in test mode only.
- Confirm attendee notification options.

## Gaps / notes

- Payments/refunds are a dedicated future deep-dive area.
- Organizer responsibilities need policy approval before public publishing.