Problem
x402 settlement proves that USDC moved. It does not produce an EU VAT treatment, an accounting invoice, or a verifiable fiscal receipt.
Input
A settled x402 v2 exact payment (USDC on Base eip155:8453 or Ethereum eip155:1), plus commercial context such as buyer country and optional buyer VAT ID.
Fiscal402 processing
Fiscal402 observes the settlement. It does not move funds. The current EU VAT engine classifies common digital-service patterns, records VIES when a VAT ID is supplied, values USDC to EUR at settled_at, and binds a UBL 2.1 artifact.
Output
A fiscal record, UBL 2.1 XML, and a signed fiscal402.receipt/1.0.0 that another system can verify against JWKS.
Limitations
- EU VAT is the production V1 path, including non-EU sellers of electronic services to attested EU customers. UK VAT is EXPERIMENTAL for GB→GB digital. US and Canada are MANUAL_REVIEW provider boundaries, not rate engines.
- Digital-service patterns currently in production. Goods and special place-of-supply services are not a live claim.
- Not tax advice and not tax-authority acceptance.
Integration path
POST https://api.fiscal402.com/settlements after the x402 payment has settled, then GET the receipt and UBL. See /docs/getting-started.