Skip to content

Use case

AI agent payments

Give agent-to-API commerce a fiscal event after the machine payment, not only a transaction hash.

Problem

Agents can pay for APIs, data and compute in seconds. Downstream accounting, audit and tax workflows still need a fiscal record the agent did not produce.

Input

Settlement evidence from an x402 v2 exact transfer initiated by an agent or on behalf of a merchant, with attested buyer location where required.

Fiscal402 processing

Fiscal402 sits after settlement. It classifies the EU fiscal event when the facts support it, writes a ledger row, and signs a receipt. It does not custody the agent’s funds.

Output

A machine-readable fiscal402.receipt the agent, merchant, or buyer systems can store, forward, and independently verify.

Limitations

Integration path

Discover capabilities at https://api.fiscal402.com/.well-known/fiscal402.json. Evaluate with POST /v1/compliance/evaluate. Ingest production events with POST /settlements.

Last updated 11 September 2026