# Hidden-ticket access code: buyer-view test matrix

This worksheet is in English. Copy it for one event and one intended audience. Record **code labels only**, not live codes, recipient names or contact lists. Keep active codes in the authorized ticketing platform. A shared code can be forwarded; it does not verify a buyer's identity or reserve a ticket.

## 1. Define the intended result

| Event / occurrence | Code label (not the code) | Code owner | Distribution channel | Review / close owner |
|---|---|---|---|---|
| [ ] | [ ] | [ ] | [ ] | [ ] |

| Ticket type or reference | Intended public view | Intended view with valid code | Normal price | Sale window / time zone | Available allocation | Code-limit unit and value |
|---|---|---|---|---|---|---|
| [target A] | Hidden | Visible | [ ] | [ ] | [ ] | [ ] |
| [target B, if used] | Hidden | Visible | [ ] | [ ] | [ ] | [ ] |
| [public comparison] | Visible | Visible | [ ] | [ ] | [ ] | Not applicable |

Document whether the **event page** itself is public or private. This matrix tests ticket-type visibility on an event page; it does not configure event-level privacy. Use only the provider's documented access-code or promotion control for the intended ticket types. A code limit does not create stock.

## 2. Test the same buyer route recipients will use

Use a clean browser session. Test the public page, direct link and embedded checkout if the event uses them. In a live event, stop before placing an order unless an approved test transaction is available.

| Scenario | Expected ticket visibility | Expected price / availability | Actual result and message | Pass, issue or not testable | Owner / next action |
|---|---|---|---|---|---|
| No code | Targets hidden; public types as planned | Public types unchanged | [ ] | [ ] | [ ] |
| Valid code or provider code link | Only intended targets revealed | Normal approved price; target can enter basket only if on sale and in stock | [ ] | [ ] | [ ] |
| Wrong code | Targets remain hidden | No unintended price or basket change | [ ] | [ ] | [ ] |
| Expired / not-yet-active code, in safe preview or controlled setup | Targets remain hidden as the provider actually implements it | No unintended sale | [ ] | [ ] | [ ] |
| Direct link or embed, if used | Matches approved access plan | Matches approved price and stock | [ ] | [ ] | [ ] |
| Old code after replacement / closure | No longer reveals targets, if closure succeeded | No unintended purchase route | [ ] | [ ] | [ ] |

If an expired-code state cannot be simulated without affecting live buyers, mark **not testable** and name the later verification owner. Do not mark it as passed from an assumption. A ticket that appears but cannot be put in the basket may still be outside its sale window, inactive or out of stock; inspect those settings separately.

## 3. Release and close

- [ ] Hidden types, public comparison type and code mappings approved.
- [ ] Price, sale window, ticket allocation and code-use unit recorded separately.
- [ ] No-code, valid-code and wrong-code paths observed on each buyer route.
- [ ] Code/link distributed only through the approved channel; no live code pasted into this card.
- [ ] Buyer instructions say a visible ticket must still be purchased or registered.
- [ ] Code use and ticket availability reviewed by: [ ] at: [ ].
- [ ] Closure or replacement action follows the provider's documented path.
- [ ] No-code and old-code views rechecked after the change; a new code tested if one replaced the old code.
- [ ] Already issued tickets reviewed separately; no assumption that closing the code changes them.

Provider examples, not universal behavior: [Ticket Fairy](https://www.ticketfairy.com/guides/unlock-hidden-tickets-with-an-access-code) reveals attached hidden types through a no-discount promotion while ticket sale dates and stock still apply. [Ticket Tailor](https://help.tickettailor.com/en/articles/3537693-how-to-reveal-tickets-with-a-code) uses `Access code required` on the ticket type and can share a code link; its [discount-code guide](https://help.tickettailor.com/en/articles/950985-how-to-create-discount-codes) separates access from price reduction. [Eventbrite](https://www.eventbrite.com/help/en-us/articles/362532/how-to-set-up-discount-codes-for-one-or-multiple-events/) can use promotional codes to reveal hidden tickets and separately set a discount. [Accelevents](https://support.accelevents.com/en/articles/2476126-create-and-apply-access-codes-for-event-ticketing) maps codes to hidden ticket types and documents buyer-side testing. Verify the current controls and limit units for the platform actually used.