What is Fiscal402?
Fiscal402 is post-settlement fiscal infrastructure for autonomous commerce. It turns machine payments into durable, verifiable fiscal events.
What is x402?
x402 is a payment protocol. Fiscal402 currently supports x402 v2 exact as its first payment protocol. Fiscal402 observes settlement after payment; it does not issue HTTP 402 or move funds.
Does x402 handle VAT?
No. x402 is a payment protocol. It proves that a transfer settled. VAT classification needs seller establishment, buyer status, place of supply, and supply type. Fiscal402 sits after settlement and produces an EU VAT determination where the corridor is in the production engine.
Is a blockchain transaction an invoice?
No. A transaction hash is settlement evidence. An invoice is an accounting document with legal parties, tax treatment, and a currency of account. Fiscal402 can emit UBL 2.1 after settlement; the chain record is not that document.
Does Fiscal402 process payments?
No. Fiscal402 does not settle payments, route funds, split transfers, or act as an x402 facilitator.
Does Fiscal402 move funds?
No. Fiscal402 is non-custodial and post-settlement. It does not settle, route, split, or custody customer funds, and it is not an x402 facilitator.
Does Fiscal402 hold funds?
No. Fiscal402 is non-custodial. It does not custody customer funds and does not move money.
What happens after settlement?
After an x402 payment has already settled, Fiscal402 ingests settlement evidence, persists a fiscal event, produces an EU fiscal determination when applicable, emits a UBL 2.1 artifact, and issues a signed fiscal402.receipt.
What is fiscal402.receipt?
fiscal402.receipt/1.0.0 is the public protocol object. It binds settlement, determination, artifact hashes, a canonical payload hash, and an Ed25519 signature so another system can verify integrity.
Can another system verify a receipt?
Yes. Independent verification uses the receipt, the issuer JWKS, and optionally the bound UBL bytes. A source-only verifier lives in the public GitHub repository. It is not published to npm yet. VERIFIED means cryptographic integrity, not tax-authority acceptance.
Does Fiscal402 support EU VAT?
Yes. EU VAT is the first production jurisdiction engine. It classifies common EU digital-service VAT patterns. It is not tax advice and not a guarantee of tax-authority acceptance.
Can US merchants use Fiscal402 for EU sales?
Yes, for electronic services to attested EU customers. That corridor is in the production EU VAT path (non-Union OSS / Article 196). Fiscal402 does not determine US sales tax on the reverse corridor (NL → US is MANUAL_REVIEW for export and US tax).
Does Fiscal402 support US sales tax?
No native US sales-tax rate engine. US is a representable jurisdiction with a provider boundary. Determination is MANUAL_REVIEW until a verified provider is attached. No guessed flat rate.
Does Fiscal402 guarantee tax compliance?
No. Fiscal402 does not provide tax advice, file VAT returns, or guarantee legal compliance or tax-authority approval.
Which payment protocols are supported?
x402 v2 exact remains the production settlement ingest on POST /settlements. MPP is supported for evidence profile mpp.settlement/1. AP2 is supported authorization evidence; a mandate is not settlement.
Is Fiscal402 free?
Fiscal402 is free during beta at 0 bps. That is not permanently free. After beta the standard rate is 10 bps (0.1%) of fiscalized volume. High-throughput merchants and platforms may use custom contracted rates.
Is Fiscal402 open source?
The protocol specification, receipt schema, test vectors, and verifier source are public. The fiscal execution engine remains proprietary.
Does Fiscal402 support MPP or AP2?
MPP is supported for the mpp.settlement/1 evidence profile (transaction id, asset, integer amount, settledAt, FINAL|CONFIRMED). AP2 is supported as authorization / mandate evidence. A valid AP2 mandate is never proof that money moved. Production x402 ingest remains POST /settlements.
How can a merchant integrate?
POST settled x402 evidence to https://api.fiscal402.com/settlements. Retrieve the UBL artifact and fiscal402.receipt, and verify against JWKS. HTTP is the public integration path. Typed npm packages are not published yet. Production ingest still requires a merchant key.
Can another system implement a verifier without Fiscal402?
Yes. fiscal402.receipt/1.0.0, fiscal402.sorted-json/1, Ed25519 over the hex digest, and UBL SHA-256 of exact UTF-8 bytes are public. TypeScript and Python verifiers in the repository must agree on the frozen fixtures. Neither is published to npm or PyPI. VERIFIED is cryptographic integrity, not tax-authority acceptance.
Can Fiscal402 post to my ERP?
Fiscal402 emits a generic EUR journal (JSON and CSV) from a verified receipt. NetSuite, SAP, Xero, Exact, and QuickBooks adapters are not implemented. Fiscal402 does not file VAT returns.
What is fiscal close in Fiscal402?
A period can move OPEN → READY_FOR_REVIEW → CLOSED only when determinations, artifacts, verified receipts, and accounting exports exist and reconciliation has no blocking exceptions. That is close readiness, not tax filing.