Every Indian friend group has a Splitwise tab and a UPI chain. Both end in the same place: arguments and unsettled balances three months later. The travel card sees every transaction. It's the obvious place to make group spending feel effortless. This memo proposes Scapia Splits.
I built this without internal Scapia data and without access to a specific industry report on Indian group travel spending. The framings below are directional truths I can defend from first principles or universal user experience (most leisure travel is social, Splitwise is widely used, primary cardholders front group expenses, unsettled balances are common). Where I cite a number, I label it as an estimate. As an intern, my first job is replacing every assumption with your real numbers from Scapia's own transaction logs and cohort analysis.
Every Scapia user is, on most trips, also paying for two or three other people. The card sees the transaction. The app doesn't know the trip exists. There's a Splitwise app for that. And a UPI chain. And a screenshot at midnight. This is the gap.
Four friends, three days, one Scapia card doing all the heavy lifting. The card knows every detail. The split conversation lives somewhere else, in screenshots and reminders.
Aanya pays the full hotel bill on her Scapia card. The other 3 say "we'll split it later." Splitwise tab opened.
Vikram pays this one on his card. Aanya texts: "split this 4-way pls." Group chat now has 2 different "to split" lists.
Karan and Riya only. Aanya pays for everyone (group rate cheaper). Two people owe 1 person. Different math.
17 small transactions across 3 cards. Some on UPI, some on cards. Nobody has a clean record at end of day.
If you accept these seven atoms, the solution is not a feature, it's a logical consequence. None depends on a specific market-size number. Each is either logical or anchored in universal user experience.
When Aanya pays Rs 8,400 at dinner with three friends, the card captures three events (authorization, transfer, receivable). The fourth event, the social debt to Riya, Vikram, and Karan, lives only in human memory.
On every group trip, the cardholder fronts credit, takes risk, settles debts, and keeps records. Banks charge for this work. The cardholder does it for free, badly.
Memory is not a settlement system. The longer the gap between event and settlement, the more friction accumulates. Some debts quietly get forgiven.
The value of a platform to user N rises with how many of N's relevant peers are on it. Scapia today has zero awareness of its users' travel networks. Splits captures that as a side effect of normal usage.
A non-Scapia friend just got Splitwised by a Scapia friend. They have a real debt to settle, a working example of the product, and zero friction. That moment is not bought; it's a byproduct of an existing user paying for dinner.
The strongest moat in retail finance is the user's coordination problem with their peers. Once a friend group's settlement history lives on Scapia, leaving means rebuilding the social graph elsewhere.
Splits drives more transactions through the primary cardholder, because they now front group spend instead of just their own. Same interchange margin, larger gross profit, zero new acquisition cost.
What this means. The proposal is not "build a feature." It's "capture the fourth event that already exists in the world but isn't yet in the database." Once that data exists, network effects, lower acquisition costs, and group-level switching costs follow as logical consequences. The Solution section below is just the user-facing surface of these seven atoms.
Four mechanics that turn every Scapia transaction into a group-aware event. The app sees the trip, the group, and the math. The user just taps "split."
When the answer is "group", everything else (rewards, settlement, currency conversion, photo memory) follows automatically.
Each transaction comes with a "split" prompt. One tap, pick your group, done. The split posts in the app instantly, before you've even left the table.
Geo + spending pattern triggers "Looks like you're on a trip." App pre-creates the trip, suggests the group based on past travel, lets you confirm in one tap.
Friends settle balances inside the Scapia app via a single tap. Money moves over UPI rails behind the scenes, but the user never leaves the brand. Scapia stays the visible layer.
Scapia coins earned on shared transactions split proportionally to the group. Now everyone in your group has a reason to be on Scapia. Group trips become a group rewards engine.
The whole feature lives in moments: at the table, at the gate, at the reckoning. Each screen earns its place by saving 10 minutes of friction.
Four lenses, honest answers. The conclusion is yes, with one regulatory pre-check, one behavioural hypothesis to validate in Phase 1, and zero changes to the existing card-side payment flow.
Tap-to-split is a UI pattern, not a payment innovation. Trip auto-detection uses geo and spend patterns the card already collects. Settlement runs on existing UPI rails. The hardest piece is the social-graph layer (who's in your travel group), which is one entity table and a relationship lookup.
Settlement is just UPI under the hood, not a new payment instrument or a deposit product. Scapia's role is the orchestration UI above existing rails. The card-side flow does not change; we are adding a record-and-settlement layer above it.
Yes, in phases. Phase 1 ships to 1,000 power users in two cities with manual group setup. Phases 2 to 4 add intelligence, group rewards, and forex. Each phase is independently shippable and measurable. No phase blocks any other.
Not initially. The wedge is timing. When the prompt fires at the moment of payment, Scapia wins by default; Splitwise wins only if the user remembers to open it later. Users do not need to "switch tools." They need to stop opening a second tool because the first one already covered it.
Splits is a viral install loop disguised as a feature. Aanya invites her group to settle a trip. Riya, Vikram, and Karan each download the Scapia app to receive their share. Two of them apply for the card within 30 days, because they've now seen the rewards math live.
This is acquisition economics that no paid channel competes with: CAC trends to near-zero on group-driven signups, while LTV climbs because each new user has 3+ social hooks already on the platform.
Splits doesn't just retain users. It cuts CAC. Here's the simplified napkin math, with placeholder numbers I'd refine on Day 1.
One north star plus three supporting metrics. Each maps to one of the seven atomic truths above, so we know what's being tested. Each has a fail condition, so we'd know if the bet didn't land.
For a Scapia user on a group trip, what fraction of their card transactions during that trip get tagged via Splits? This is the single metric that proves Splits is the way Scapia users handle group trips. Below 10 percent at six months would mean the feature did not land.
What fraction of active Scapia users have used Splits at least once in their first 30 days post-launch? Tests whether the in-the-moment prompt is reachable.
Of friends invited to settle a Split, what fraction download Scapia within 30 days? Of those, what fraction apply for the card within 60? Tests whether the social loop actually compounds.
For users who become primary cardholders on group trips, what is the lift in monthly card spend versus their pre-Splits baseline? Tests the revenue thesis directly.
Why these three. Together they triangulate the strategic thesis. Adoption tests whether the in-the-moment prompt actually works as a behaviour change. Network tests whether the viral loop compounds at all. Business tests whether the revenue case is real. Each is independently falsifiable, each is a kill condition for one piece of the argument, and each can be measured cleanly without the counterfactual-modelling problems that retention-style cohort analysis introduces at this stage.
Don't bet the company on Phase 4. Each stop ships something users feel, in a small enough cohort that course-correction is cheap.
Tap-to-split at POS. Manual group setup. Limited to 1,000 power users in Mumbai/Bangalore.
Geo + spend pattern triggers trip mode. Suggested groups based on past co-travelers. Open to all card users.
Scapia coins earned on shared transactions distribute to the whole group. Group leaderboard within Scapia community.
International trips: shared expenses split in INR after live FX conversion. Single global flow, no fee guesswork.
Six likely failure modes. Each paired with a real mitigation, not a hand-wave.
Splitwise has trained a generation of urban Indians to expect a separate app for shared expenses. Muscle memory is a real switching cost, even when Scapia would be a better tool in the same moment.
MitigationSplits opens automatically on the card-holder's tap. The friend just clicks a link, no install required for the first interaction. Lower friction than asking them to switch tools.
If 2 of 4 friends don't have Scapia, splits feel half-finished. Friction doesn't disappear; it just shifts.
MitigationSplits work without requiring all members to be cardholders. Settlement via UPI to non-Scapia members. The non-cardholder gets a smooth payment experience and a soft pitch for the card. Low pressure, high reach.
"I didn't have the dessert." "I wasn't there for that round." Splits in real life have edge cases.
MitigationAdjust-share UI at the group picker. Per-item assignment for restaurants. Quick "I wasn't there" toggle that re-balances the rest. Solve 90% of edge cases, accept the rest.
Federal Bank and RBI have rules around what apps can do with payment data and pseudo-settlement. Some of this might require careful regulatory mapping.
MitigationSettlement is just UPI under the hood. No new regulatory creature. Scapia's role is the orchestration UI. Worth confirming with compliance early, but no fundamental block.
Other Indian travel-fintech could ship a similar feature within months.
MitigationThe moat is the social graph, not the feature. First-mover captures the group networks. After 50K+ groups are on Scapia, switching means rebuilding your travel social graph elsewhere. Not impossible, but real.
Splits scales with trips. A travel slowdown stalls the network effect.
MitigationSplits also work for non-trip group spend (dinners, weekend plans, recurring groups). The trip case is the wedge, but the use case is universal. Falls back gracefully to "everyday splits" if trip volumes dip.
I'd love to intern at Scapia on product/strategy. First task: replace every assumption in this memo with your real numbers, then ship Splits MVP in 4 weeks. Talk to me.
gauravmankele.iitb@gmail.com