delay_days was renamed, and it's the wrong lever for a fulfillment hold anyway

delay_days became delay_days_override on the Balance Settings API, and Stripe caps how long money may sit in a connected account under manual payouts -- 10, 90, or 730 days depending on country (D8).

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?

Reaching for delay_days to build a fulfillment hold misreads what it actually controls: it governs how long money sits in the connected account's own balance after a transfer already happened, not whether the platform can hold funds before transferring at all -- and the parameter itself was renamed to delay_days_override on the Balance Settings API, so code written against the old name doesn't even compile against the current one.

Why this one is easy to get wrong

A parameter named delay_days reads like exactly the knob a hold-before-payout feature needs, and it's genuinely about timing money movement -- the confusion is reasonable, because the pack's actual hold mechanism (the absence of a transfer) lives entirely before this parameter is ever relevant, and nothing about the name signals that boundary.

What you get instead

buildPayoutSettingsParams() sets sellers to schedule: {interval: 'manual'} and never touches delay_days_override at all, because the platform-side hold already governs the timing that matters. What the pack does encode explicitly are the post-release country caps Stripe enforces on manual-schedule balances -- 10 days for Thailand, 2 years for the US, 90 days everywhere else -- as a live-cutover checklist item, since exceeding them is a real operational constraint the code doesn't otherwise protect against.

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