Skip to content

Commerce events

Agentful records durable commerce events when important domain state changes. Events are inserted inside the same database transaction as the state change, so they represent committed facts rather than best-effort notifications.

  • orders.created
  • orders.paid
  • orders.refunded
  • orders.status_changed
  • payments.captured
  • payments.refunded

Disputes and provider webhooks are tracked separately from refunds.

Core event tools:

  • events.list
  • events.get
  • events.list_for_aggregate
  • events.replay

Replay resets delivery rows for a specific event so failed consumers can run again. Handlers must be idempotent because delivery is at least once.

Enabled plugins receive only the event types declared in their manifest and allowed by their requested permissions. Plugin delivery failures do not roll back the original order or payment transaction; they are retried through the delivery table.