Embed Fiscal402 after settlement. One platform integration exposes a global fiscal-event model with explicit jurisdiction coverage to many merchants. Fiscal402 stays post-settlement: you already moved the money; Fiscal402 makes the result fiscally usable when coverage exists.
Input
- Verified settlement evidence (protocol, network, asset, tx, settled_at)
- Merchant fiscal profile (legal name, country, VAT/tax IDs, invoice address)
- Transaction context (seller, buyer, supply, attested customer country)
Fiscal402
- verified settlement
- ↓
- FiscalEvent
- ↓
- JurisdictionRouter
- ↓
- determination where verified
Output
- Normalized fiscal event
- Jurisdiction evaluation (SUPPORTED / EXPERIMENTAL / MANUAL_REVIEW)
fiscal402.receipt/1.0.0when production-eligible- UBL 2.1 artifact on the EU path
Boundary
Fiscal402 does not:
- settle payment
- hold funds
- replace a facilitator
- authorize payment
- remit tax
Coverage before ingest
Query POST https://api.fiscal402.com/v1/capabilities/check with seller/buyer countries before you process. US → NL digital B2C can be EU VAT production. NL → US persists as a fiscal event and fails closed on US tax.
Sandbox
Evaluate without settlement: POST https://api.fiscal402.com/v1/compliance/evaluate. Ingest after settlement: POST https://api.fiscal402.com/settlements with X-Fiscal402-Key. Global parties: POST https://api.fiscal402.com/v1/fiscal-events.