0 %

Ticket transfer

District by Zomato - Simple, secure ticket sharing with clear ownership rules.

For

District by Zomato

My role

Senior Product Designer

Teams

PM, Engineering, Risk Ops, CX and Data

Platform

iOS, Android

UI/UX design App design

Challenge


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.

Problem Statement

Share tickets quickly and confidently

Problem Statement

Understand when ownership changes

Problem Statement

Avoid accidental or irreversible actions

Problem Statement

Trust that transfers are secure

The Solution

The solution needed to clearly communicate ticket ownership at every step, reduce user anxiety, and minimize support requests. The flow is built around two 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.

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.

The receiver is notified via an in-app notification, a custom message from the sender, and a deep-linked aerobar that takes them directly to the ticket acceptance page.

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

Impact


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. 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



Icon Let's talk about your project!

Image Image