Cancel and refund

One action on a registration for "they are not coming — give them their money back".

Who uses it: an organizer who may both cancel people and refund payments, on the registration's page.

What they came to do: do both halves in one place, so neither gets forgotten.

What must be true when they leave: they read exactly what would happen to the money and to every ticket before confirming, and either both halves happened or neither did.

Decided

• Refunding and cancelling stay separate everywhere else. A refund from the Payments tab never cancels anybody or voids a ticket — a partial refund is often a price correction, and the person still expects to get in. Cancelling a person never refunds. This action is the only thing that does both.
• The organizer picks the people (everyone by default) and the amount (everything refundable by default) independently, so a full cancellation with a partial refund is one decision.
• The confirmation says how much is refunded and from which payment (back to the card, or marked refunded for money recorded by hand, which the organizer gives back themselves), how much stays paid, what happens to each person's tickets (voided, handed to another companion, released from a shared ticket), whether the registration ends up cancelled, and who in the household stays registered.
• One transaction. If a card refund is refused, nothing is cancelled and the reason is shown.
• Two audit rows on the registration, one per half, sharing a decision id, on top of the usual rows for people, tickets and payments.
• The people half follows the same rules as cancelling from a person's page: a ticket other people are admitted on goes to another companion or the whole thing is refused.

Open

• Keeping our platform fee on a refund is the tenant setting (payments.refund_reverses_fee); this action does not offer the per-refund toggle the Payments tab has.