Flow monitor connecting… reading … correlation

Flow · one box per ledger entry name of the canonical flow (architecture §6); the number is the step. Hover a box for what it means and what lit it

Refusals · request.refused, counterparty.verified with ok:false, mandate.denied, payment.ambiguous, for this correlation

Checks · what the buyer verified about the seller before sending a byte (counterparty.verified), and whether the seller accepted the checkout

Live feeds · the entries of this correlation, as each ledger serves them

Buyer ledger
not read yet
    Seller ledger
    not read yet
      Authority · mandate status
      done: its ledger entry exists in progress: next step, while the flow is live refused, with the reason code outcome unknown (payment.ambiguous) no entry

      This page polls the two ledgers and the authority's status endpoint from your browser and renders what it reads: the same public evidence the verifier consumes, nothing computed here and nothing written anywhere. When the buyer bought from a seller of another operator, that seller's own public list of purchases is read too (its /ledger, a plain list in its own form) and its line for the checkout session lights the payment boxes; the buyer's sealed receipt is where that purchase is verified. A step turns green when its entry appears, never before. A replay plays recorded entries back and says so on screen; it is never shown as live. Polling pauses while this tab is hidden and resumes, with a fresh read, when it is shown again. Override the feeds with ?seller=…&buyer=…&authority=…, pin a transaction with ?correlation=…, hide older transactions from the picker with ?since=2026-09-10, or read faster or slower with ?interval=1000 (milliseconds; every read is a request against the ledger being watched).