What Stripe Webhooks does
Stripe Webhooks are HTTPS POST requests that Stripe sends to an endpoint your application registers, delivering event notifications as JSON payloads so your integration can react to asynchronous events such as a bank confirming a payment, a customer disputing a charge, or a recurring payment succeeding. Events come in snapshot form (full API object state) or thin form (minimal data you expand with a follow-up call), and each request carries a Stripe-Signature header your server can verify with an endpoint secret. Your endpoint should return a 2xx status quickly; in live mode Stripe retries failed deliveries with exponential backoff for up to three days.
How to identify Stripe Webhooks
Temso identifies Stripe Webhookstraffic by matching the request's User-Agent header against this pattern. User-agent strings can be spoofed, so treat a match as an indication, not proof.
Stripe\/1\.0Stripe Webhooks FAQ
What is Stripe Webhooks?
Stripe Webhooks is Stripe's event delivery system: it sends JSON event payloads over HTTPS POST to an endpoint you configure, notifying your application in real time about events like payment_intent.succeeded or customer.subscription.created.
Can I block Stripe Webhooks with robots.txt?
No. Webhooks are server-to-server POST deliveries to an endpoint you explicitly registered with Stripe, not web crawling, so robots.txt does not apply. If you no longer want the traffic, remove or disable the webhook endpoint in Stripe; you can also restrict your firewall to Stripe's published sending IPs.
About Operational Bots
Monitoring, security scanning, link previews, webhooks, and feed fetchers: the utility traffic that keeps integrations and shared links working.
Most of this traffic is service-critical or user-triggered. Webhooks and previews don't follow robots.txt, and blocking them tends to break things you rely on.
