Edit Template

Product Authorization Ledger

A record of every allow and refusal.

The Authorization Ledger keeps each verdict with the Trust Packet™ behind it, so you can show who approved what.

Ledger entryerp.buyer.example.comREFUSED
record
al_000419
action
update_supplier_bank
sender
ap.supplier.example.com
packet
tp_7f3a91c2
verdict
REFUSED
reason
nonce already used
prev
ex-e52d
hash
ex-f09a

One record. Its prev value is the hash of the record before it. Sample ids and hashes.

01 · What it is

A signed record, not a search through email.

Every allow and every refusal goes into the Authorization Ledger, with the packet that decided it.

When someone asks who approved a payee change, the answer is a signed record your team can show.

What it proves

What ran?
Each approved action, with its packet.
What was held?
Each action sent to a person.
What was refused?
Each failed check, with the reason.
Who approved?
The approver’s own signed packet.
Which packet?
The exact Trust Packet behind each verdict.

02 · What it looks like

Sample entries for a bank change.

The bank change is held for review, an approver signs, then the change runs. A second presentation of the same packet is refused. Each step is its own entry.

Authorization Ledgererp.buyer.example.comIllustrative
ChainRecordActionSenderVerdictCommits to
al_000415write_recordbilling.svc.example.comAPPROVEDprev ex-71c0hash ex-9d02
al_000416update_supplier_bankap.supplier.example.comREVIEW
Approver packet missing
prev ex-9d02hash ex-a41f
al_000417approve_supplier_bankapprover.buyer.example.comAPPROVEDprev ex-a41fhash ex-c3b8
al_000418update_supplier_bankap.supplier.example.comAPPROVEDprev ex-c3b8hash ex-e52d
al_000419update_supplier_bankap.supplier.example.comREFUSED
Nonce already used
prev ex-e52dhash ex-f09a
al_000420approve_purchaseassistant.agent.example.comREVIEW
Person packet missing
prev ex-f09ahash ex-0b77

Each record commits to the hash of the record before it, so a changed or missing row shows. Sample ids and hashes.

03 · The hash link

Each entry commits to the one before.

Change a row, or remove one, and every hash after it no longer matches. Both sides can keep a copy and compare.

A dispute starts from a signed record instead of a log file.

What an investigator does with a row

  1. Read. The verdict, the reason and the packet behind it.

  2. Recompute. The hash, from the entry and the hash before it.

  3. Compare. With the copy the other side holds.

04 · Read it, watch it

Check it yourself.

The specification

RFC-2002, Authorization Ledger

The ledger format, including entries for refused packets, in the open RFC series on GitHub.

Open the RFC series

Recorded demo

Watch it in the ERP demo

Follow the ledger as the bank change is held, approved and run.

See it work

Pilot

Try it in a sandbox first.

No live customer data sits on UniKey systems.

A UniKey property. © 2026 Swoop In Technologies LLC

Edit Template