Transfer a Resold Event Ticket Safely
Design a verified ticket-transfer journey that protects buyer and seller when ownership moves after a resale purchase.
The brief
Understand the problem
Background
A resale payment does not guarantee that a valid ticket has transferred. Buyers need confidence about seat, fees, delivery timing, and venue restrictions, while sellers need a clear release from responsibility only after acceptance.
User context
Noah buys a concert ticket two days before the event. The seller holds the ticket in an external venue account, and the venue requires the attendee's name to match an identity check at entry.
Product problem
The marketplace needs to coordinate payment protection, external transfer, buyer acceptance, and dispute evidence without exposing a reusable ticket code.
Objective
Create a post-purchase transfer flow for one verified resale ticket, including timeout and failed-transfer recovery.
What to design
Define the experience
Required experience
- Review purchase terms, seat details, fees, and transfer conditions
- Track the seller's external transfer without revealing the entry credential
- Accept ownership and verify attendee details
- Resolve a missed deadline or mismatched ticket
Screens and states
- Protected purchase summary
- Transfer tracker
- Ticket acceptance
- Transfer issue resolution
Core user flow
Follow the critical path
- 01
Noah reviews the seat, total price, name requirement, and delivery deadline
- 02
The seller initiates transfer through the venue account and submits a reference
- 03
Noah receives the venue invitation and verifies that section and seat match
- 04
He accepts ownership and updates the permitted attendee name
- 05
Payment releases only after verified acceptance is recorded
Product rules
Requirements and constraints
Requirements
- Show face value, resale price, fees, restrictions, and refund conditions before commitment
- Keep payment protected until the required ownership event is verified
- Use status evidence from the venue system where available
- Prevent screenshots or copied barcodes from serving as proof of transfer
- Provide a timed issue route with evidence for buyers and sellers
Constraints
- Venue transfer capabilities and identity rules differ by event
- The marketplace cannot change a venue's entry policy
- The live barcode must remain hidden until the venue allows display
Reality check
States worth considering
Finish line
What to deliver
- Four mobile-first screens covering protected transfer, acceptance, and one disputed mismatch
If you want more
Optional extensions
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.