Support us on Product Hunt
We're on Product Hunt! Show your love, give us a boost, and help more designers discover better ways to grow.
Upvote on Product Hunt
Shared Ride Payment Splitting on Uber
Design a simple flow for passengers to split fares fairly during shared rides.
Background

Uber’s shared rides (e.g., UberPool, UberX Share) allow multiple riders heading in the same direction to travel together at a reduced cost. However, when friends or coworkers share a private Uber, splitting the payment often happens outside the app — through cash or third-party transfers. This creates friction, confusion, and sometimes conflict about who owes what.

Context

A native payment-splitting feature would make cost-sharing seamless. Whether two friends are going to a concert or four colleagues are heading home, Uber could handle the split automatically, improving both convenience and trust.

Business Objective
  • Improve customer satisfaction by removing awkward post-ride payment steps.

  • Increase adoption of group/private rides by making them more transparent and fair.

  • Strengthen Uber’s reputation as a frictionless mobility solution.

Target User
  • Friends casually sharing an Uber after social events.

  • Students or coworkers splitting costs on a regular commute.

  • Riders who avoid group rides due to “payment awkwardness.”

Core Problem

How can Uber make it fast and intuitive to split fares among multiple passengers, without slowing down the ride-booking process or complicating payments?

Challenge

Design the UI flow and experience that allows riders to:

  1. Select “Split Fare” when booking or during a ride.

  2. Invite co-riders via phone number, Uber handle, or shareable link.

  3. Show pending/accepted split requests in-app.

  4. Handle cases when someone doesn’t accept or fails to pay.

  5. See a clear final receipt with each rider’s share.

Constraints
  • Must work for both pre-arranged rides (friends together) and dynamic shared rides (UberPool-style).

  • Keep the split flow lightweight — it shouldn’t delay booking.

  • Handle edge cases (e.g., if one rider’s card fails, the main booker should not be overcharged unexpectedly).

  • Should work across different payment methods (cards, wallets, etc.).


Grab the PDF version
Save a copy to review offline, print it out for focus time, or share it with friends — this PDF is made for flexible learning.
Join our official community
Get feedback, connect with designers, and grow together — all in a free, friendly space built for your UX journey.
Join the community
Partner with uixperiment
Looking to create a challenge for hiring or learning? Let's team up — we work with companies and campuses to shape meaningful UX experiences.
Start a collaboration