01
Evidence with less data
The receipt contains references and hashes, not the personal attributes presented. Retention in the source system is managed separately.
AFFINITY / Evidence Receipts
The decision passes.
The evidence stays.
Keep technical evidence of a decision without copying the personal attributes used to assess it into the receipt. Inspect, export and check its integrity.
Pilot integration · scope agreed with you
Evidence ReceiptsInteractive example
A decision with a trace.
Example receiptER / DEMO-001
Decision approved
- Source
- Verify Gateway
- Decision context
- Recorded
- Personal attributes
- Not included in the receipt
AFFINITY EVIDENCEDEMONSTRATION
Illustrative checks; no real receipt is verified.
Try the controls · simulated data
01 / The problem
A result alone does not tell the whole story.
Scattered logs complicate audits. Keeping copies of all the data does not explain what happened, when or in which context. You need evidence you can inspect and verify.
02 / What's included
Review, verify and share evidence.
02
Verifiable signature
ES256 signing and published keys allow integrity checks when signing is configured as mandatory.
03
Two ways to review
JSON preserves the technical structure; PDF supports human review. Both can be exported in supported flows.
04
Public verification
Check receipts by identifier or document without an account. A witness or anchor is configured optionally.
03 / How it works
From what happened to what you can demonstrate.
- 01
Capture the evidence
Supported flows attempt to generate a receipt with the decision, technical references, hashes and timestamps.
- 02
Inspect and export
Find the receipt associated with your operation and export JSON or PDF for review and retention.
- 03
Check integrity
Verify the hash and configured signature through the public service. Anchoring is an optional, independent layer.
04 / IN YOUR CONTEXT
Built around real problems.
Every integration starts with a specific use case. Here are a few starting points.
Let's talk01Review a verification
Link a Verify Gateway result to its receipt when one has been generated. Inspect the decision context without including disclosed attributes in the receipt itself.
02Review a credential lifecycle
Keep evidence of issuance or revocation in supported Product API flows. Coverage is validated per producer and operation.
03Investigate agent actions
Use available receipts to review approvals or denials. Generation can fail without reversing the action and does not yet cover every flow consistently.
PRODUCT SCOPE
Clarity from day one.
What you can explore today
Queries, JSON/PDF export, configurable ES256 signing and public verification. The v1 format is partial and generation is not guaranteed for every event.
Where it is heading
Unifying producers, complete format validation and anchor reconciliation continue to evolve. A receipt provides technical evidence; it does not certify regulatory compliance on its own.
Evidence Receipts
Your use case. Our next conversation.
Tell us what you want to solve. We’ll define the scope and the next step together.
Let's talkView overview