Skip to content

Use case

Machine-readable receipts

Consume fiscal402.receipt/1.0.0 as a portable, signed fiscal-event object.

Problem

PDF invoices and dashboard exports are not a common primitive for autonomous commerce. Downstream systems need a stable, verifiable JSON object.

Input

A fiscal402.receipt document, the issuer JWKS, and optionally the bound UBL UTF-8 bytes.

Fiscal402 processing

Independent verification recomputes fiscal402.sorted-json/1, checks the SHA-256 digest, verifies the Ed25519 signature against JWKS, and optionally matches the UBL SHA-256.

Output

A VERIFIED or INVALID result. VERIFIED means Fiscal402 receipt integrity under the public rules. It does not mean tax-authority approval.

Limitations

Integration path

Read the specification at /protocol/receipt. Download the sanitized example at /examples/fiscal402.receipt-1.0.0.json. Verify with the public repository source.

Last updated 11 September 2026