Swiggy
Medium
Should Swiggy build UPI? If yes, why do you think so?
This is a build vs partner question. Not a "UPI is popular, so yes" question. Swiggy should build UPI only if owning the payment step changes something it cares about: conversion, speed or control.
Step 1. Clarifying Questions
- Build what? A full UPI app like PhonePe, or an in-app UPI handle so users pay without leaving Swiggy? Assume in-app UPI through a bank partner.
- Goal? Higher payment success, lower cost, or a new financial services business? Assume payment success and checkout speed.
Swiggy and Zomato have both experimented with in-app UPI before. If you cite this in the interview, check the latest status first.
Step 2. The problem today
Most Swiggy orders are paid by UPI. The usual flow: tap pay, jump to PhonePe or Google Pay, enter PIN, come back. Every app switch is a chance to fail: the app doesn't return, a timeout, a bank server down. At Swiggy's scale, even 1% failed payments (illustrative) means lakhs of lost orders a month.
Step 3. Options
1. Partner (today): hand off to PhonePe or Google Pay. No build, no control.
2. In-app UPI with a bank partner: the user links a bank account once and pays inside Swiggy with a PIN. Moderate effort.
3. A full UPI app for payments to anyone. Heavy compliance and fraud work, and no direct income.
Step 4. For and against
For:
- Payment success: no app switch, fewer failures and drop-offs.
- Speed: a 10-minute Instamart promise starts with a 10-second checkout.
- Control: today an outage at a payments app is an outage for Swiggy.
- Future: owning the payment relationship opens Swiggy One offers, credit and BNPL later.
Against:
- No direct revenue. UPI merchant payments carry zero MDR.
- Trust: users trust PhonePe and Google Pay with their bank account more than a food app.
- Fraud, disputes and regulatory work now sit with Swiggy and its bank.
- Focus: payments is not Swiggy's core.
Step 5. Recommendation
Yes to option 2, no to option 3. Build in-app UPI with a bank partner, and offer it as a choice, never forced.
- Target repeat users who faced a failed payment in the last 30 days first.
- Reward linking with Swiggy One benefits or cashback.
- Keep PhonePe and Google Pay as a fallback.
Step 6. Metrics
- North Star: payment success rate at checkout
- Checkout time from pay tap to order confirmed
- Adoption: bank linking rate, % orders paid by in-app UPI
- Guardrails: fraud rate, disputes per 1,000 payments, payment support tickets
Interview tip: never argue for building payments on revenue. In India, UPI earns almost nothing per transaction. Argue on payment success and control.
Community Answers (0)
No answers yet. Be the first to share your approach!