Guide · Stripe → Discord · Verified November 1, 2026

Stripe to Discord 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 Discord with its own retry schedule and delivery log.

Billing failures are urgent for a day and then routine. This pairing posts each failed or action-required invoice into a billing channel with the amount and the hosted invoice link, so the team sees the problem before the customer writes in.

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: failed payments only

{
  "allow": [
    {
      "field": "event.type",
      "op": "in",
      "value": ["invoice.payment_failed", "invoice.payment_action_required"]
    }
  ]
}

3. Configure the Discord destination

A Hooks Discord destination POSTs a message to a channel's incoming webhook URL; that URL carries the token, so it lives in a project secret. Content is plain text with optional embeds, and Discord answers 204 when the message is accepted.

Destination: Discord incoming webhook

{
  "webhookUrl": "{{secret.DISCORD_WEBHOOK_URL}}",
  "content": "Payment failed: {{event.subject.title}}",
  "embeds": "{\"title\":\"{{event.subject.title}}\",\"url\":\"{{event.subject.url}}\",\"color\":15158332}"
}

Secrets enter configs only as {{secret.NAME}} references; literal credentials are rejected. Full Discord 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

Discord rate-limits per webhook, not per message. A burst of failed invoices hits one webhook and comes back as 429 with retry_after in the body. Hooks retries on the destination's schedule and records the server hint, so nothing is dropped — but during an incident the channel can lag behind the delivery log, and the attempt timeline is the place to see the queue.

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.

Discord rate-limits per webhook, not per message

A burst of failed invoices hits one webhook and comes back as 429 with retry_after in the body. Hooks retries on the destination's schedule and records the server hint, so nothing is dropped — but during an incident the channel can lag behind the delivery log, and the attempt timeline is the place to see the queue.

More Stripe guides

Other ways into Discord