-
Payments
Separate test and live payment modes completely
Locks test keys and live keys to their environments so test charges can't hit real cards and vice versa.
Free Prompt
What This Does / How This Helps
Draws a hard line between test and live payment modes, enforced at startup, so a misconfigured environment can't charge real cards with test flows or leak test behavior into production. Mode mixups are a rite of passage for payment launches, and both directions are bad: production running test keys means nobody's actually being charged (free product, awkward emails), and a staging environment holding live keys means your QA flow just charged a real card. The startup assertion makes the mismatch impossible to boot with. The webhook audit matters too: events signed with the wrong secret or delivered to the wrong environment's endpoint create phantom state that's miserable to debug.
Want to skip doing this by hand?
Fortivibe audits your app for all of the areas these prompts cover (and more).