#mebezac_unexpected
sacred narwhalBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1257394056456044605
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
whole ice
Do you have a Payment Intent ID or Charge ID I can look at to see?
grave citrus
How can I verify this step?
whole ice
I don't understand. The Payment Intent you sent was created on 6/28 and the Payment Method was automatically updated in February, then later detached when used for a failed payment. There was no retry.
Also, where are you seeing a 1.5 year delay? Even in your screenshots it looks like the oldest event happaned in 2/24 of this year
jolly wing
The payment method was removed at 5:03pm, the payment attempt happened at 5:23pm (after the payment method was removed)
whole ice
What's the URL of this page?
grave citrus
@whole ice Can you please check my issue?
whole ice
Please be patient. We have a lot of other people we're helping
whole ice
It looks like you never canceled the Payment Intent after it initially went uncaptured. For Payment Intents that have no successful payment, you should monitor for those and cancel them after a period of time to stop this edge-case from occurring
jolly wing
Ok, so just to confirm removing a payment method will cause any non-cancelled payment intents to attempt to be charged? Is that correct?
Is that documented somewhere, along with any other triggers for attempting to charge a payment intent automatically?
whole ice
If you detach the Payment Method, it can no longer be used to make payments. Similarly, if you cancel a Payment Intent, no charges can be attempted on it.
We document payment retries here: https://stripe.com/resources/more/payment-retries-101-how-businesses-can-make-the-most-of-this-important-detail
jolly wing
Right that was our assumption "If you detach the Payment Method, it can no longer be used to make payments" so why when we removed pm_1MOYSi2R3kkGxJkDBXjLvwhX was it then used to attempt payment 20 minutes later?
It was the only payment method for that customer
whole ice
Huh... okay, yeah I see what you're saying now. Let me check with my team to see if anyone has an idea about what might have caused this.
jolly wing
Ok, thanks!
whole ice
Ah, okay. So the Payment Method was detached, which means it can no longer be used. Stripe later sends the payment_intent.payment_failed because the Payment Method is unusable. No payment attempt was made after it was detached. That progression of events is expected in this case, since (until the Payment Method was detached) the Payment Intent was technically in a capturable state.
Does that make sense?
jolly wing
Oh, ok yeah that makes sense, albeit a bit strange since we have webhook listeners for failed payments that send emails to our customers about the failure.
Like you said, I guess the long-term fix is to monitor incomplete payment intents and cancel them if they sit for a while.
sacred narwhalBOT
whole ice
Yeah, that's generally waht I'd recommend, since they remain in a payable state more-or-less indefinitely