問題文
A fitness chain's membership charges are submitted to a payment provider by custom retry logic that runs until it receives a success. Members are occasionally charged twice. The provider says it does reject duplicates, but only when the same request identifier is presented, and the identifiers it receives are always different. What should be corrected in the build?
選択肢
- The charge should be moved into the same transaction as the record update, so that a failed charge undoes the membership record change along with it.
- The provider should be asked to detect duplicates by amount and member.
- The retry logic should stop after the first attempt regardless of the outcome, since any second attempt risks a duplicate, and members can be asked to submit the payment again through the self-service portal whenever the first attempt does not produce a receipt.
- The retry has to present the same identifier on every attempt, because a new identifier per attempt makes each retry look like a separate charge.