Bot intelligence record
2checkout
Usually allowUse the 2checkout identifier to separate 2checkout webhook or service callback traffic from normal visitor requests in server logs.
- Operator
- 2checkout
- Family
- 2checkout
- Type
- Webhook
- Source type
- Verified Directory
- Last checked
- 2026-05-20
User-Agent Pattern
2checkout2checkout
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: 2checkout 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.
Webhook notifications, callbacks, payment events, or service-to-service integration requests.
Record Details
Structured data- Operator
- 2checkout
- Family
- 2checkout
- Type
- Webhook
- Purpose
- Webhook
- Identity type
- Verified Bot
- Confidence
- Medium
- Last verified
- 2026-04-01
- Last checked
- 2026-05-20
- Source type
- Verified Directory
- Verification
- Validate the identifying user-agent or signature against the operator documentation before creating hard allow rules.
- Spoofing risk
- User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.
Notes
2checkout is listed in the Botcrawl directory as a webhook callback service from 2checkout. The primary identifier for log review is 2checkout.
Identification
- User-agent pattern:
2checkout - Family: 2checkout
- Type: Webhook
- Kind: Webhook
Common use
Webhook notifications, callbacks, payment events, or service-to-service integration requests.
Verification and handling
Confirm the user-agent against server logs and use published operator documentation, IP ranges, reverse DNS, or other trust signals when available.
Directory guidance marks the risk level as Safe and the blocking decision as No. Do not rely on the user-agent string alone because user-agent strings can be copied or spoofed.
Robots.txt handling: No.
Evidence and Source
- Validate the identifying user-agent or signature against the operator documentation before creating hard allow rules.
- Match `2checkout` as a case-insensitive substring in HTTP user-agent logs. Do not treat a user-agent match alone as proof of identity for allow-listing.
- Webhook notifications, callbacks, payment events, or service-to-service integration requests.
- User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.
https://knowledgecenter.2checkout.com/API-Integration/Webhooks/
Monitor This Bot In Edge
Botcrawl EdgeUse Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.