CONCEPTS

The verdict, the UCP way.

Fidacy attaches a signed verdict to a Universal Commerce Protocol order as a trust_envelope — so trust travels with the order across parties, not with the platform that issued it. UCP support is a preview: the envelope may change with the spec; the verdict core does not.

The trust envelope

Fidacy wraps the same signed verdict every protocol carries and binds it to the order by hash. Attach it under order.trust_envelope.

{ "order": { "id": "ord_7c2", ,
  "trust_envelope": {
    "issuer": "fidacy",
    "decision": "approve",
    "order_hash": "sha256:1a9f…",
    "jws": "eyJ…", "verify_url": "https://…/jwks.json"
  }
}}

Bound to the order

The order_hash covers the canonical order. Change a line item after the verdict and the hash no longer matches — the envelope stops applying, and every party can tell.

Who reads it

{{ row.who }}

{{ row.use }}

One core, three protocols

UCP is the third adapter over the protocol-blind verdict core, beside AP2 and A2A. The decision, the signature, and the audit chain are identical — only the wrapper differs. For the normative field-by-field spec, read the extension.

← PREVIOUS
A2A Protocol
NEXT →
API Reference