Rework or remove the "pending" ticket state #135

Open
opened 2026-06-24 15:27:03 +00:00 by padreug · 0 comments
Owner

From the 2026-06-24 design review. The current "pending" ticket state is confusing and not currently useful — today a ticket is effectively either bought or not.

Two directions (decide)

  • (a) Remove it entirely — simplest; a ticket is paid or it doesn't exist.
  • (b) Repurpose it for an organizer-approval flow — most useful for free tickets: the host approves requests, so a ticket sits "pending" until approved/declined. Also overlaps with cash-on-arrival (reserved-but-unpaid).

Note vs ui-tweaks-4

ui-tweaks-4 removes the "Pending" tab from the My Tickets UI as a surface simplification. This issue is the deeper state/model decision behind it — keep them distinct.

Scope / planning

More complex than surface-level: touches the ticket lifecycle in the LNbits events extension + webapp (My Tickets, purchase flow, door scanner). Needs planning. Related: cash-on-arrival, free-ticket approval, notifications ("are you still coming?").

Draft from 2026-06-24 design review.

From the 2026-06-24 design review. The current **"pending"** ticket state is confusing and not currently useful — today a ticket is effectively either bought or not. ## Two directions (decide) - **(a) Remove it entirely** — simplest; a ticket is paid or it doesn't exist. - **(b) Repurpose it for an organizer-approval flow** — most useful for **free tickets**: the host approves requests, so a ticket sits "pending" until approved/declined. Also overlaps with cash-on-arrival (reserved-but-unpaid). ## Note vs ui-tweaks-4 ui-tweaks-4 removes the **"Pending" tab** from the My Tickets UI as a surface simplification. This issue is the deeper **state/model** decision behind it — keep them distinct. ## Scope / planning More complex than surface-level: touches the ticket lifecycle in the LNbits events extension + webapp (My Tickets, purchase flow, door scanner). Needs planning. Related: cash-on-arrival, free-ticket approval, notifications ("are you still coming?"). _Draft from 2026-06-24 design review._
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
aiolabs/webapp#135
No description provided.