THE CORE IDEA
AoR

The Authorization of Record.

When an agent moves money, one question outlives the transaction: was it actually allowed? The Authorization of Record is Fidacy's signed answer: a verifiable statement of authority, bound to the action and preserved in a tamper-evident evidence trail.

Why a system of record for authorization

Ledgers record that money moved. They do not record that the movement was authorized: by which user, under which mandate, checked against which policy, and decided how. That gap is where agent commerce breaks down: a dispute becomes one party's logs against another's, with no neutral truth in between.

The Authorization of Record gives the transaction a signed statement of authority: which mandate was active, which policy was applied and what Fidacy decided at that moment. A counterparty can check the signature and record without accepting an internal log on faith.

What it binds together

{{ row.title }}

{{ row.body }}

Three properties that make it authoritative

{{ row.tag }}

{{ row.body }}

The record, in one object

{
  "authorized": true,
  "user": "usr_4a1", "agent": "agt_shopper_02",
  "mandate_hash": "sha256:9f2c…",
  "decision": "approve", "policy": "pol_2026_07",
  "chain": { "seq": 41, "prev": "sha256:7b0a…" },
  "jws": "eyJhbGciOiJFZERTQSJ9.."
}

See it hold up

The Authorization of Record is a receipt you can verify and try to break. Tamper with one in the sandbox, or verify a real one yourself.

Open the Proof sandbox → How receipts work →