Does Payhawk Invoice Fetching Agent respect robots.txt?

Its robots behavior is not confirmed in the bot metadata, and it has no stable token for a targeted rule. Cloudflare's record marks the agent as not following robots.txt.

Does this agent affect AI search or model training?

No. Its documented purpose is to collect an account holder's invoice for an expense workflow. It neither indexes the public web for AI answers nor gathers training content.

What happens if the agent cannot retrieve an invoice?

Payhawk notifies the user and asks for a manual upload. The same fallback applies when the invoice is unavailable through the supplier account.

Payhawk Invoice Fetching Agent Bot Guide

Q: How can I verify Payhawk Invoice Fetching Agent is genuine?

Verify its Web Bot Auth HTTP message signature with Payhawk's directory at `https://external-bot.payhawk.com/.well-known/http-message-signatures-directory`. No verified IP range or stable user-agent token is listed for it.

What is Payhawk Invoice Fetching Agent?

Payhawk Invoice Fetching Agent is the browser automation behind Agent Fetch in Payhawk's Financial Controller AI Agent. Its job is specific: retrieve a receipt or invoice from a supplier website and attach it to the matching expense in Payhawk.

The workflow begins when online fetching is enabled and a card expense is missing a document. Payhawk attempts the retrieval before asking the employee to upload the file manually. On a first visit or after a session expires, the employee receives a secure login link for the supplier portal. If the site presents a CAPTCHA, the agent pauses until the employee completes it.

Payhawk says the agent limits its visit to the account's payment history and invoice area. It compares amount and date to choose a matching document, attaches the result to the expense, and notifies the user. When it cannot fetch or match a document, the user returns to the manual upload path.

For a supplier, this traffic looks more like an automated signed-in browser session than a crawler. It may navigate an account page and download a document after the account holder has authorized access. Blocking the request can interrupt invoice collection, but it does not make the supplier less visible in an answer engine.

This agent has no role in AI search indexing and its documented workflow does not collect pages for model training. The AI label refers to Payhawk's finance product and matching workflow, not to a system that discovers public web content for answers.

There is no stable user-agent token for this agent. Cloudflare classifies it as an agent, marks it as not following robots.txt, and lists no user-agent pattern. It links the Payhawk product page above and publishes a Web Bot Auth signature directory at https://external-bot.payhawk.com/.well-known/http-message-signatures-directory. That signed identity is the available control point.

Relevant for AI search

Is Payhawk Invoice Fetching Agent relevant for AI search?

Yes. Payhawk Invoice Fetching Agent collects pages for an AI product, so what it can crawl influences how AI systems describe your brand.

Payhawk Invoice Fetching Agent crawls and indexes pages so the AI search or assistant behind it can retrieve them at answer time. A page it has never fetched cannot be quoted, summarized, or linked in that product's answers, so most sites keep it allowed to stay citable. Blocking it removes your pages from that AI surface and hands those citations to competitors.

How to handle Payhawk Invoice Fetching Agent

Do not create a guessed robots.txt group for Payhawk Invoice Fetching Agent. It has no documented token, and its robots behavior is not a reliable access control.

Before Payhawk fetches an invoice, authenticate the agent by checking its Web Bot Auth signature against the keys at https://external-bot.payhawk.com/.well-known/http-message-signatures-directory. Then apply the same login, authorization, download limits, and abuse checks you use for a person accessing invoices. A valid agent signature identifies Payhawk's automation; it should not bypass the supplier account's own controls. If automated invoice retrieval is not permitted, enforce that decision at the edge or in the application.

Examples

A Payhawk user authorizes Agent Fetch for a software vendor. When the next card charge lacks an invoice, the agent signs in, finds the document by date and amount, and attaches it to the expense.
A supplier receives a request that claims to be Payhawk but has no valid Web Bot Auth signature. Its edge policy rejects the request instead of trusting an arbitrary browser header.

Frequently asked questions about Payhawk Invoice Fetching Agent

Learn about AI visibility monitoring and how Promptwatch helps your brand succeed in AI search.

It visits after Agent Fetch has been enabled and Payhawk finds a card expense without a receipt or invoice. The user may first need to authenticate with the supplier.

Related bots

Amazon Kendra

Amazon Kendra is a managed information retrieval and intelligent search service that uses natural language processing and advanced deep learning model.

AI Assistant