Automated receipt checks
Confirms schema v29, callback-key attribution, HMAC verification, replay rejection, forward-only receipt state, immutable callback evidence and contradictory-terminal-event quarantine.
ClaraWideProvider delivery receipt QAThis release keeps provider submission evidence separate from authenticated delivery receipts. Signed callbacks can advance delivery truth; bad signatures and replayed event IDs are rejected, while contradictory terminal receipts are quarantined instead of silently rewriting history.
Confirms schema v29, callback-key attribution, HMAC verification, replay rejection, forward-only receipt state, immutable callback evidence and contradictory-terminal-event quarantine.
Use the staging simulator to prove the callback trust boundary without connecting a real provider.
No provider-message evidence loaded yet.
No callback receipts loaded yet.
No reconciliation events loaded yet.
A terminal receipt that contradicts prior terminal truth is retained and quarantined for review; it does not overwrite the earlier state.
No reconciliation conflicts loaded yet.
These stay open until a real provider, real signing key, real callback traffic and real bounce/complaint operations exist.
Clearing browser evidence does not rewrite server-owned provider messages, signed receipts, reconciliation events or conflicts.