Context

Payment orchestration needs to support retries, provider failover, and future payment methods without leaking provider-specific fields through the catalog.

Decision

Stripe commands and events remain inside the PaymentGatewayService boundary. PaymentService talks to the gateway through provider-neutral contracts.

Consequences

Provider changes are localized to PaymentGatewayService. The gateway must maintain a mapping between provider identifiers and internal payment references.