Point refresh_url at a page, and a slow seller is stuck there forever

Stripe Account Links are single-use and short-lived -- refresh_url has to mint a brand new link and redirect, not render a static page, or an onboarding seller who takes too long gets permanently stuck (D4).

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?

Pointing refresh_url at a plain page -- 'your onboarding link expired, try again' -- looks like reasonable error handling, and it's a dead end: the seller has no way to actually get a working link again unless that page itself triggers minting a new one. A seller who takes too long filling out KYC, or who navigates away and comes back later, is stuck exactly there.

Why this one is easy to get wrong

refresh_url reads like a standard 'expired link' redirect target in most auth and onboarding flows, where showing an explanatory page is the normal, correct response to an expired token -- Account Links are unusual in that the only correct response to expiry is generating a brand new one immediately, which isn't the default pattern most onboarding-link handling follows.

What you get instead

D4 has refresh_url point at an API endpoint (/api/sellers/onboard) that creates the account if it's missing and always mints a fresh Account Link before redirecting -- never a rendered page. The pack's database also never tries to mirror any KYC field, because Stripe stops sending identity updates the moment an Account Link is created; only capability status and requirement counts are stored, which is exactly what a hosted-KYC integration is supposed to leave to Stripe.

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