Summary
As an organizer, I want to embed a ticket widget on external websites, so that attendees can buy tickets without leaving my site
Blocked by: story-010-ticket-purchase-and-cart, story-012-byog-payment-processing
Acceptance Criteria
1. Widget Setup
- Embed Code: Organizer copies a provided embed code snippet to place on their external website.
- Responsive: Widget adapts to the host page's width and respects event branding.
2. Widget Behavior
- Inline Flow: For providers supporting inline payment (Stripe, Pix), the entire purchase flow stays within the widget.
- Redirect Flow: For redirect-based providers (PayPal, Mercado Pago), the attendee is redirected and returns to the host site after payment.
Test Plan
Tier 1 — Acceptance Tests
- AC1: Copy embed code snippet from event settings
- AC2: Widget is responsive and displays event branding
- AC3: Inline purchase flow completes within widget (Stripe, Pix)
- AC4: Redirect flow navigates away and returns to host page (PayPal, Mercado Pago)
Tier 2 — Edge Cases
- Widget on HTTP (non-HTTPS) page shows warning
- Widget with sold-out event shows sold-out message
- Widget with no payment provider configured handles gracefully
- Widget cross-origin security isolation
📄 Full spec: spec/elixir-phoenix-migration/10-product/stories/story-031-embeddable-ticket-widget.md
Summary
As an organizer, I want to embed a ticket widget on external websites, so that attendees can buy tickets without leaving my site
Blocked by: story-010-ticket-purchase-and-cart, story-012-byog-payment-processing
Acceptance Criteria
1. Widget Setup
2. Widget Behavior
Test Plan
Tier 1 — Acceptance Tests
Tier 2 — Edge Cases
📄 Full spec:
spec/elixir-phoenix-migration/10-product/stories/story-031-embeddable-ticket-widget.md