Split & Pay — Group expenses.

Split a tab, share a link, settle without IOUs

Other splitter apps make every participant create an account, add friends, and wait for the rest to install before a balance settles. Most one-off tabs — dinners, group trips, shared subscriptions — never resolve because the friction is on the wrong side.

Public share routes via short room codes — anyone with the link sees the tab, no signup required to view a balance. Settlement is a status flip with a free-text method tag (Venmo, Zelle, Cash App, cash) — splitnpay does not act as a payment processor, the money moves out-of-band and the room records it.

• Mobile
  iOS + Android via React Native — per the product page's `operatingSystem` metadata.
• Web
  Next.js App Router with public `/apps/splitnpay/r/[code]` share routes and per-room OG images.
• Settlement
  Status-flip API (`paid` / `pending`) tagged with `method` (Venmo / Zelle / Cash App / cash) — not a payment processor.
• Hardening
  Settle API is rate-limited per-IP and uses per-JTI dedup so a replayed request can't flip the same share twice.

• 0 signups
  To view a tab — the participants who would never install are still in the flow.
• OG per share
  Each `/r/[code]` URL renders a custom OG image so previews carry the room context.
• Replay-safe
  Per-JTI dedup on the settle API closes the duplicate-submission window inherent to public routes.

• 1A real room-creation API with entropy-checked codes — current demo codes are hardcoded.
• 2Multi-currency support beyond the single-`currency` field, ideally with a per-room rate snapshot.
• 3Per-room rate-limit key on the settle API in addition to the current per-IP limit, so a single shared NAT can't burn another room's budget.