Stripe Connector Catalogue

Setup reachability

Unavailable for the WordPress-only design-partner release. Do not supply credentials or configure this connector for the current release.

Webhook boundary

The source-defined connector-support endpoint is /api/webhooks/stripe-support?connector_id=<uuid>. It bounds the payload, verifies the endpoint signature, then returns private/no-store 409 with design_partner_release_deferred before the support-event allowlist or Inngest dispatch. The worker applies the same release fence before event data, ticket, message, or pipeline work. Future allowlist/dispatch code remains dormant; a 409 may cause provider retry. Configured connector, signing secret, provider delivery, Inngest, downstream effect, deployment, live, product, and independent read-back proof remain open.

Do not point a connector webhook at /api/webhooks/stripe. That is the separate direct Keva billing endpoint, uses its own endpoint signing secret, and processes billing events synchronously rather than through the connector-support event path. Customer billing mutations and three subscription-status event types remain suspended under their documented reconciliation boundaries. Signed checkout completion is private/no-store 503 stripe_checkout_event_suspended after signature/body verification and before receipt, attempt, database, Stripe retrieval/subscription, effect, audit, or outbox work. Receipt/attempt/reconciliation code and schema are prospective dormant custody, not active production processing. This does not prove configured/provider, migration, deployment, live, product, or independent read-back behavior. Other signed event types remain no-op 200 responses.

Current status

Credential admission and a stored row are not provider authentication, idempotency, effect, independent read-back, rollback, or product proof.