Stripe Webhook

Receives and processes Stripe webhook events. The request must include a valid Stripe-Signature header — Stripe adds this automatically.

Handled events:

• checkout.session.completed — fulfills one-time purchases
• customer.subscription.updated — updates subscription tier
• customer.subscription.deleted — downgrades to the highest remaining one-time tier

POST /billing/webhook

Stripe webhook

cURL

curl --request POST \
  --url https://api.comparebench.com/billing/webhook \
  --header 'Content-Type: application/json' \
  --header 'Stripe-Signature: <stripe-signature>' \
  --data '
{
  "id": "evt_1OqXYZ...",
  "type": "checkout.session.completed",
  "data": {
    "object": {}
  }
}
'

200

{}

Receives Stripe webhook events. This endpoint is called by Stripe — you do not call it directly.

The Stripe-Signature header is added automatically by Stripe and is used to verify the payload. Requests without a valid signature return 400.

Handled events:

Event	Action
checkout.session.completed	Fulfills one-time purchases (enthusiast tier)
customer.subscription.updated	Syncs subscription tier changes
customer.subscription.deleted	Downgrades to the highest remaining one-time purchase tier, or free

To test webhooks locally, use the Stripe CLI:

stripe listen --forward-to localhost:8181/billing/webhook

Headers

Stripe-Signature · string · required

Webhook signature from Stripe — used to verify the payload

Body

application/json

Standard Stripe event object. See Stripe docs for the full shape.

id · string

Example:

"evt_1OqXYZ..."

type · string

Event type

Example:

"checkout.session.completed"

data · object

Show child attributes

Response

200

application/json

Event processed

The response is of type object.