Every model writes the deprecated Connect account shape with total confidence

stripe.accounts.create({type: 'express'}) is the pre-December-2025 shape Stripe now labels deprecated -- and it's exactly what an agent's training data emits first, with no warning (D1).

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?

Writing stripe.accounts.create({type: 'express'}) and reading account.charges_enabled / account.payouts_enabled produces code that looks completely correct and matches years of Stripe documentation and tutorials -- and it's the superseded account shape. Stripe shipped Accounts V2 in December 2025 and now labels the legacy Standard/Express/Custom account types deprecated outright, recommending V2 for new integrations.

Why this one is easy to get wrong

Every model's pretraining is dominated by the pre-2025 shape, because it was correct and universally documented for years -- an agent writing stripe.accounts.create({type: 'express'}) is writing what the overwhelming majority of indexed examples still show, with no signal in the SDK call itself that the shape it just wrote is the one Stripe has since superseded.

What you get instead

D1 pins account creation through POST /v2/core/accounts (stripe.v2.core.accounts.create) instead, following Stripe's own explicit recommendation that new Connect integrations use the v2 path. V1 and V2 address the same underlying account object -- existing v1 accounts and webhook events keep working against v2-created accounts -- which is exactly what lets the pack's webhook handling rely on the v1 account.updated event even for accounts created through v2.

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