Accounting calls follow the commit under stable keys
Context
A remote service can complete a financial request even when its response is lost.
Decision
Preserve stable keys for financial requests and record answers separately from domain commits. Recover by resuming known requests rather than guessing that failure means no remote effect.
Alternatives Considered
Calling Accounting under a domain lock extends transaction duration. Removing the sale on a lost answer could leave a real remote charge without its purchase record.
Consequences
Recovery has explicit gaps: provisional deletion is not retried, and missing transport can leave pending work silent. Declined purchases remain until their deadline or an authorized void.