Stripe Billing Events
Public Stripe webhook example endpoint with realistic invoice and payment events.
Receives Stripe invoice and payment lifecycle events and forwards them for downstream processing.
Endpoint URL
Use this endpoint when configuring the webhook sender:
https://hook-xxxxxx.fasthook.io/Example request (curl)
curl -X POST "https://hook-xxxxxx.fasthook.io/" \
-H "Content-Type: application/json" \
-H "Stripe-Signature: t=1713600000,v1=***redacted***" \
-d '{"id":"evt_1QxYz","type":"invoice.paid","data":{"object":{"id":"in_123","customer":"cus_123"}}}'Example headers
{
"content-type": "application/json",
"stripe-signature": "t=1713600000,v1=***redacted***",
"user-agent": "Stripe/1.0 (+https://stripe.com/docs/webhooks)"
}Example payload (JSON)
{
"id": "evt_1QxYz",
"type": "invoice.paid",
"created": 1713600000,
"data": {
"object": {
"id": "in_123",
"customer": "cus_123",
"status": "paid",
"amount_paid": 4900,
"currency": "usd"
}
}
}How this webhook works
- Provider sends a POST request to the endpoint URL.
- FastHook stores the request headers, body, path, query, and source verification result.
- Matching connections create outbound events for configured destinations.
- Delivery attempts record destination response status, body, latency, and retry context.
- Failed events can be retried after the destination or route is fixed.
Common debugging checks
- Send Stripe traffic to a dedicated FastHook source per environment.
- Use event.id for deduplication and receiver-side idempotency.
- Inspect FastHook events and attempts before retrying billing deliveries.
Integration context
This page targets stripe webhook flows and is optimized for debugging and testing scenarios developers face in production.
Last updated: Apr 21, 2026
Owner tools
Need full request, event, and attempt records? Use the private dashboard for retries, filters, transformations, and source or destination controls.