Overview
ChargeBee is a webhook callback used for webhook delivery, payment notifications, service callbacks, and server-to-server integration events.
Its primary user-agent pattern is ChargeBee.
ChargeBee is Unverified at the identity-evidence level. The listed identity remains useful for detection, but this record does not currently contain authoritative evidence sufficient to authenticate the identity claim.
Robots.txt behavior is not currently confirmed.
ChargeBee can usually be allowed after confirming the source and monitoring request volume.
Identity
- User-Agent
ChargeBee- HTTP Agent Examples
ChargeBee- Robots.txt Token
ChargeBee- Identity Type
- Observed
- Evidence Method
- Treat `ChargeBee` as an identity signal only. Confirm it with current operator documentation, cryptographic verification, forward-confirmed reverse DNS, source-network ownership, or other authoritative evidence before trusting the claimed identity.
Classification
- Type
- Webhook
- Kind
- Webhook
- Family
- ChargeBee
- Purpose
- webhook
Behavior and handling
- Common Use
- ChargeBee is used for webhook delivery, payment notifications, service callbacks, and server-to-server integration events.
- Detection Notes
- ChargeBee traffic is primarily detected by the `ChargeBee` user-agent pattern. Compare source IPs, reverse DNS, request paths, and crawl cadence before trusting the traffic.
- Respects robots.txt
- Unknown
- Spoofing Risk
- ChargeBee has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
- Risk
- Safe
- Recommended Handling
- No
Rules and controls
- Robots.txt Snippet
# robots.txt behavior is unconfirmed. Do not rely on this rule without verification.