top of page

Learnings

  • Launching both flows simultaneously expanded the scope and delayed the first release.

  • If repeated, I’d prioritize the simple flow first (split evenly).

  • I learned to balance delivery speed vs case coverage.

  • Close coordination with Tech and QA ensured quality without impacting other flows.

Preview Split Payment.jpg

Split Payments on Pay Terminal

We streamlined the group payment experience by enabling split payments directly from the Pay terminal, improving usability and boosting adoption.
Redesigning the group payment experience with split-by-items and split-evenly flows

Through interviews with waiters, managers, and admins, we discovered a critical pain point: there was no way to split bills on the POS or Pay terminal.

Manual division led to errors, wasted time, and frustration.

Involved teams: Product, Technology, Sales, Onboarding, Support, Marketing. 

Goals

  • Business:
    Increase Pay terminal penetration by adding valuable functionality

  • User:
    Speed up the checkout process and offer an intuitive group payment flow.

Solution

Split Evenly:
  • “Split” button shown on the payment screen.

  • "Split evenly" button shown on the split screen.

  • Screen for select number of people (2–6) or input to custom value (max 24).

  • New “Next Payment” button to proceed.

  • Tip screen per person.

Split evenly.png
Split by Item:
  • “Split” button shown on the payment screen.

  • "Split by item" button shown on the split screen.

  • Select specific items screen.

  • Supports partial item payments.

  • Confirmation modal with selected items.

Restrictions:

  • Disabled if other payment methods are present.

  • Adjusts totals if values don’t match.

  • Blocks button if there are payments registered in the POS.

Split by item.png

Research

Split - Research.jpg
  • Split by item: 100% task success, CMS Score 4.47

  • Split evenly: 60% task success, CMS Score 4.45

In-person and remote interviews.

 

We ran usability tests with real restaurant staff and used UMUX Lite for validation.

  • Removed unnecessary screens

  • Simplified item selection

  • Improved interaction times

Key UI changes based on feedback:

Results

Launch date: January 23, 2024

Split evenly

Weekly usage: 58 times

Launched 1 month before “Split by item” to accelerate delivery.

Measured one month after launch.

Launch date: February 27, 2024

Split by item

Weekly usage: 150 times

Released later due to higher technical complexity.

Measured one mont after launch.

Business impact

Mar 2024

26.16%

Feb 2025

27.51%

Jan 2024

21.33%

Role

UX flow design, edge case handling, user validation, and business metrics.

Tools

Figma, interviews, CMS Score, QA, Metabase.

Outcome

More usability, more Pay usage, less operational friction.

bottom of page