Bot intelligence record
Payhawk Invoice Fetching Agent
Review firstPayhawk Invoice Fetching Agent is a signed-agent identity used to recognize Payhawk automated browser or AI-agent traffic in Botcrawl logs. The importable Botcrawl identifier is payhawk-invoice-fetching-bot.
- Operator
- Payhawk
- Type
- Ai
- Source type
- Official
- Last checked
- 2026-06-22
User-Agent Pattern
Payhawkpayhawk-invoice-fetching-bot
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: payhawk-invoice-fetching-bot
Disallow: /
Click the snippet to copy it, or highlight the text manually.
Handling Guidance
DependsUse this record as bot intelligence, then verify the request source and behavior before allowing, blocking, or rate limiting.
AI invoice and receipt retrieval from supplier websites after user authorization.
Record Details
Structured data- Operator
- Payhawk
- Type
- Ai
- Purpose
- AI Invoice And Receipt Retrieval From Supplier Websites After User Authorization.
- Identity type
- Signed Agent
- Confidence
- High
- Last verified
- 2026-06-22
- Last checked
- 2026-06-22
- Source type
- Official
- Verification
- HTTP Message Signatures / Web Bot Auth; verify Signature, Signature-Input, and Signature-Agent headers when available.
- Spoofing risk
- Medium when matched by identifier only; lower after signed-agent verification succeeds.
Notes
Payhawk Invoice Fetching Agent is a Botcrawl signed-agent identity for automated traffic associated with Payhawk. The importable Botcrawl identifier is payhawk-invoice-fetching-bot.
Identification
- Botcrawl identifier:
payhawk-invoice-fetching-bot - Operator: Payhawk
- Family: Payhawk Invoice Fetching Agent
- Type: AI agent / browser automation
- Identity model: signed-agent identity
- Supporting identifiers:
payhawk-invoice-fetching-bot
Common use
AI invoice and receipt retrieval from supplier websites after user authorization.
Verification and handling
This identity is best handled as a signed-agent or managed browser identity, not as a traditional fixed HTTP user-agent crawler. For Edge enforcement, match the Botcrawl identifier and verify supporting request signals when available, including Signature, Signature-Input, Signature-Agent, managed bot identifiers, request headers, operator documentation, IP ownership, and observed behavior. Do not treat the identifier alone as cryptographic proof because plain identifiers can be copied.
Botcrawl marks this as normal-risk traffic by default. Monitor or allow when it is expected, rate-limit if it creates load, and block when the activity is unwanted or unverifiable.
Reference: operator documentation.
Evidence and Source
- HTTP Message Signatures / Web Bot Auth; verify Signature, Signature-Input, and Signature-Agent headers when available.
- Importable Botcrawl signed-agent identity. This row intentionally uses the Botcrawl identifier in bot_user_agent because the current importer requires a non-empty identifier; it is not a claim that the agent always sends a fixed traditional HTTP User-Agent string.
- AI invoice and receipt retrieval from supplier websites after user authorization.
- Medium when matched by identifier only; lower after signed-agent verification succeeds.
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.
