How to enable ticket transfers to another person and test the handoff

1. Define the transfer scope

Download the ticket-transfer handoff test card (Markdown, English)

Record the event, eligible and excluded ticket types, and any approved transfer window. Decide who may initiate a change and who handles exceptions. Check whether add-ons, assigned seats, or registration answers follow the ticket. On Events.com, the organizer selects eligible categories and may set a date range; purchased add-ons do not transfer there.[1]

2. Enable the supported route

Apply the approved scope in your event’s ticket settings. InEvent has a transfer setting and a per-type control to prevent giveaway; it also lists registration features incompatible with transfer. Events.com uses a post-registration transfer setting and category selection. Save, then reopen the settings to confirm what persisted.[3][1]

Check what “transfer” means on your platform. Eventbrite says it cannot move a ticket between accounts. When permitted, the original purchaser can edit order or attendee information; the new attendee may claim by email. That differs from accepting an account-level transfer. Do not advertise an unavailable self-service route.[4][5]

3. Run a controlled handoff test

With authorized sample records, try an eligible ticket and an excluded type. For the eligible one, observe the sender’s request, recipient’s action, and status before and after acceptance. Events.com shows a pending transfer until acceptance; InEvent offers pending and completed views. Record your provider’s actual states: a sent invitation is not a completed handoff.[2][3]

Have the recipient open the resulting ticket through the official route. Compare reference, event/date, type, assigned seat if any, and admission status with the organizer record. Check the original credential and linked extras in this provider. If the request is declined or pending, verify who currently holds the admission right before briefing gate staff.

4. Publish instructions and own exceptions

Tell holders where to start, which types qualify, the deadline, and how to get help. Tie payment or refund wording to separately approved event terms. Give check-in and support teams the current-record lookup path and an owner for pending or mismatched transfers. Recheck the scope and one controlled handoff after relevant settings changes.