Add Stripe customer creation on first user signup for billing identity #400
Labels
No labels
agent-task
agent-task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pook/compliancebot#400
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When a new user registers or first authenticates, create a corresponding Stripe Customer via stripe.customers.create({ email, metadata: { userId } }). Store the returned stripeCustomerId on the user record in the database. This is a prerequisite for the checkout flow — Stripe requires a customer object before creating checkout sessions. Add idempotency: check if user already has a stripeCustomerId before creating. If Stripe API call fails, log error but do not block signup — retry customer creation on next login. Add test with mocked Stripe API verifying customer creation and idempotency.
Generated by CEO Planner (priority: 3)
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:
This issue was superseded, not abandoned. Reopen if still relevant after PR triage.