CASE STUDY

Ticket Transfer Flow (District App)

Simple, secure ticket sharing with clear ownership rules.

Overview

District allows users to seamlessly transfer event tickets to friends and family — whether plans change or attendees enter the venue separately. The challenge was to design a flow that feels instant and effortless, while still being secure, and transparent.

The solution needed to clearly communicate ticket ownership at every step, reduce user anxiety, and minimize support requests.

The Problem

Event tickets are high-value and time-sensitive. Users needed a way to:

  • Share tickets quickly and confidently
  • Understand when ownership changes
  • Avoid accidental or irreversible actions
  • Trust that transfers are secure

At the same time, the system had to prevent misuse and keep operational overhead low.

Goals

Design for last-minute, high-pressure scenarios

  • Enable fast, intuitive ticket transfers
  • Make ownership states unmistakably clear
  • Balance flexibility with strong control
  • Reduce confusion and customer support dependency

The Solution

The flow is built around simple, well-defined rules:


A. Reversible until accepted:

The sender can cancel the transfer anytime before the receiver accepts the ticket.


B. Irreversible after acceptance:

Once accepted, ownership fully transfers to the receiver. Only they can choose to return the ticket to the original sender.


These rules are clearly communicated through UI states and confirmation messaging.

Queued Ticketing for events

Transfer flow - Sender

Initiated directly from the ticket details screen. Recipient verified via mobile number. Explicit confirmation before finalizing the transfer. Real-time status updates for both sender and receiver. Tickets state change to "Transfer Pending" on the sender’s tickets details page.

Post-transfer receiver's flow

Tickets appear instantly in the receiver’s profile/tickets section. Clear success and completion messaging closes the loop.


No ambiguity. No follow-ups.

What if the receiver’s plans change?

The ticket transfer flow also supports reversibility after acceptance. If the receiver’s plans change, they can choose to return the ticket back to the original sender.


Flexible transfers, even after acceptance

Trust & safety by design

Strong confirmation steps prevent accidental transfers. Clear copy explains reversibility and ownership rules. Edge cases handled gracefully (unaccepted or expired transfers)


This ensures flexibility for users without compromising security.

Impact

Without disclosing internal metrics, here’s the story:

Faster, more confident ticket sharing

Reduced confusion around ticket ownership

Fewer support tickets related to transfers

Improved reliability for group entries and split arrivals