Voucher · September 2026 · sample
402B-brackwater-2026-000001
Acme GmbH, Berlin · DE311234567
Brackwater Data Level 1
Reverse charge, § 13b UStG. Self-made voucher, not an invoice of the seller. Every receipt links to its transaction on Base.
An agent that pays over x402 leaves a USDC transfer to a wallet address. Your accountant cannot book that. 402lounge reads the chain, puts a name and a description on every payment, and turns a month of them into one document per seller. Every receipt links to its transaction on Base.
Receipts · Oct 30 · 1,284 todayexample
Voucher · September 2026 · sample
402B-brackwater-2026-000001
Reverse charge, § 13b UStG. Self-made voucher, not an invoice of the seller. Every receipt links to its transaction on Base.
One line in the agent's MCP client. From there it signs up on its own, with its wallet, and asks you nothing.
Run this once in a terminal. Claude Code keeps the server for every session.
claude mcp add --transport http 402lounge https://mcp.402lounge.com/mcp
Your agents keep paying as they do today, from their own wallets, to the sellers they choose. Here is what happens after.
A few cents in USDC on Base for a search, a page, a dataset. We read the transfer from the chain once it is confirmed and write a receipt: amount, time, block, hash.
The payTo address is looked up in the register. A verified seller appears with its name and what it sells, in its own words from its 402 answer. An unknown wallet stays marked as unknown, so you see what cannot be booked.
On the 1st, each finished month becomes one numbered voucher per seller: lines per endpoint, the EUR value at the day's ECB rate, the tax note your accountant needs. PDF and JSON, hashed, never changed afterwards. Part of Books, from €29 a month.
Every wallet, every seller, every month. The dashboard shows what was paid, to whom, and what still needs a human, and the same answers come back over MCP and REST.
Overview
October 2026 · example · chain read 4 minutes ago
Where the money went
Needs a human
418 payments to 2 unknown wallets (45.50 USDC). No seller, no voucher line.
VAT ID not confirmed yet. VIES did not answer at 03:15, check it again under Company.
Wallet 0x9b2e…41a0 of Otto paid 1,140 times but is not confirmed.
Seller from the register, description from the seller's catalogue or the agent's own report, EUR value at the day's ECB rate. Unknown wallets stay visible as unknown.
Unconfirmed wallets, unknown sellers, a VAT ID VIES has not confirmed yet. The dashboard says what to do, and nothing waits silently.
Buyers and sellers climb the same four levels. A level says what we have checked about a company, and therefore what a document can carry. Nothing is required up front. Every agent account starts on level 1.
Every entry is read from the seller's own 402 answer. We show what a machine can verify, and nothing a seller wrote about itself.
List your service and prove your wallet once. From then on every payment to it carries your name and your description on the buyer's side. Free on levels 0 and 1, the company check for level 2 costs €10 a year.
One URL and one wallet
Give us the URL of one paid endpoint and the wallet it pays to. We read the rest from your 402 answer. The checks start the same night.
Prove the wallet, climb to level 1
A signature from the wallet, or 0.01 USDC sent from it. From then on buyers see your name, and wallet policies can allow you by level.
Level 3: we invoice for you
With a signed mandate we issue one invoice per buyer and month in your name, numbered, archived, in the EU e-invoice format. Part of Books.
Tell us how many agents you run and what your accountant needs. A person answers, usually the same day.