PAY-008medium SeverityPayment Processing & Webhook Integrity
Checkout Session Creation Rate-Limited
Unprotected checkout session endpoints allow malicious bots to spam Stripe API calls and hit provider rate limits.
1-Click Fix Prompt for Cursor & Claude Code
Review my codebase for "Checkout Session Creation Rate-Limited" (PAY-008). Issue: Unprotected checkout session endpoints allow malicious bots to spam Stripe API calls and hit provider rate limits. Remediation required: Apply rate limiting to checkout creation endpoints and require an active user session. Please: 1. Locate any occurrences of this issue across my repository. 2. Refactor the code to follow production standards without breaking existing functionality. 3. Provide a clear command or step to test and verify the fix.
Why AI Assistants Write This Bug
Unprotected checkout session endpoints allow malicious bots to spam Stripe API calls and hit provider rate limits.
AI code generation prioritizes immediate syntax execution over production edge cases. When an assistant hits an undefined variable or strict type error, it frequently takes the path of least resistance rather than implementing standard pre-launch security patterns.
Code Comparison
Common AI Code PatternVulnerable
// Vulnerable AI-generated pattern for: Checkout Session Creation Rate-Limited
// Flawed Stripe webhook handler
export async function POST(req: Request) {
const body = await req.json(); // BUG: Fails signature verification!
const signature = req.headers.get("stripe-signature");
// Unhandled events drop silently
return Response.json({ received: true });
}Launch-Ready Fix
// Production-ready fix for: Checkout Session Creation Rate-Limited
// Fixed Stripe webhook with raw text buffer
export async function POST(req: Request) {
const body = await req.text(); // Raw text preserves HMAC signature
const signature = req.headers.get("stripe-signature");
const event = stripe.webhooks.constructEvent(body, signature!, process.env.STRIPE_WEBHOOK_SECRET!);
// Acknowledge receipt with 200
return Response.json({ received: true }, { status: 200 });
}Remediation & Verification Checklist
Remediation: Apply rate limiting to checkout creation endpoints and require an active user session.
- Search your codebase for pattern matching "Checkout Session Creation Rate-Limited".
- Apply the recommended remediation: Apply rate limiting to checkout creation endpoints and require an active user session.
- Run local build and test commands to ensure no regressions.
- Verify in your browser or with curl that the issue is resolved.
Audit All 108 Checks in One Click
Checking items one by one takes hours. Let us do it in 2 minutes.
With the Founder Pass ($15 one-time), we automatically scan your repository for this issue, plus all other 107 launch checks across secrets, Stripe webhooks, Supabase RLS, and security headers.