#anuroop0431
fierce bone
chilly jasper
Hi there!
the status of that invoice is uncollectible, so it's expected you get an error.
Is your question why the invoice became uncollectible?
cloud token
No the invoice wasn't uncollectible when this happened
It was still active for collection in a retry period.
This is the invoice id
in_1NjAY7IGl3kRb8fo8pN9LCDh
chilly jasper
Having a look
cloud token
Sure thank you!
north harness
Why this happened?
because there was still an ACH payment(py_3NjBWFIGl3kRb8fo05I90SUU) processing against the Invoice at the time you made the call so that needs to resolve before you can do anything else.
Should we stop attempting to immediately charge an invoice on PM update if an invoice is in retry period?
it's not really about the retry period I think, more it's about the Invoice'schargebeingstatus:pending.
cloud token
So if a invoice is in retry period, which it always be pending?
In our case, we have retries set up for 3 days past first try, 7 days past the first retry and 7 days past the second retry.
Does the invoice stay in a pending state through these 17 days?
north harness
the pending status is not because the Invoice is undergoing retries, it's because the last payment attempt on it was using ACH, which takes a few days to process.
https://stripe.com/docs/payments/ach-debit#:~:text=It can take up to 4 business days to receive acknowledgement of success or failure.
cloud token
can we identify if an invoice is in pending state before we attempt to charge it?
north harness
invoice->charge->status
cloud token
Thank you!