Even though the gateway correctly receives the callback indicating that the payment status is approved, the transaction does not progress to authorized and then approved. A subsequent authorization request is sent, and since the return is undefined, the transaction remains in the authorizing status until the number of retries is exhausted.

For this issue to occur, the gateway must retry at the same timestamp as it received the callback. It is not simple to reproduce this behavior, as hitting the exact same timestamp is quite difficult.

There are two actions the partner can take:

1. If the payment is approved, respond to subsequent authorization request calls from the gateway with this status rather than undefined.
2. Increase the number of retries (delayToCancel) so that the gateway makes more attempts.