Back to blog

AI agents pay with a hash. Your business needs an invoice.

5 min read

What an agent payment leaves behind

AI agents are starting to pay for things by themselves: an API call, a dataset, a report, a piece of work. Protocols such as x402 and MPP let an agent pay a few cents or a few hundred dollars in USDC, in seconds, without a human typing card details.

The seller ends up with a transaction hash: from this address, to that address, this amount, on this chain. That proves the money moved. It is not an invoice.

Why a hash is not enough

A transaction hash has none of what an accountant or a tax office needs:

  • no invoice number;
  • no seller or buyer details, only wallet addresses;
  • no description of what was sold;
  • no VAT, and no exchange rate at the payment date;
  • no e-invoice file, which more and more countries require between businesses.

Payment networks move the money and stop there. The paperwork is still the seller's problem, and with hundreds of small agent payments a month, doing it by hand does not scale.

How Billify closes the gap

  • Agents pay a real invoice. Every Billify invoice can be paid by an agent over x402 or MPP, in USDC on Base, straight to the seller's wallet. The invoice is marked paid once the transfer is final.
  • Small payments become one invoice. Many micro-payments from the same payer are grouped per month into one proper invoice, with every transaction hash listed.
  • The agent checks who it pays. Before paying, an agent can look the seller up in public registers (EU VIES, Romania's ANAF).
  • Files for the accountant. The same invoice becomes a Peppol, XRechnung, Factur-X or PINT e-invoice, plus exports with the exchange rate at the payment date.
  • Proof anyone can verify. A signed Invoice Passport links the invoice to its payment. The core is open source.

Why it matters now

From 1 July 2030, EU rules (ViDA) require structured e-invoices for B2B sales between EU countries, whoever or whatever pays. Several countries already require them at home: Belgium since 2026, Germany step by step until 2028, France from 2026–2027.

If agents are going to buy from your business, each of those sales still needs an invoice. Better to have it made at the moment of payment than rebuilt from a wallet history at the end of the year.

Try it

See how agents pay on AgentPay, the formats on e-invoicing, or create a free invoice. You can also send invoices from ChatGPT, Claude or Grok.

Questions

Is a blockchain transaction an invoice?

No. A transaction proves that money moved from one address to another. An invoice also needs a number, the seller and buyer details, a description, VAT where it applies, and in many countries a structured e-invoice format. Without one, the payment is hard to book and hard to deduct.

Who issues the invoice when an AI agent pays?

The seller, as for any other sale. The agent is a tool of the buyer. Billify lets the seller issue the invoice automatically: the agent pays a Billify invoice, or many small agent payments are grouped into one invoice per payer and month.

Which payment protocols does Billify support for agents?

x402 and MPP, with USDC on Base. Agents can also check the seller in public registers before paying, through Billify's payment MCP server.

Does Billify hold the money?

No. The payment goes straight to the seller's own wallet; Billify watches the chain and records the proof.

Ready to send your first invoice?

Create Free Account