x402 is a machine-payment protocol: HTTP 402, payment requirements, settle, retry. Fiscal402 is not x402. Fiscal402 sits after the transfer exists and produces a fiscal event other systems can store, post, and independently verify.
- x402 v2 exact settlement
- ↓
- Fiscal402 (post-settlement)
- ↓
- EU VAT determination
- ↓
- UBL 2.1
- ↓
- fiscal402.receipt/1.0.0
What each layer owns
| Layer | Proves | Does not prove |
|---|---|---|
| x402 | Payment requirements and settlement of an exact transfer | VAT, invoice, legal identity |
| Chain / USDC transfer | Value moved on a network | Place of supply, buyer status |
| Fiscal402 | A signed fiscal event bound to that settlement | Tax-authority acceptance or a filed return |
Production vs architecture
| Capability | Status |
|---|---|
| x402 v2 exact ingest | PRODUCTION |
| EU VAT determination | PRODUCTION |
| UBL 2.1 / EN 16931 | PRODUCTION |
| fiscal402.receipt/1.0.0 | PRODUCTION (frozen) |
| MPP mpp.settlement/1 evidence | SUPPORTED (HTTP ingest remains POST /settlements) |
| AP2 | SUPPORTED as authorization evidence; a mandate is not settlement |
| UK VAT | EXPERIMENTAL (GB→GB digital). No receipt v1 |
| US sales tax / Canada GST | MANUAL_REVIEW. No native rate table |
Ecosystem position
Facilitators, agent wallets, and x402 resource servers remain responsible for payment. Fiscal402 attaches after settlement. There is no official Coinbase, Stripe, or Cloudflare partnership to claim. A listing in an x402 directory would describe a fiscal observer, not a facilitator.