Stripe Webhook Telemetry

Implementation evidence

Stripe Webhook Telemetry: from boundary to verified row

Use Stripe Webhook Telemetry at a controlled application boundary, keep the event contract small, and verify a known outcome before building aggregate views.

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

Before you start

Prerequisites and boundaries

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

1Prepare one reusable server-side delivery client with bounded network behavior.
2Add the outcome event at the success, failure, retry, or timeout boundary.
3Send controlled fixtures 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 contract

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

Implementation checkpoints

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

Production boundary

Keep the outcome event small and recoverable

This pattern provides

A bounded, SQL-ready outcome beside the upstream workflow.
Stable fields for dashboards, alerts, and cross-event correlation.
A fixture-driven path for validating success, failure, retry, and timeout behavior.

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

Event schema starting points

Review the row grain, emit boundary, required types, privacy classes, example payload, and validation checklist before adapting a query or snippet to production.

Revenue operations9 fields