#shawn-paymentintent-capture
1 messages · Page 1 of 1 (latest)
shawn-paymentintent-capture
@lunar flume that should be impossible. Capturing a PaymentIntent is synchronous so you start and when that ends the PaymentIntent is status: 'succeeded'.
IF you do the requests in parallel though that's expected. The second one waits on the first one to finish, and when that first one finishes the PaymentIntent is already captured so obviously that second fails.
yes, they might be happening in parallel which I can understand why the state would be requires_capture, but why the wrong error code?
there's no wrong error code. That error code is when you capture the Charge itself, you're capturing the PaymentIntent and get a different error code that's all
oh i see