#terry.lau
1 messages ยท Page 1 of 1 (latest)
Hello ๐
How recent is this? Do you example PaymentIntent IDs?
They were around October - November
intent IDs: pi_3Ln4ufA8aJ5eS52Q0Qw9xYh9, pi_3LwTzyA8aJ5eS52Q08pRwwd0, pi_3M5CwFA8aJ5eS52Q0JPUZvRC
from 3 affected accounts, some were attempted multiple times
We've had payments from those issuers go through in the past, so trying to figure out why some are left in an upcaptured state, only to be canceled later.
It looks like you're using manual capture for the PaymentIntents which means you're initially placing a hold and then capturing the amount by calling the API
https://stripe.com/docs/payments/place-a-hold-on-a-payment-method#authorize-only
However, for the first PaymentIntent we didn't receive a request to capture the amount. So after 7 days, the hold was released.
https://dashboard.stripe.com/logs/req_qz7A3pEiOqksH3
Checking other PaymentIntents...
yup same thing with other PaymentIntents
We never received a request to capture the amount
Makes sense then. Thanks for clarifying there
NP! ๐ Happy to help