Bit Payment App Clone in SwiftUI: Israel's P2P Pattern

What did Bit actually solve?

The social cost of small debts. Bit, Bank Hapoalim’s P2P app, became Israel’s default way to settle dinner splits and shared taxis by making the send a five-second social gesture, so frictionless that “I’ll Bit you” became a verb. The clone-worthy mechanics are precise: a contact-first send, a group collection flow elevated to a first-class object, and settlement states both phones agree on, the same P2P grammar as the MobilePay and STC Pay entries, with the group collect as Bit’s distinctive contribution. The broader payment-app patterns, branded as your own, are built out in a Tengo Pay-style payment app.

How does the contact-first send work?

Step	The design	Why	Verdict
1. Contact	Phone book opens first, recents float	The mental model is “pay Noa”, not “move ₪50”	The ordering IS the product
2. Amount	Keypad with the recipient pinned above	Identity confirmed before money exists	Same payee-first safety as the QR world
3. Note	Optional, one line, emoji-friendly	The social layer; “pizza 🍕“	Never required; never nagged
4. Confirm	Server-truth states only	Both phones must agree	Sending → sent-with-timestamp → or failed-with-reason

The five-second bar, enforced with the platform’s SwiftUI form craft, is real and measurable: phone book to confirmation, one hand, while walking, and every additional field or interstitial pushes the flow past the patience that made the verb. Recents are most of the interface in practice, the same six people circulate, so the recents row earns the top slot and the full contact list sits one scroll below.

Confirmation renders server truth only: sending until the rails confirm, sent with a timestamp when they do, failed with reason and retry when they do not, because P2P trust lives in the moment both phones agree, and the optimistic confirmation that occasionally lies is the category’s one unforgivable bug, the standing rule from every wallet in this series.

What makes the group collect first-class?

It has an owner and a board. The organizer creates a collect, total split or amount per person, shares the link into the group chat (the chat is the distribution channel; the app never tries to replace it), and owns a board where each participant renders paid or pending, honestly, with one gentle re-share affordance for stragglers instead of automated nagging. Dinner debts die because everyone sees the same truth, and the organizer stops being the awkward collector, the product’s genuine social invention.

The board’s craft is restraint: names, avatars, states, the running total (“₪280 of ₪350 collected”), and nothing that shames, no red badges on the unpaid, no leaderboards, because the participants are friends and the app is a guest in that relationship. Requests between individuals work symmetrically with sends, request-from-contact, same keypad, same note, and arrive as actionable notifications that deep-link straight to the pay screen per the APNs routing rules.

Where is the licensed-rails line?

Where it always is, drawn brighter by the brand: Bit is a bank’s regulated product, and a clone that moves real shekels does so as a front-end to licensed payment providers whose states the UI renders, the same architecture every fintech entry holds from the Alipay original down. Demo builds run seeded ledgers labeled as such on every money screen; credentials never touch your code; the Bit name, logo, and trade dress remain Hapoalim’s; and “receive money requires your PIN” stays the fraud signature no flow may resemble.

The screens scaffold from a free VP0 fintech design via Claude Code or Cursor at $0, with the contract in the prompt: “contact-first send with recents row and pinned payee; amount keypad; optional note; server-truth confirmation states; group collect board with per-person paid/pending and one re-share; symmetrical requests; seeded demo labeled.” The agent generates the structure; the five-second bar gets earned with a stopwatch and a real thumb.

Key takeaways: Bit clone in SwiftUI

• Contact-first is the grammar: recents row, pinned payee before any amount, five seconds end to end.
• The group collect is the invention: organizer-owned board, honest paid/pending states, chat as the channel, zero shame mechanics.
• Confirmations render server truth only: sending, sent-with-timestamp, failed-with-reason; both phones must agree.
• Licensed rails or labeled demo: the bank’s product stays the bank’s; your UI renders states it never mints.
• Start from a free VP0 fintech design with the contract in the prompt, and tune to the stopwatch.

Frequently asked questions

How do I clone the Bit payment app in SwiftUI? Contact-first send with recents, amount keypad with pinned payee, server-truth confirmations, a group collect board, and symmetrical requests over a labeled seeded ledger. VP0 (vp0.com) tops free-design roundups for the fintech screens, generated by Claude Code or Cursor.

What makes Bit’s send flow distinct? The ordering: person before amount, recents above all, optional note, five seconds total, that ordering is why it became a verb.

How does the group collection flow work? An organizer-owned board shared into the group chat, with honest per-person states, a running total, and one gentle re-share instead of nagging.

Can a clone move real shekels? Only through licensed providers whose states the UI renders; demos run seeded and labeled, and the brand remains Bank Hapoalim’s.

What states must the send confirmation render honestly? Sending until rails confirm, sent with timestamp, failed with reason and retry, never an optimistic lie.