Platform
Receipt check
Kind: A platform service both lanes stand on.
Availability
ShippedLive on this deployment: it needs nothing more to run.
- Door
/verify · /api/verify-receipt- Unlocks with
- Nothing: it is free and public.
Every status follows one rule from this deployment's own configuration: a capability is marked shipped only when everything it needs is in place.
What it does
Anyone can check a delivered document's receipt fingerprint against the receipt ledger.
Keep in mind
A receipt that cannot be checked is reported as unchecked, never as a failed match.
What it refuses
| Answer | HTTP | Meaning |
|---|---|---|
unavailable | 503 | The receipt ledger could not be read: the answer is unchecked, never a failed match. |
| — | 429 | Too many requests in a short time: the answer says when to try again. |
- Answer
unavailable- HTTP
- 503
- Meaning
- The receipt ledger could not be read: the answer is unchecked, never a failed match.
- Answer
- —
- HTTP
- 429
- Meaning
- Too many requests in a short time: the answer says when to try again.
What can leave EstateDraft
The registry declares no action of this capability that reaches outside EstateDraft.
Evidence
src/app/api/verify-receipt/route.test.tssrc/lib/master-plan-phase4a.test.tssrc/app/api/verify-receipt/route.tssrc/lib/receipt-hash.ts
Reviewed: