Refund a whole event

Steps

1. 1 Member Open the event as member 0:04 ▣
2. 2 Member Buy one GA ticket 0:05

   Reserving takes the seat out of inventory and starts a 5-minute hold; the countdown on the next page is that hold.

3. 3 Member The hold timer is running on the checkout page 0:06 ▣

   If the hold expires the seat goes straight back into inventory — the scheduler sweeps it, nobody has to click anything.

4. 4 Member Pay for the order 0:07 ▣

   Charged through the mock payments adapter with token tok_success.

5. 5 Member Land back on My Club, purchase confirmed 0:09 ▣

   The hub is where a member already lives — tickets, credit, listings and comps — so the purchase confirms in context rather than on a receipt page they have to navigate away from.

6. 6 Member Open the site menu 0:10

   The collapsed bar is one row at every role; the full role-gated navigation lives in this panel and closes as soon as you leave.

7. 7 Member The ticket is in the wallet 0:11 ▣
8. 8 Administrator The venue cancels — open the event's refund policy 0:22 ▣

   Policy on the left is the everyday setting; the danger zone on the right is the one action that cannot be walked back.

9. 9 Administrator The page prices the button before anyone touches it 0:23 ▣

   The exposure is the same order set the bulk refund itself walks, so the number on screen is the number that moves.

10. 10 Administrator Refund the entire event 0:24 ▣

    Two dialogs, not one. The first names the money and the event; the second says the ledger postings are final.

11. 11 Administrator The page says what happened 0:25 ▣

    Confirm before, acknowledge after — a silent reload is indistinguishable from a dead button.

12. 12 Administrator The books took a reversal, not an edit 0:26 ▣

    A wrong posting is fixed by a mirror, never an UPDATE — which is why the second dialog can honestly say the postings are final.