Bot intelligence record
Trustly
Usually allowTrustly is a webhook callback from Trustly Group AB used for webhook delivery, payment notifications, service callbacks; it appears in server logs as `Trustly`.
- Operator
- Trustly Group AB
- Family
- Trustly Group AB
- Type
- Webhook
- Source type
- Documented
- Last checked
- 2026-06-23
User-Agent Pattern
Trustly Group ABTrustly
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: Trustly
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.
Trustly is used for webhook delivery, payment notifications, service callbacks, and server-to-server integration events.
Record Details
Structured data- Operator
- Trustly Group AB
- Family
- Trustly Group AB
- Type
- Webhook
- Purpose
- Webhook
- Identity type
- Verified Bot
- Confidence
- Medium
- Last verified
- 2026-04-01
- Last checked
- 2026-06-23
- Source type
- Documented
- Verification
- Verify Trustly by matching `Trustly` to Trustly Group AB evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
- Spoofing risk
- Trustly has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
Notes
- Trustly is a webhook callback from Trustly Group AB used for webhook delivery, payment notifications, service callbacks, and server-to-server integration events.
- Its primary user-agent pattern is
Trustly; related patterns includeTrustly/; a representative HTTP user-agent isTrustly/1. - Trustly is verified with Medium confidence. The identity type is Verified Bot, and the evidence basis is documented crawler-pattern evidence.
- Trustly does not have confirmed robots.txt behavior in the available public evidence.
- Trustly can usually be allowed after confirming the source and monitoring request volume.
Evidence and Source
- Verify Trustly by matching `Trustly` to Trustly Group AB evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
- Trustly traffic is primarily detected by the `Trustly` user-agent pattern; related patterns include `Trustly/`; a representative HTTP user-agent is `Trustly/1`. Compare source IPs, reverse DNS, request paths, and crawl cadence with Trustly Group AB infrastructure before trusting the traffic.
- Trustly is used for webhook delivery, payment notifications, service callbacks, and server-to-server integration events.
- Trustly 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.