Bot intelligence record
Stripe
Usually allowStripe is a webhook callback used for webhook delivery, payment notifications, service callbacks; it appears in server logs as `Stripe/1.0`.
User-Agent Pattern
StripeStripe/1.0
User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.
Robots.txt Snippet
Click snippet to copyUser-agent: Stripe/1.0
Disallow: /Click the snippet to copy it, or highlight the text manually.
Handling Guidance
NoThis bot is usually safe to allow when the request source is verified and the traffic matches your site policy.
Stripe is used for webhook delivery, payment notifications, service callbacks, and server-to-server integration events.
Record Details
Structured data- Operator
- Stripe
- Family
- Stripe
- Type
- Webhook
- Purpose
- Webhook
- Identity type
- Verified Bot
- Confidence
- Medium
- Last verified
- 2026-06-23
- Last checked
- 2026-06-23
- Source type
- Documented
- Verification
- Verify Stripe by matching `Stripe/1.0` to a public crawler reference or source-linked documentation, then checking reverse DNS, IP ownership, request behavior, and crawl consistency.
- Spoofing risk
- Stripe has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
Notes
- Stripe is a webhook callback used for webhook delivery, payment notifications, service callbacks, and server-to-server integration events.
- Its primary user-agent pattern is
Stripe/1.0; a representative HTTP user-agent isStripe/1.0 (+https://stripe.com/docs/webhooks). - Stripe is verified with Medium confidence. The identity type is Verified Bot, and the evidence basis is a public crawler reference or source-linked documentation.
- Stripe is marked as not reliably governed by robots.txt directives; use server-side rules if the traffic should be restricted.
- Stripe can usually be allowed after confirming the source and monitoring request volume.
Evidence and Source
- Verify Stripe by matching `Stripe/1.0` to a public crawler reference or source-linked documentation, then checking reverse DNS, IP ownership, request behavior, and crawl consistency.
- Stripe traffic is primarily detected by the `Stripe/1.0` user-agent pattern; a representative HTTP user-agent is `Stripe/1.0 (+https://stripe.com/docs/webhooks)`. Compare source IPs, reverse DNS, request paths, and crawl cadence before trusting the traffic.
- Stripe is used for webhook delivery, payment notifications, service callbacks, and server-to-server integration events.
- Stripe has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
Monitor This Bot In Edge
Botcrawl EdgeUse Botcrawl Edge to see matching traffic, identify related datacenter activity, and create allow, block, rate-limit, or log rules across connected sites.