Payment Domain Event

Overview

Meaning and scope

Payment Domain Event is an immutable statement that a meaningful payment-domain fact has occurred. Examples include a payment being authorized, a route being selected, a settlement batch closing, or a refund being approved. It describes a completed fact in past-tense business language, unlike a payment command, which requests that an action be performed.

Mechanism and operation

A payment domain event expresses a durable business fact such as invoice issued, transfer confirmed or refund approved. It is emitted when the owning domain accepts a transition and usually carries an immutable identifier and context. Event consumers can update projections or trigger later actions, but the event does not itself grant payment authority. Its semantic contract matters more than the particular message broker used to transport it. Operational implementation normally requires clear business meaning, aggregate or entity reference, event time and unique ID, schema version, and reliable publication after state change. Useful measures include publication success, event lag, consumer failure rate, schema compatibility, and reconciliation against source state.

Practical payment example

A payment state machine emits PaymentConfirmed with a unique event identity. Consumers derive invoices and notifications from the event while preserving immutable commercial context and handling replay safely.

Operational checks

Define the business meaning, version, unique identity, aggregate ID, occurrence time and causation context for each event. A domain event represents a completed or accepted business transition, not an arbitrary HTTP log. Consumers must tolerate duplicate delivery and schema evolution, and should not infer payment settlement from an event labeled merely requested or detected. Retain the underlying evidence needed to reproduce a ledger update.

Distinctions and limits

The principal risks include events emitted before durable state, ambiguous names, mutable payloads, missing causation, and using technical logs as business events.

Related reading

Related definitions: Payment Command, Payment Event Type.