Edit Template

Product Trust Packet

A signed permission for one action.

A Trust Packet™ is a signed permission for one action, one recipient and one use. Your verifier checks it before anything changes.

Trust Packettp_7f3a91c2Illustrative
action
update_supplier_bank
sender
ap.supplier.example.com
audience
erp.buyer.example.com
payee
Sample Merchant
account
XXXXXXXX0000
expires
in a few minutes
nonce
example_nonce_7f3a
signature
example_signature_only

Sample values. Signed by the sender, checked by the recipient’s verifier.

01 · What it is

One action, one recipient, one use.

A credential says who is calling. A Trust Packet says what this one action is allowed to do. The action needs both.

The sender signs it. The key behind the signature is published in the sender’s own DNS as its Authority Anchor, so any verifier can check it with no prior integration. A stolen login alone can’t make one.

What it proves

Who signed?
The key is checked against the sender’s Authority Anchor in its own DNS.
What for?
This payee, this amount, this account.
When?
A short window you set: a few minutes, then void.
How many times?
Once. A replayed packet is refused.
For whom?
This recipient only.

02 · What it looks like

A sample packet for a bank change.

A supplier asks to change its bank details. The packet names the action, who sent it, who it’s for and the new account, then carries the sender’s signature.

Trust Packet anatomytp_7f3a91c2Illustrative
action
update_supplier_bank
sender
ap.supplier.example.com
audience
erp.buyer.example.com
scope
payee: Sample Merchant
account: XXXXXXXX0000
expires
in a few minutes
nonce
example_nonce_7f3a
signature
example_signature_only
  1. What is being asked. The packet is good for this action and no other.
  2. Who signed. The verifier looks up this domain’s Authority Anchor in DNS.
  3. Who it is for. Presented to any other recipient, the packet is refused.
  4. The exact parameters. This payee, this account, this amount. Change one and the signature no longer matches.
  5. How long it lasts. A few minutes. After that the packet is void.
  6. How many times. Once. A second presentation is refused as a replay.
  7. The proof. Made with the sender’s private key, which stays with the sender.

Sample values only: example domains, a masked account and a placeholder signature. Field names are illustrative. RFC-2001 defines the required fields.

03 · Single use

Present it twice. The second time is refused.

A copied packet is refused at any other recipient, and refused a second time at this one. The refusal is written to the Authorization Ledger like any other verdict.

First presentationtp_7f3a91c2
  1. Signatureagainst the Authority Anchor in DNSpass
  2. Time windowinside the short validity windowpass
  3. Not replayednonce not seen beforepass
  4. Audiencenamed for this recipientpass
  5. Scope and chainaction and limits inside what was signedpass
APPROVEDWritten to the ledger as al_000418. The ERP update runs.
Second presentationtp_7f3a91c2
  1. Signatureagainst the Authority Anchor in DNSpass
  2. Time windowinside the short validity windowpass
  3. Not replayednonce not seen beforerefused
  4. Audiencenamed for this recipientnot run
  5. Scope and chainaction and limits inside what was signednot run
REFUSEDNonce already used. Written to the ledger as al_000419. The ERP update does not run.

04 · On the wire

What the packet points at.

The sender field names a domain. The verifier reads that domain’s Authority Anchor from DNS and checks the signature against it.

When authority was delegated, the packet also carries an Authorization Certificate, and the verifier checks every link in it.

Sample Trust PacketIllustrative
{
  "action": "update_supplier_bank",
  "sender": "ap.supplier.example.com",
  "audience": "erp.buyer.example.com",
  "payee": {
    "name": "Sample Merchant",
    "routing": "000000000",
    "account": "XXXXXXXX0000"
  },
  "expires": "in a few minutes",
  "nonce": "example_nonce_7f3a",
  "signature": "example_signature_only"
}

Sample fields, for illustration. RFC-2001 defines the required fields, and a deployment can add its own. Example domains, a zero routing number and a masked account.

05 · Read it, watch it

Check it yourself.

The specification

RFC-2001, Trust Packet format

How this part is built and checked, in the open RFC series on GitHub.

Open the RFC series

Recorded demo

Watch it in the ERP demo

A supplier bank change, held until it’s verified, in the UniKey demo environment.

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