191542113.1 is the one start session later, and with no playload data passed from frontend, but make authorize request earlier and then successfully capture, so this one logged to civi with no name and email
191542083.1 is the one start session first, then wait 52 seconds then have the authorized request later than the first one, while with the customer info from playload, but since the other one made request first, so been blocked by verification error. do not made the step to capture it, so not log to civi.

Info from log:
This transaction (191542113.1) made made authorize request on Sep 6 17:07:27 right before the other one (made authorize request on Sep 6 17:07:55) that have the customer info from playload (191542083.1), which this one with playload info have the first session on Sep 6 17:07:02, which is way before the success captured one (Sep 6 17:07:25) and the second session timestamp for the one do not success due to (createPayment call came back with validation error in payment_method with message: Cannot use a single-use payment method more than once).

Can not mock it locally, but suspect that client tried to donate twice, the first time wait too long, then lost the playload info, then make the request again, then this time works but without playload info or open a new tab?