Stripe webhook telemetry

Test the integration

Send and verify events with Stripe webhook telemetry

Use Stripe webhook telemetry where your app knows the final result. Collect only the fields you need, then verify a test event before building charts.

1
Choose the outcome
Webhook debugging
2
Define the contract
provider_event_id, event_type, livemode, endpoint, and received_at
3
Log the final result
Verify the Stripe-Signature header before trusting or logging any event fields, and never send the signature or raw body to Telemetry.
4
Check the stored event
Exercise a known fixture, then inspect webhook_processed for one correctly typed terminal row.

Before you start

A server endpoint that verifies Stripe signatures against the unmodified request body
Persistent deduplication keyed by the Stripe event identifier
A fast acknowledgement path with slow downstream work moved to an idempotent job

Delivery setup

Install and initialize server-side

Import telemetry-sh in server-only code and initialize it once with process.env.TELEMETRY_API_KEY. Keep ingestion credentials out of browser bundles, client-visible environment variables, source control, logs, and exception messages.

stripe-webhooks-install

npm installation

bash

npm install telemetry-sh

1Create one reusable server-side client. Set its timeout and retry limit.
2Log an event when the operation succeeds, fails, retries, or times out.
3Send test events with known results and inspect the stored rows before enabling an alert.

Snippet

Start with one structured event

Add this shape where the workflow completes, fails, or retries. Then build the dashboard from real fields.

stripe-webhooks

Stripe webhook telemetry event

javascript

await telemetry.log("webhook_processed", {
  provider: "stripe",
  provider_event_id: event.id,
  event_type: "invoice.payment_succeeded",
  status: "success",
  latency_ms: 328,
  downstream_job_count: 2,
  idempotency_outcome: "new_event",
  livemode: event.livemode,
});

Event schema

provider_event_id, event_type, livemode, endpoint, and received_at

status, status_code, latency_ms, attempt, and idempotency_outcome

downstream_job, downstream_status, error_type, account_id, and release

Check your setup

Checkpoint 1

Verify the Stripe-Signature header before trusting or logging any event fields, and never send the signature or raw body to Telemetry.

Checkpoint 2

Record duplicate delivery separately from duplicate business processing; the event identifier should make the latter impossible.

Checkpoint 3

Connect the acknowledged delivery to a downstream job outcome so a quick 2xx response cannot hide failed subscription or invoice work.

Verification

Prove the event arrived

Run this after exercising known success and failure cases. Replace the fallback table name if your final event contract differs from the snippet.

stripe-webhooks-verification

Stripe webhook telemetry verification query

sql

SELECT *
FROM webhook_processed
ORDER BY timestamp_utc DESC
LIMIT 20;

Confirm one terminal row per logical outcome, with the expected status, identifiers, units, and UTC time.

Inspect the inferred schema and verify that retries do not change field types or generate a new logical event ID.

Search the stored fields for credentials, raw payloads, prompts, private content, and unbounded error messages.

Exercise a provider timeout, ingestion rejection, and process shutdown before treating the dashboard as complete.

Implementation references

Review the event contract, data-safety guidance, and upstream primary documentation before enabling a new production path.

Webhook debugging use case Webhook completion SQL Redacting sensitive data Stripe webhook endpoint guidance

Where to log

Keep the outcome event small and recoverable

This pattern provides

Record the outcome as an event you can query with SQL.
Stable fields for dashboards, alerts, and cross-event correlation.
Test events for checking success, failure, retries, and timeouts.

This pattern does not provide

An OTLP exporter, automatic collection pipeline, or replacement for detailed traces and diagnostic logs.
Exactly-once delivery merely because the payload contains an event ID.
Permission to collect raw provider payloads, user content, credentials, or regulated data.

Delivery and idempotency Batching and shutdown Troubleshoot ingestion

Example event schemas

Check what each event records, when to send it, and which field types it needs. Review the example payload and privacy checklist before using it in production.

Revenue operations9 fields