Skip to content
Sign in

Example run Brindle Coffee › Runs › Run #3

Prove invoice.paid · renewal

Stripe · From sub_1QH…4drI · #01 #03 #04 · localhost:3000/webhooks/stripe

Run by maya-mbp from the web app

A real run against a deliberately buggy handler. Get a URL to prove your own.

3 findings

Critical 1 High 1 Medium 1 Info 1

exit 1

8 scenarios · 16 deliveries · 43.2 s · CI exit 1 (--fail-on high)

State after D5 · orders.count

1 to 2

Expected 1 · got 2

Same request, same response, a different state.

Findings

  1. Level 1 · transport · evidence D12

  2. Level 2 · judged on maya-mbp · evidence D4 D5 D10 D11

    Same request, same response, a different state.

    What happened

    D5 delivered the same invoice.paid event as D4. Both got 200 {"received":true}, but orders.count went 1 → 2, expected 1. The retry D11 did the same after D10. Only the probe could see this.

    Why it matters

    Stripe may deliver the same event more than once, and retries failed or timed-out deliveries with backoff for up to 3 days in live mode. Each duplicate creates another order.

    Stripe docs › Webhooks › Handle duplicate events · Retry behavior

    Likely cause: The handler doesn't record the event id before it writes.

    Fix

    Record event.id before creating the order and return 200 early when it is already recorded. After the fix, D5 and D11 should leave orders.count at 1.

    Express (detected from X-Powered-By)

    // before creating the order
    const { rowCount } = await db.query(
      'INSERT INTO processed_events (id) VALUES ($1) ON CONFLICT DO NOTHING',
      [event.id]
    );
    if (rowCount === 0) return res.sendStatus(200); // already handled
  3. Level 1 · transport · evidence D10 D16

  4. Level 2 · judged on maya-mbp · evidence D6 D15 · Info · not counted

Deliveries

Deliveries of this run, grouped by scenario
D+msEventStatusLatency (10 s budget)orders.countResult
Once · 200 × 3 · orders.count 0 → 1
D1+1 320invoice.paid200184 ms0 → 1▬ pass
D2+1 684payment_intent.succeeded200121 ms1 → 1▬ pass
D3+1 985customer.subscription.updated200143 ms1 → 1▬ pass
Twice · 200, 200 · orders.count 1 → 2 on D5, expected 1
D4+3 978invoice.paid200212 ms0 → 1▬ pass
D5+4 720invoice.paid= D4′200196 ms1 → 2 · expected 1 High · F2
Shuffled · reversed · orders.count 0 → 1 · status not probed
D6+6 766customer.subscription.updated200138 ms0 → 0▬ pass
D7+7 084payment_intent.succeeded200117 ms0 → 0▬ pass
D8+7 381invoice.paid200199 ms0 → 1▬ pass
Late · 400 in 41 ms · rejected as expected
D9+9 430invoice.paidt − 360 s40041 ms0 → 0▬ pass (rejected)
Retry after error · D10 11 840 ms → retry D11 → orders.count 1 → 2
D10+11 321invoice.paid20011 840 ms +1 840 over0 → 1 Medium · F3
D11+25 191invoice.paidretry200205 ms1 → 2 · expected 1 High · F2
Tampered · 200 in 167 ms · accepted a changed body
D12+27 246invoice.paidbody changed200167 ms0 → 1 · expected 0 Critical · F1
Burst · 200 × 3 · 312–601 ms · orders.count 0 → 1 (final)
D13+29 263invoice.paid200601 ms—▬ pass
D14+29 265payment_intent.succeeded200312 ms—▬ pass
D15+29 266customer.subscription.updated200448 ms—▬ pass
Slow budget · 10 420 ms · 420 ms over budget
D16+31 714invoice.paid20010 420 ms +420 over0 → 1 Medium · F3