When a transaction has multiple payments and becomes asynchronous due to Sherlock or Defense mode, and if the first payment authorization attempt fails, it can result in the other payments being stuck in an "Authorized" status. This is because the entire transaction is canceled, but our worker does not recognize this and proceeds with an authorization attempt for the second payment. Consequently, the second payment cannot be canceled, as the transaction has already been canceled, and it does not allow a cancellation request.

Create a transaction with two payments, in which Defense Mode or any other feature that makes the transaction asynchronous is activated. Then, use a custom provider connector to decline the first payment authorization attempt while approving the other one.

N/A