Transfers active and payouts inactive is normal -- and money gets stuck there

payouts became a Stripe capability, not the boolean payouts_enabled -- and a seller can have active transfers with inactive payouts, a legal but useless state where money reaches Stripe and stops (D5).

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?

Reading account.payouts_enabled to decide whether a seller can actually receive money reads a field that no longer exists on the V2 account shape at all -- payouts became a per-capability status in a 2025-04-30 change. Worse, a seller can have an active stripe_transfers capability and an inactive payouts capability simultaneously, which is a normal, common state: money moves into their Stripe balance and then just sits there, unable to reach their bank.

Why this one is easy to get wrong

charges_enabled and payouts_enabled are the two booleans every pre-2025 Connect tutorial checks, so reaching for them is the well-worn pattern -- and releasing funds to a seller whose transfers capability is active looks entirely correct by every test that only checks 'can this seller receive a transfer,' because a transfer to a payouts-inactive account still succeeds, it just can't leave Stripe afterward.

What you get instead

sellerStateFromAccount() derives seller state purely from capability status -- transfersStatus and payoutsStatus, read from configuration.recipient.capabilities.stripe_balance -- never from the removed booleans. releaseDecision() explicitly allows a release when transfers is active even if payouts is not, since blocking it would strand the money on the platform's own balance instead, which is worse; it returns warnPayoutsDisabled: true so the seller can be told, rather than silently leaving them unpaid with no signal at all.

Source: ARCHITECTURE.md D5 — 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 →