x402 VAT is a search phrase for a real gap. x402 moves USDC. European VAT is a tax on a supply, not on a hash. The two layers do not substitute for each other.
What x402 proves
- A resource required payment (HTTP 402 + requirements).
- An exact transfer of an amount of an asset to a payTo address settled.
- The client can retry with proof and receive the resource.
What VAT requires that x402 does not carry
- Seller legal establishment — not a wallet.
- Buyer country and, for B2B, taxable-person status.
- Place of supply for the service (for electronic services, typically the customer).
- B2B versus B2C, and whether a VAT ID was confirmed (VIES).
- A document in a currency of account (EUR for the production path).
Where Fiscal402 sits
Fiscal402 is post-settlement. After x402 has already settled, a merchant or agent posts settlement evidence plus commercial context. Fiscal402 persists a fiscal event, runs the EU VAT engine where the corridor is in scope, emits UBL 2.1, and signs fiscal402.receipt/1.0.0.
- x402 settlement
- ↓
- Fiscal402
- ↓
- EU VAT determination
- ↓
- UBL 2.1
- ↓
- fiscal402.receipt
Identity split
Payer and payTo wallets are payment identity. They are not legal persons, VAT registrations, or establishments. Buyer country is merchant-attested (consumerCountry), not inferred from IP or the chain. Fiscal402 records IP/wallet signals as provenance only.
Place of supply, B2B/B2C, VIES
For B2C electronic services the production engine uses destination member-state standard rates (OSS). For intra-EU B2B with an accepted VAT ID it records reverse charge. VIES is stored as a status and a hash of the VAT ID — not the raw number. Unconfirmed IDs are not silently reverse-charged.
What you get
- An EU VAT determination with regime, rate, and ruleset version.
- A UBL 2.1 / EN 16931 invoice in EUR, bound by SHA-256 of exact bytes.
- A signed receipt another system can verify against JWKS.
Ingest (after settlement)
POST /settlements
POST https://api.fiscal402.com/settlements
Content-Type: application/json
X-Fiscal402-Key: $FISCAL402_API_KEY
Idempotency-Key: acme-nl-de-1
{
"amountUsdc": "1.00",
"txHash": "0xYOUR_SETTLED_TX",
"timestamp": "2026-09-10T12:00:00.000Z",
"payerWallet": "0xPAYER",
"receiverWallet": "0xPAY_TO",
"network": "eip155:1",
"asset": "USDC",
"scheme": "exact",
"consumerCountry": "DE",
"consumerName": "Buyer GmbH"
}FAQ
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 — facts a wallet and a transaction hash do not carry.
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.
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.