A seller who takes one chargeback and vanishes leaves the platform down for good

losses_collector: application means the platform absorbs a connected account's negative balance -- and after 180 days negative, Stripe sweeps the platform's own reserve to zero it out (D11-D12).

This is one of the things Marketplace Payouts & Connected Accounts already handles. Take payment from buyers and pay out sellers, with the onboarding and identity checks Stripe requires.

Buy for $1993 of 3 clean-room builds passed · full refund if it fails on your machine

Is this you?

A seller who takes a large chargeback and then never sells again leaves their Stripe balance negative with no future transactions to recover it from -- and under losses_collector: 'application' (the platform's own onboarding configuration), that negative balance is the platform's liability, not the seller's. Left untracked, it surfaces up to 180 days later as an unexplained reserve sweep against the platform's own account.

Why this one is easy to get wrong

The dispute-handling code path looks complete once it correctly debits the platform and attempts to recover the seller's net from their balance -- what's easy to miss is that recovery can fail (the seller's balance is already too low or empty), and nothing about a successful-looking dispute handler surfaces that the shortfall is now a standing, un-clawed-back liability sitting quietly for up to six months.

What you get instead

disputeAction() computes expectedNegativeBalance directly -- how far a reversal would drive the seller's balance negative -- and Seller.negativeBalance tracks accrued exposure so it's visible on the /marketplace page immediately, rather than surfacing only when Stripe's 180-day sweep eventually happens. payments.debit_negative_balances, which lets Stripe attempt to auto-debit a seller's bank account, is deliberately left as a manual live-cutover checklist item rather than a code default, since it carries real consumer-protection implications the pack won't silently opt an operator into.

Source: ARCHITECTURE.md D11, D12 — checkable in the pack you receive

How you actually use this

You don’t install a library or wire up an SDK. Your own coding agent builds the code in your project, and you keep it — no runtime dependency on us.

Step 1
Download and unzip
You get a folder: the docs that tell an agent what to build, a starting skeleton, and the test suite that decides when it's done.
Step 2
Open it in Claude Code or Cursor
Point your coding agent at the folder. Nothing to install, no account with us, no API key.
Step 3
Paste one prompt
The pack contains the exact prompt. Paste it as your first message and leave it alone — it works through the build itself, choosing a cheaper or stronger model per task.
Step 4
Run ./verify.sh
One command. It prints a pass or fail for every check. Green means the build is done — the same script we ran to produce the receipt on this page.

Typical build: about 25 minutes of your agent working, mostly unattended. Then you integrate the working module into your app the way you would any code you’d written yourself.

Why you can believe this

3 of 3 runs passed

We ran this pack from an empty folder 3 times and published exactly what happened — every check, the model, the token cost, the wall time. Not a testimonial, and not our opinion: the same verify.sh you run yourself. Read the full receipt →

Buy for $199 14-day refund if verify.sh fails →