Stripe doesn't offer escrow. The hold is just the absence of a transfer.

Stripe states plainly it doesn't provide escrow services -- a fulfillment hold under separate charges and transfers is nothing more than the gap between capturing a payment and calling transfers.create (D7).

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?

Looking for an escrow product, a held-funds API, or a configuration flag to hold buyer money before paying a seller finds nothing, because Stripe explicitly does not offer one -- 'Escrow has a precise legal definition, and Stripe doesn't provide escrow services or support escrow accounts.' Building a hold as if it were a distinct Stripe feature, rather than an application-level gap, produces code searching for an API that was never going to exist.

Why this one is easy to get wrong

Marketplaces holding buyer funds before paying a seller is common enough that 'escrow' feels like it should map to a named Stripe capability, the same way transfers and payouts do -- there's no natural reason to expect the entire feature is actually just an absence, something the platform code has to construct itself rather than configure.

What you get instead

D7's releaseDecision() makes the hold explicit application logic: under D2's charge model, buyer funds sit on the platform balance from capture until the platform itself calls transfers.create, and that gap is the whole hold -- there is nothing to configure. The function checks, in order, whether a dispute is open (highest priority, not bypassable even with force), the order's state, the seller's active status, and finally whether holdUntil has actually elapsed, with force: true as the only documented early-release lever.

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