Receipts
A receipt for what actually happened.
Each operation produces a receipt you can keep, share and check independently. It records what was asked, what the system reported and what was verified — as three separate facts.
Illustrative example · not customer data
Anatomy of a receipt.
Identity
Receiptexample-r-01
OperationPurge one cache path
ConnectionExample Cloudflare zone
Requested byExample agent
Timeline
Requestedexample time
Provider acknowledgedexample time
Recordedexample time
Three separate facts
ExecutionThe provider reported the purge request as accepted.
DeliveryWhether the result reached the requesting agent.
VerificationWhether the record’s integrity and signature check out.
Limitations stated on the receipt
- Confirms the provider accepted the request — not that every edge node has evicted the path.
- Payload retention can differ from receipt metadata retention.
Source references
Links back to the provider’s own identifiers, so anyone with access can check the original record.
Portable export
Export a selected receipt as a bundle you can verify without an Ardyn account.
Private by default
Receipts belong to your workspace. Public verification never searches customer receipts by ID.