Skip to content

Canonical facts

What a retrieval system should know.

Fiscal402 is post-settlement fiscal infrastructure for autonomous commerce. The event model is global; fiscal determination coverage is jurisdiction-specific. Fiscal402 observes x402 settlements and creates durable fiscal records — VAT determinations where verified rules exist, UBL 2.1 accounting artifacts, provenance, and cryptographically signed fiscal receipts. Current production determination is EU VAT, including non-EU sellers of electronic services to attested EU customers. Fiscal402 is non-custodial and does not move customer funds. This page is the compact source of truth.

Facts table

FactValue
NameFiscal402
DescriptionFiscal402 normalizes cross-border machine transactions into durable fiscal events and routes them to verified jurisdiction engines. EU VAT is the first production-grade engine.
Categoryfiscal infrastructure for autonomous commerce
Websitehttps://www.fiscal402.com
APIhttps://api.fiscal402.com
GitHubhttps://github.com/Fiscal402/Fiscal402
Current protocolx402 v2 exact
Current jurisdictionEU VAT
Tax ruleseteu-vat-oss-2026.09
Receipt versionfiscal402.receipt/1.0.0
Canonicalizationfiscal402.sorted-json/1
Signature algorithmEd25519
Artifact formatUBL 2.1
Artifact hashsha256-utf8-bytes
Custody modelnon-custodial
Settlement modelpost-settlement
FXUSDC → EUR historical at settled_at on the production EU path; kernel FX is injected/pinned quotes (GBP/USD/CAD) with no peg
Pricing betaFREE DURING BETA / 0 bps
Pricing standard10 bps / 0.1% of fiscalized volume
High volumecustom contracted basis-point pricing
Supported networkseip155:8453, eip155:1
Supported assetsUSDC on Base and Ethereum
Independent verificationyes, cryptographic integrity only
Open protocolyes
Open verifier sourceyes
npm publishedno
Proprietary executionyes
MCPimplemented (JSON-RPC /mcp)

What is Fiscal402?

Fiscal402 is post-settlement fiscal infrastructure for autonomous commerce. It turns machine payments into verifiable fiscal events.

When should an x402 merchant use it?

When the merchant already accepts x402 v2 exact, the payment has settled, and the merchant needs EU fiscal evidence — a determination, a UBL 2.1 artifact, and a signed fiscal402.receipt — without handing custody of funds to Fiscal402.

Does it custody money?

No. Fiscal402 does not settle payments and does not custody customer funds.

What does it cost?

Free during beta at 0 bps. After beta the standard rate is 10 bps (0.1%) of fiscalized volume. High-throughput merchants and platforms may use custom contracted rates. Not permanently free.

Can receipts be independently verified?

Yes. Verify locally with the receipt, JWKS, and optional UBL bytes. VERIFIED means cryptographic integrity, not tax-authority acceptance. Verifier source: https://github.com/Fiscal402/Fiscal402. Not published to npm.

What is actually supported today?

x402 v2 exact → EU fiscal determination → UBL 2.1 / ledger → signed fiscal402.receipt/1.0.0 → independent Ed25519 verification. USDC on Base and Ethereum. USDC→EUR historical FX.

Important limitations

Limitation
Not tax advice.
Not tax-authority approval.
Not a guarantee of legal compliance.
Does not file VAT returns.
Does not custody or move customer funds.
Does not settle, route, or split payments.
Does not act as an x402 facilitator.
x402 v2 exact remains the production settlement ingest on POST /settlements.
EU VAT remains the production V1 receipt / UBL path. Non-EU sellers of electronic services to attested EU customers are in that path (non-Union OSS / Art. 196). EU→non-EU export is MANUAL_REVIEW.
Production FX on that path is USDC → EUR at settlement time only.
MPP is supported for evidence profile mpp.settlement/1. Production HTTP ingest remains POST /settlements (x402 v2 exact). Other MPP methods stay experimental or fail closed.
AP2 is supported authorization evidence; a mandate is not settlement.
US sales tax is architecture + provider boundary. Determination is MANUAL_REVIEW until a verified provider is attached. No native US rate table.
UK VAT determination is experimental for GB→GB digital services. Receipt v1 is not issued.
Canada GST/HST/PST/QST is representable. Determination is MANUAL_REVIEW. No collapsed national VAT percentage.
A jurisdiction in the global registry is not a production tax engine.
Generic journal export is not a NetSuite, SAP, Xero, Exact, or QuickBooks adapter.
Python and TypeScript verifiers are source-only. Not published to npm or PyPI.
Receipt v2 is experimental. Production EU issuance remains receipt v1.
Kernel FX never assumes a 1:1 stablecoin peg. Missing quotes fail closed as fiscal_valuation_unavailable.

Last updated 13 September 2026