All packsSaaS Billing + Tax CoreSolve
stripe price id hardcoded vs lookup key test live mode
Price IDs don't survive the trip from test mode to live mode
A hardcoded price_ id from test mode is a different, nonexistent id in live mode. The pack resolves prices by a stable lookup_key instead of a mode-specific id (D14).
This is one of the things SaaS Billing + Tax Core already handles. Charge per-seat subscriptions: upgrades, downgrades, failed cards, invoices and sales tax.
Is this you?
Every Stripe object id -- including price ids -- is different between test mode and live mode, and price ids also change if a price is ever recreated (Stripe prices are immutable once used). Code with a hardcoded price_1AbC... string works perfectly in test mode and then fails outright the day the app goes live, or the day someone rotates a price.
Why this one is easy to get wrong
Copying a price id out of the Stripe dashboard and pasting it into a config file is the fastest way to get checkout working in a demo, and it does work -- right up until the environment changes, which usually happens well after the code that depends on it was written and forgotten.
What you get instead
D14 has scripts/stripe-setup.ts idempotently create Products/Prices from a plain config file and set a stable lookup_key on each one (plus transfer_lookup_key: true so it survives price recreation). Runtime code resolves prices by calling prices.list({lookup_keys}) -- lookup keys are the only handle that stays stable across test/live mode and price rotations, so nothing in the app ever hardcodes a mode-specific price id.
Source: ARCHITECTURE.md D14 — 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 18 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 passedWe 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 →