PRODUCT REQUIREMENTS DOCUMENT

GPay Groups

Smart Settlement Mode

1. Why This, Why Now, Why Us

The strategic case in three sentences

India processes 13B+ UPI transactions/month, yet settlement for group expenses still leaks to Splitwise — an app with no UPI integration and 10M+ users globally. GPay already sits at the point of payment; every group dinner, Goa trip, and shared Zomato order is a trust moment we’re not capturing. Smart Settlement Mode closes that loop without adding transaction complexity — it makes GPay the operating system for shared financial life.

Why this feature?

• Splitwise has 10M+ global users despite having no native UPI settlement - proof that the gap exists and isn’t captured by GPay today.
• Post-COVID group travel in India has surged; IRCTC group bookings and multi-person Zomato orders are behavioral proxies for the target use case.
• Deferred settlement is not laziness - it’s rational. Users don’t want to break flow during a trip; they want one clean moment of closure at the end.

Why now?

• Group-based UPI usage is growing faster than individual P2P - behavioral data from GPay’s own logs shows multi-person request chains increasing YoY.
• Splitwise’s recent stagnation on India-specific UX creates a window before a well-funded India-native competitor moves in.
• RBI’s updated UPI circular (2025) explicitly permits multi-party deferred payment instructions, removing the key regulatory blocker.

Why Google Pay?

• GPay has UPI rails, a 150M+ MAU base in India, and direct integration with contacts - the three things a group settlement product must have.
• Network effects are local: when one person in a group uses GPay Groups, the friction to onboard others is near zero because most Indians already have GPay installed.
• Google’s ML capabilities enable a smarter settlement graph algorithm than any standalone app could afford to build.