Inspiration
We run a small content studio. Every finished job ends the same way: one client payment, three or four people, and an awkward conversation about who did what. Today that split happens in spreadsheets, chat threads or a quick "let's just do equal shares" — tools like Splitwise divide a bill, but nothing explains why one person should get more. The person who did the invisible work (the late re-record, the fourth edit) is usually the one who gets under-counted.
What it does
FairSplit turns one PayPal payment for a team job into an explainable split:
- Fund — the client pays the job budget on PayPal checkout. The payment is authorized, not captured. PayPal holds an authorization for up to 29 days (3-day honor period); FairSplit captures only after everyone agrees.
- Propose — the AI reads the production log (script drafts, edit cuts, client review notes, recordings with minutes) and proposes each person's share. Every reason cites the exact log lines.
- Dispute — anyone can object once per version, in plain words, and may attach work that was missing from the log (shown as "added by in a dispute").
- A claim with no new evidence does not move money. In our demo, Jun asked for 70% "because editing is the hardest part" — the AI answered No change and pointed at the edits it had already counted.
- Real missing work does. Sora added an unlogged 22-minute re-recording; the AI checked it fits the timeline and moved her from 16% to 19%, saying exactly which line she added. (Same run as the video: v1 Mina 32 / Jun 52 / Sora 16 → v3 32 / 49 / 19.)
- Agree — each contributor approves the current version. A new version resets approvals.
- Pay — after unanimous approval FairSplit captures the authorization and sends one PayPal Payouts batch to everyone. The receipt shows the real capture, batch and transaction IDs. (In the video run all three sandbox receivers got their payouts: batch status SUCCESS, 3 of 3.)
The AI never moves money. It only proposes. You can also paste your own team's work log (CSV) and split your own job.
How we built it
- PayPal Orders v2 (
intent: AUTHORIZE→ capture after agreement) and PayPal Payouts (one batch, one item per contributor), all in the sandbox. - Claude (Anthropic API) in a manual tool-use loop —
list_log_events,get_contributor,get_disputes,submit_proposal— capped at 6 rounds and 20 seconds. - The server, not the model, turns percentages into cents (largest remainder) and rejects proposals that don't sum to 100%, cite non-existent log lines, or change someone's share without citing that person's evidence.
- If the model fails, a transparent rule-based fallback (labelled on screen) keeps the flow working.
- Cloudflare Workers + a Durable Object for state; React + Vite for the UI. Dispute text is treated as data, never as instructions.
Challenges we ran into
- Keeping the AI honest under pressure: our first version raised Jun's share a little after his "70%" demand. We added a server rule — a share may only change if the explanation cites new evidence for that person — and measured it on a small sample of real Claude runs: the weak dispute left the split unchanged in 3 of 3 runs, the missing-work dispute raised the share in 3 of 3.
- Our sandbox merchant account is Korean, and PayPal blocks KR→KR payments. Judges can still pay as a US guest with a PayPal test card (see "Try it").
What we learned
Showing why a number moved (or why it didn't) builds more trust than any single "fair" number.
What's next
Import logs automatically from the tools teams already use (file versions, review tools, recording sessions) and give each contributor their own invite link instead of the demo's "Viewing as" switch.
Try it
- Live demo: https://fairsplit.solhun.com (PayPal sandbox — no real money moves)
- Pay it yourself: Fund with PayPal → Pay with debit or credit card → country United States → card 4032 0393 6134 9402, expiry 06/2028, CVV 427, any US address, turn off "create account".
- Code (MIT): https://github.com/woorichicken/fairsplit — a new project: the repository was created and everything in it was built during the submission period, starting Nov 12, 2026 (see the commit history).
Built With
- anthropic
- claude
- cloudflare-workers
- durable-objects
- paypal
- paypal-orders
- paypal-payouts
- react
- typescript
- vite