Real receipts · independently verifiable

What an AI Decision Receipt looks like in the real world

Each scenario below is a genuine decision an AI agent might take — and each one is sealed into a signed, hash‑chained Decision Receipt that lives in this node's ledger right now. The content shown is synthetic demo data, but the cryptography is real: click Verify this receipt on any card to confirm its signature, integrity and chain yourself — no account, no access to our systems.

Open the verifier → Read the ADR spec
Five real, hash-chained Decision Receipts live in this node's ledger — each independently verifiable below.
Customer support · low risk

AI agent approved a refund

A support copilot autonomously approved a customer refund within its spending authority and sealed the decision into a signed receipt.

approved
Banking · high risk

AI agent rejected a loan

A credit agent declined a loan application under a documented policy, with a human reviewer recorded in the receipt.

rejected
CRM / Operations · medium risk

AI agent modified a customer record

An operations agent updated a customer record, sealing the before/after fingerprints into a tamper-evident receipt.

modified
Treasury · critical risk

AI agent approved a wire transfer

A treasury agent released a wire transfer within its approval limit — the exact scenario auditors ask to reconstruct.

approved
Insurance · high risk

AI agent flagged a claim for review

A claims agent flagged a suspicious claim for human review, recording the decision and rationale fingerprints.

flagged

How a company can reproduce this

Every receipt here was created with the same public API and SDK a customer uses. In a test environment it is three lines:

import { Signatrust } from 'signatrust';

const str = new Signatrust({ apiKey: process.env.SIGNATRUST_API_KEY });

const { receipt, share_url } = await str.issueReceipt({
  model: { provider: 'openai', name: 'gpt-4o', version: '2026.4' },
  decision: {
    type: 'refund_approval',
    input,            // hashed locally — raw content never leaves your servers
    output,           // hashed locally
    risk_level: 'low',
    policies: ['support-refunds-v2'],
  },
});
// share_url → anyone can verify it, exactly like the cards above.