Stripe shows the charge, your database has no order. Eight ways the record goes missing between checkout and your orders table, and the query that finds every one.
Payment cleared, the account did not upgrade. Seven causes in subscription access, plus the opposite problem: free users who unlock paid features by editing the browser.
How to find out in one sitting whether one logged-in customer can read or change another's data, why AI-built apps get this wrong, and the fix for the three usual causes.
Stripe took the money but the order never landed in your CRM. Nine places the chain breaks, in the order to check them, plus what a free outside check can and cannot tell you.
Your Stripe webhook passes every test and then fails for real customers. Eight causes, in the order to rule them out, with the exact thing to look at for each.
The deploy says success, the site still runs old code, and a worker you thought was gone keeps processing jobs. Eight checks to find the zombie, with the commands.
A 9.5-severity Next.js flaw (GHSA-673q-mjm6-r5xr) can let strangers run code on some apps. Five checks an owner can do today, in plain words.
The three real ways sk_live_ keys leak from AI-built apps, plus the 5-minute check to find out if yours already has.
The exact mechanism that ships secret keys to the browser in AI-built apps, and the 5-minute grep that catches it before launch.
Someone found your anon key in the bundle. Is that a breach? Here's what the anon key actually grants, and the RLS mistake that turns it into one.
A working checklist for Supabase security: RLS policies, anon keys, service role leaks, and the mistakes I keep finding in AI-built apps.