Wireframe with example data. Nothing on these pages reads a live service.

Published events

What Trade Gateway sent to a consumer, by reference. This is the page that answers "I have an error, what payload is the gateway sending to my service?"

Not buildable yet

Nothing records what went out. The publisher emits a pointer event and persists only job watermarks and leases, so there is no event log to list. This needs an event store in trade-gateway-publisher (or a read of the consumer-side record) before the table below can be filled.

Published (UTC) Reference Origin Topic Event ID
18 Nov 2026, 09:38:51 GBCHED.2026.0001234 TRACES ..._ched_stream_internal 0f3a…c81
18 Nov 2026, 09:31:02 GBCHED.2026.0001234 Force ..._ched_stream_internal 7b21…a04
17 Nov 2026, 16:02:44 GBCHED.2026.0001198 TRACES ..._ched_stream_internal_asb c940…1de

Data source: No listing endpoint exists. GET ched/{chedId} on the publisher triggers a publish; it does not report one.

origin is a free-text field on the event, not an enum. Only one value is ever written by our code: Force, set by the publisher's GET ched/{chedId} route. Everything else arrives from TRACES unchanged by the scheduled job, so the other values are TRACES' own and should not be assumed.

What the consumer actually receives

A pointer, not the certificate. The event carries the id, the origin and the timestamps; the consumer then fetches the full mapped profile from the gateway. So "the payload the gateway sent" is these fields, and the certificate body is what the consumer fetched afterwards.

{
  "id": "GBCHED.2026.0001234",
  "origin": "Force",
  "timestamp": "2026-11-18T09:31:02Z"
}
A forced republish of an unchanged CHED carries the same duplication id and is deduplicated by the FIFO stream — it can appear in this list as an attempt that the consumer never saw. Show the consumer outcome alongside it, or the page will mislead.