Guide · Stripe → Telegram · Verified November 1, 2026

Stripe to Telegram webhook guide

Short answer: One Stripe endpoint verifies each delivery, a destination filter keeps the events in this guide, and every match is delivered to Telegram with its own retry schedule and delivery log.

A small team wants a ping in Telegram when someone buys, without opening the Stripe dashboard. This pairing sends each completed checkout into a sales chat with the amount and customer reference, and the delivery log keeps the Stripe event that produced it.

At a glance

1. Configure the Stripe webhook

  1. In the Stripe Dashboard, open Developers → Webhooks → Add endpoint.
  2. Paste the endpoint's ingestion URL and select the events you need (invoice, checkout, subscription).
  3. Copy the endpoint's Signing secret (`whsec_...`) into the Hooks endpoint secret.
  4. Send a test event from the Stripe Dashboard and confirm it in the delivery log.

HMAC-SHA256 over <t>.<raw body>; any matching v1 signature passes. Five minutes between t and the current time.

2. Filter to the events that matter

Filters run per destination before rendering, so a non-matching event is stored with no delivery and no agent call. The rules below are the difference between a useful pairing and a noisy one.

Filter: completed checkouts

{
  "allow": [
    { "field": "event.type", "op": "equals", "value": "checkout_session.completed" }
  ]
}

3. Configure the Telegram destination

A Hooks Telegram destination calls sendMessage with your bot token and a chat id; the token stays in a project secret. The message text renders from the event, and Telegram's ok flag decides success even when the HTTP status is 200.

Destination: Telegram bot

{
  "token": "{{secret.TELEGRAM_BOT_TOKEN}}",
  "chatId": "-1009876543210",
  "text": "New checkout: {{event.subject.title}}\n{{event.subject.url}}",
  "parseMode": "HTML"
}

Secrets enter configs only as {{secret.NAME}} references; literal credentials are rejected. Full Telegram target guide

4. Verify the delivery and its retries

Send one real event from the source, then open Deliveries. A 2xx from the target means accepted, not finished. 408, 425, 429 and 5xx retry with backoff honoring Retry-After; other 4xx fail permanently with a named code. The rendered request is stored per attempt, so a bad field path is visible without re-sending.

Hooks delivery detail: attempt timeline, request payload, and the destination response for one delivery
Delivery detail: the attempt timeline, the rendered request the target received, and its response — the same record an event keeps for every destination.

The pitfall this pairing hits

HTML parse mode does not escape the payload. Hooks renders the template and sends it as-is. A customer name or product title containing <, > or & makes Telegram reject the message with can't parse entities, and the failure arrives as HTTP 200 with ok: false. Drop parseMode for plain text, or escape the fields in the template.

Frequently asked questions

Do I need one endpoint per source or one per destination?

One endpoint per source. Each destination under that endpoint carries its own filter, template, retry schedule, and delivery log, so the same event can feed several targets without duplicate ingress URLs.

What happens while the target is down?

Retryable failures back off and retry within the destination's window; permanent 4xx failures stop immediately. Either way, the original event stays stored, so after fixing the target you replay the event instead of asking the source to send it again.

HTML parse mode does not escape the payload

Hooks renders the template and sends it as-is. A customer name or product title containing <, > or & makes Telegram reject the message with can't parse entities, and the failure arrives as HTTP 200 with ok: false. Drop parseMode for plain text, or escape the fields in the template.

More Stripe guides

Other ways into Telegram