What we ran into, and what we did about it
Notes from building and running CARTIQO: real defects and decisions in security, engineering and accessibility, each with the question it answers and the code that shipped.
- Rate limit before you read the body, not after — Should a rate limiter run before or after request validation?
- Parsing the JSON is what breaks the webhook signature — Why does my Stripe webhook signature verification always fail?
- Your checkout return URL is an open redirect unless you pin the origin — Is it safe to build a Stripe success_url from the Origin header?
- The env file your .gitignore does not protect is the one that leaks — How do I check whether an API key was ever committed to git?
- The success page is not a receipt, and treating it as one loses money — Can I fulfil an order on the Stripe success page instead of a webhook?
- Every page on your Next.js site may be sharing one Open Graph description — Why does every page on my Next.js site have the same og:title?
- Your CSS reset outranks your components, and nothing will error — Why is my CSS class not applying even though the selector matches?
- An ARIA role is a promise, and a broken one is worse than none — Do I need keyboard handling if I add an ARIA role?
- We build the site before we invoice for it — How does CARTIQO work, and what do I pay before seeing anything?