Transactions & events
The journal is the system telling you what it did: transfers crossing their states, fees collected, endpoints changing. Follow any reference and its whole governed record opens, every event, the fee, the balances after.
One journal. One reference. The whole record.
- Surface
- the activity journal
- Each row
- amount · status · route · ref
- Follow
- one reference, end to end
- Delivery
- coming
The book as it stands.
as of 09:48:17A $2,400.00 transfer from collection. Reserved 09:42, settled 09:48, fee collected.
Lineage · 7 events
- transfer.requested09:42:01.220
Created against an accepted quote (tolerance: exact).
- appfee.assessed09:42:01.224
Your application fee assessed up front, on the quote.
- debit_envelope.reserved09:42:01.241
Value held on the source: committed, not yet gone.
- transfer.submitted09:42:02.010
Submitted to the provider rail.
- transfer.awaiting_finality09:42:02.122
Waiting on the provider's finality signal.
- transfer.settled09:48:17.604
Final on the rail; the reserve is released.
- appfee.collected09:48:17.611
Fee collected into the fee collection account.
The wider stream · filter by family
- appfee.collectedtr_3Vd7Q09:48:17
- transfer.settledtr_3Vd7Q09:48:17
- transfer.awaiting_finalitytr_3Vd7Q09:42:02
- transfer.submittedtr_3Vd7Q09:42:02
- debit_envelope.reservedtr_3Vd7Q09:42:01
- appfee.assessedtr_3Vd7Q09:42:01
- transfer.requestedtr_3Vd7Q09:42:01
- change.proposedak_live_2Kp09:40:12
- appfee.collectedtr_3Vb2109:39:18
- transfer.settledtr_3Vb2109:39:18
- transfer.awaiting_finalitytr_3Vb2109:38:42
- transfer.submittedtr_3Vb2109:38:42
- debit_envelope.reservedtr_3Vb2109:38:41
- appfee.assessedtr_3Vb2109:38:41
- transfer.requestedtr_3Vb2109:38:41
- endpoint.suspendedep_4Lm09:36:50
- appfee.collectedtr_3Vb2809:31:02
- transfer.settledtr_3Vb2809:31:02
- transfer.awaiting_finalitytr_3Vb2809:30:03
- transfer.submittedtr_3Vb2809:30:02
- debit_envelope.reservedtr_3Vb2809:30:02
- appfee.assessedtr_3Vb2809:30:02
- transfer.requestedtr_3Vb2809:30:02
- transfer.awaiting_finalitytr_3Vb2f09:28:15
- transfer.submittedtr_3Vb2f09:28:15
- debit_envelope.reservedtr_3Vb2f09:28:14
- appfee.assessedtr_3Vb2f09:28:14
- transfer.requestedtr_3Vb2f09:28:14
- account.openedacc_9Tw09:24:33
- settings.updatedorg_Northwind09:21:08
- appfee.collectedtr_3Vb3609:17:40
- transfer.settledtr_3Vb3609:17:40
- transfer.awaiting_finalitytr_3Vb3609:16:32
- transfer.submittedtr_3Vb3609:16:32
- debit_envelope.reservedtr_3Vb3609:16:31
- appfee.assessedtr_3Vb3609:16:31
- transfer.requestedtr_3Vb3609:16:31
- key.createdak_live_7Q409:12:44
- member.role_changedpr_2Kp09:05:31
- appfee.reversedtr_3Vb3d09:04:09
- transfer.returnedtr_3Vb3d09:04:09
- transfer.awaiting_finalitytr_3Vb3d09:03:23
- transfer.submittedtr_3Vb3d09:03:23
- debit_envelope.reservedtr_3Vb3d09:03:22
- appfee.assessedtr_3Vb3d09:03:22
- transfer.requestedtr_3Vb3d09:03:22
- appfee.collectedtr_3Vb4508:51:09
- transfer.settledtr_3Vb4508:51:09
- transfer.awaiting_finalitytr_3Vb4508:50:13
- transfer.submittedtr_3Vb4508:50:13
- debit_envelope.reservedtr_3Vb4508:50:12
- appfee.assessedtr_3Vb4508:50:12
- transfer.requestedtr_3Vb4508:50:12
- appfee.collectedtr_3Vb4c08:44:41
- transfer.settledtr_3Vb4c08:44:41
- transfer.awaiting_finalitytr_3Vb4c08:44:03
- transfer.submittedtr_3Vb4c08:44:02
- debit_envelope.reservedtr_3Vb4c08:44:02
- appfee.assessedtr_3Vb4c08:44:02
- transfer.requestedtr_3Vb4c08:44:02
- config.fee_rule_amendedfeerule_app08:41:27
Read it; you do not write it
The journal is a record, not a form. Each row is an event the system emitted as it acted. You filter to a family to watch one kind of change, or follow a single reference to see a transfer's entire life.
Follow the reference
Select tr_3Vd7Q and its lineage opens — requested, fee assessed, reserved, submitted, awaiting finality, settled, fee collected — every event carrying the same correlation reference. Nothing about a transfer happens off this thread.
Replay reconstructs the state
Because the journal is the events themselves, any state can be rebuilt by replaying them. The figures you read carry a freshness, so you always know whether a number is fully caught up before you act on it.
Outbound delivery is coming
Today you read the stream in the console. Pushing these events to your own endpoint, with retries, is being built. Until it lands, the stream here is the source of truth.