All packsSaaS Billing + Tax CoreSolve
stripe tax automatic calculation not collecting tax jurisdictions
automatic_tax: true collects zero tax with zero registrations
Stripe Tax only calculates and collects tax in jurisdictions where you've added a registration -- flipping the flag on with no registrations silently collects nothing (D18).
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?
Turning on automatic_tax: {enabled: true} feels like it should mean "Stripe now handles tax" -- but Stripe Tax only calculates and collects tax in jurisdictions where a registration has actually been added in the Stripe dashboard. Zero registrations means zero tax collected, silently, on every invoice, and the resulting liability is the merchant's, not Stripe's.
Why this one is easy to get wrong
The flag's name and Stripe's own marketing describe it as fully automatic, and the checkout session parameter itself has no failure mode to catch -- it succeeds whether or not any registration exists, so there's no error, no warning, nothing an agent (or a human) would notice until a tax authority does, which can be months or years later.
What you get instead
D18 documents this as an operator-facing boundary code cannot close: enabling Stripe Tax, adding your home registration, and checking the threshold-monitoring tab monthly are manual dashboard steps, made an explicit blocking checklist item in the pack's prompts rather than something the build silently assumes is handled.
Source: ARCHITECTURE.md D18 — 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 →