# Ticket checkout timer: completion and expiry card

Use this English card for one event and one supported checkout path. Record a **test reference**, not a real buyer's name, email, payment details or ticket code. Do not create a live charge unless the test is approved.

| Setup | Record |
| --- | --- |
| Event / ticket type / test environment | |
| Provider timer setting and approved duration | |
| Sales end date (separate control) | |
| Checkout questions and payment path in scope | |
| Reviewer / exception owner | |

| Controlled attempt | Start / deadline | Expected | Observed buyer screen | Order state | Available stock before / after | Issue owner |
| --- | --- | --- | --- | --- | --- | --- |
| Finish before expiry | | Completed only after the provider confirms the order | | | | |
| Let checkout expire | | No completed order from this attempt; inspect actual provider state | | | | |
| Pause or interrupt midway | | Record whether the timer continues, resets or offers recovery | | | | |

- [ ] A buyer can see and understand the remaining time or expiry message, **if the platform displays one**.
- [ ] The path leaves adequate time for the actual form and payment steps, including an assisted or accessible completion route where needed. Record the route; do not assume a universal extension feature.
- [ ] An expired attempt was checked in the authoritative order and inventory records before stock was promised or manually reassigned.
- [ ] An unexpected result has an owner and was rechecked after correction.
- [ ] The card will be rerun after a timer, form or payment-path change.

Provider references: [Eventbrite's registration time limit](https://support.eventbrite.com/hc/en-us/articles/34862118224658-Change-the-registration-time-limit) and [Planning Pod's checkout time limit](https://planningpod.com/help-center/setting-up-checkout-time-limit-for-registrations). Their hold and expiry behavior is provider-specific.