Selling event tickets and handling refunds

Starting an order

When a buyer starts checkout, Military OS records each ticket or add-on, its price, quantity, currency, and order total. The completed payment must match that order.

An unfinished checkout expires. A payment confirmation must refer to the same checkout before tickets are issued.

Confirming the payment

Military OS records each attempt to confirm a payment. If processing fails, it can be tried again.

The Stripe payment number is checked before tickets are created. If Stripe sends the same confirmation again, Military OS returns the existing order instead of creating a duplicate charge record or duplicate tickets.

Tickets

Each issued ticket remains connected to the order and ticket type. Event staff can check it in, transfer it to a member or guest, and see its current status.

Refunds

Each refund request has its own reference number. Repeating the same request returns the first refund record rather than refunding the order twice. Staff cannot refund more than the amount still available on the order.

Event and membership payments use separate records. An event payment can issue tickets but cannot create a membership. A membership payment requires a signed-in account and creates the membership term only after Stripe confirms payment.

Screenshots show the product version available when this post was published.

Discussion

Discussion loads here through GitHub-backed comments when JavaScript is available.