SealLab

The same proof flow, under a test-only name.

SealLab exercises the packet, seal, local report, and verifier path without giving a real payment instruction or touching the live ProofRail ledger.

Create SealLab Test Pass Open verifier

What stays identical

The JSON packet, ProofRail Seal format, SHA-256 receipt, local report object, and verifier path are the same mechanics used by the live checkout flow.

Packet`proofrail.order_intent.v3` with sorted JSON receipt canonicalization. v2 packets still verify; only new payment intake requires v3.
Report`proofrail.payment_report.v1` stays `USER_REPORTED_SENT_UNVERIFIED`.
VerifierThe public verifier checks digest, report linkage, seal linkage, and non-custody boundaries.

Rule

Test receipts can prove the system. They cannot prove payment.

A SealLab packet may be valid end to end, but it carries `test_only=true`, `production_ledger_eligible=false`, and `no_real_payment_expected=true`. Those markers are the receipt boundary.