Question 26
A payment request times out. The service supports a stable idempotency key and a status lookup by that key, but the client does not yet know whether the payment completed. Which actions form the safest retry policy?
Assign a new idempotency key to each attempt so every retry is audited separately.
Repeat the request after each timeout without checking status or limiting total attempts.
Reuse the original idempotency key whenever the same logical payment is submitted again.
Treat the timeout as a successfully completed payment and never consult the service record.
Query the original key's status before deciding whether another payment call is necessary.
Create a replacement order so the retry receives a different payment identity for easier accounting.