Money Commands Take Request Keys

Context

Clients need to recover a completed financial outcome after losing its response.

Decision

Use scoped request keys for supported money commands, with claim-first creation paths and replay-and-store approval paths.

Alternatives Considered

Rely only on expected versions. A lost successful response would become a stale refusal, while creation has no prior row version.

Use an early separate key claim for every approval command. The existing audited-guard protocol retains refusal evidence without leaving that claim behind.

Consequences

Matching retained bodies replay; changed bodies under a completed key are refused. Accounting modules share the hosted request ledger and its cleanup. Fresh console keys and unkeyed ancillary commands limit user-level retry protection.