Verify Stripe webhook signature and extract customer data on checkout.session.completed #358

Closed
opened 2026-04-10 12:32:56 -04:00 by pook · 1 comment
Owner

Create src/routes/webhooks/stripe.ts handler for POST /webhooks/stripe that: (1) reads raw body via express.raw({ type: 'application/json' }), (2) verifies signature using stripe.webhooks.constructEvent, (3) on checkout.session.completed extracts customer_email and subscription ID, (4) returns 200. Return 400 for invalid signature, 500 for unexpected errors. Add test with a signed webhook payload and an invalid signature asserting 400. Replaces stale #306 with exact scope.


Generated by CEO Planner (priority: 3)

Create `src/routes/webhooks/stripe.ts` handler for POST /webhooks/stripe that: (1) reads raw body via `express.raw({ type: 'application/json' })`, (2) verifies signature using `stripe.webhooks.constructEvent`, (3) on `checkout.session.completed` extracts customer_email and subscription ID, (4) returns 200. Return 400 for invalid signature, 500 for unexpected errors. Add test with a signed webhook payload and an invalid signature asserting 400. Replaces stale #306 with exact scope. --- *Generated by CEO Planner (priority: 3)*
Author
Owner

Bulk-closed 2026-04-10 during pipeline triage.

Context: CEO agent had created 100 open agent-task issues against compliancebot, largely duplicates of each other and of the 50 currently-open PRs. Root cause traced to a git-push race in agent-worker executor (dispatch jobs collided on branch agent/dispatch/* because jobId prefix truncated to literal "dispatch"). Fix deployed: runId is now threaded from Paperclip shim through /dispatch → TaskJob → executor, and branches are keyed on a 12-char unique run key.

What to do next:

  1. Triage the 50 open PRs at https://192.168.183.110:3000/pook/compliancebot/pulls — many are ready to merge
  2. CEO should halt new task creation until open PRs drop below 10
  3. Surviving kept issues: #313, #314, #315, #341, #342, #350, #351, #352 (PR review/merge tasks)

This issue was superseded, not abandoned. Reopen if still relevant after PR triage.

Bulk-closed 2026-04-10 during pipeline triage. **Context:** CEO agent had created 100 open agent-task issues against compliancebot, largely duplicates of each other and of the 50 currently-open PRs. Root cause traced to a git-push race in agent-worker executor (dispatch jobs collided on branch `agent/dispatch/*` because jobId prefix truncated to literal "dispatch"). Fix deployed: runId is now threaded from Paperclip shim through /dispatch → TaskJob → executor, and branches are keyed on a 12-char unique run key. **What to do next:** 1. Triage the 50 open PRs at https://192.168.183.110:3000/pook/compliancebot/pulls — many are ready to merge 2. CEO should halt new task creation until open PRs drop below 10 3. Surviving kept issues: #313, #314, #315, #341, #342, #350, #351, #352 (PR review/merge tasks) This issue was superseded, not abandoned. Reopen if still relevant after PR triage.
pook closed this issue 2026-04-10 14:47:43 -04:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pook/compliancebot#358
No description provided.