Signed evidence
Payment Passport
A Payment Passport is the signed, canonical record of a payment’s truth — something a counterparty, an auditor or your own finance team can verify independently, without trusting your database or a screenshot. It is produced from Payment Truth and signed with a key whose public half is published.
The problem
“Trust me, it settled” does not hold up in a dispute, an audit or a reconciliation between two companies. You need evidence a third party can check for themselves — that names exactly what was observed, and that no one could have quietly edited after the fact.
EVIDENCE != CONSENSUS
What StoneReason does
Signs the canonical truth
The Payment Truth for a session — its axes and the evidence they rest on — is serialized canonically and signed with Ed25519.
Anyone can verify
The public signing keys are published at a stable endpoint. A third party verifies a Passport with the key and a domain tag, offline, without calling you.
Corrections keep history
If the truth changes — a later observation, a reorg — a new Passport is issued. The prior one is not erased; the record is append-only.
What StoneReason does not do
A Passport is not consensus. It attests what StoneReason observed and established, not a cryptographic proof from the chain’s validators.
No stronger than the observation. If finality was not
established, the Passport says UNESTABLISHED — it
never signs a certainty that was not there.
No custody, no keys of yours. Signing a Passport touches no funds and uses StoneReason’s own signing key, not yours.
No silent edits. The signature covers the exact record; a changed byte fails verification.
Live on this deployment
Passport generation and third-party verification are
live. The public signing keys are served at
GET /v1/payment-passports/signing-keys, and any Passport
verifies against them independently. The strength of a given Passport is exactly the
strength of what was observed for that payment — an unpaid or unobserved
obligation produces a Passport that honestly says so.
What a Passport carries
Who this is for: anyone who has to show a payment happened — finance and audit teams, counterparties settling between systems, platforms proving a payout to a user.
Input: a payment session with established truth.
Output: a signed Payment Passport, independently verifiable.