#mclowrider_cancel-sub-invoice-payment
limber coralBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1399388534493806665
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- mclowrider_webhooks, 5 days ago, 4 messages
carmine iris
Hi, you made the request to cancel the subscription,https://dashboard.stripe.com/logs/req_qayRdinKqm7FRn at 2025-07-22 16:52:19 UTC. The billing cycle anchor on there is 2024-07-22 15:58:31. That invoice was created before the cancellation. You're asking why this event, evt_1RnjUuB6RcW2vRiFrRSocVht was triggered after the subscription deletion. Taking a further look here.
it looks like the end customer tried to pay the invoice shortly after the subscription was deleted
Since the invoice was not voided, they can still attempt to pay.
limber coralBOT
mclowrider_cancel-sub-invoice-payment
elfin oasis
Hi there 👋 I'm jumping in as my teammate needed to step away, and am taking a closer look at that Invoice.
Yeah, it looks like your customer triggered some actions from the Billing Customer Portal.
quick girder
Do we know what actions they triggered?
elfin oasis
Rather than approach this from that angle, can you instead help me understand how this payment impacted your flows? That way we can discuss what changes make sense to make to avoid that disruption going forward.
quick girder
Basically, an payment attempt was made minutes after the subscription was deleted
An attempt to charge the customer
elfin oasis
I don't think that's accurate, but please share related object IDs and timestamps if you believe I'm mistaken.
It looks like the request to cancel the Subscription was made at 2025-07-22 16:52:19 UTC:
https://dashboard.stripe.com/logs/req_qayRdinKqm7FRn
It looks like the Payment Intent associated with that Invoice (pi_3Rnib3B6RcW2vRiF16M4wrMt) was confirmed at 2025-07-22 16:44:02 UTC, prior to the Subscription cancellation.
The part that seems like it was handled after the Subscription was cancelled, was the 3DS authentication challenge that the issuer of the customer's card required. Though I'm not exactly sure whether that timed out or if the customer did complete the challenge before the issuer declined the transaction.
If you'd like to avoid payments being processed for Invoices when you cancel the related Subscription, you'll also want to add logic to find those related Invoices and to make a request to void them.
Once they're voided, then no further payments can be attempted for them.
quick girder
This event 👉🏾 evt_1RnjUuB6RcW2vRiFrRSocVht seems to have fired 4 minutes after the subscription was deleted
Are you saying that event 👆🏾 happened off the back of a failed 3DS attempt that was initiated before the subscription was deleted?
elfin oasis
Yup, off the back of this invoice.payment_action_required is my suspicion:
https://dashboard.stripe.com/events/evt_1RnjIOB6RcW2vRiF0by3fLfB
elfin oasis
Yeah, that's my thinking. I think they started the payment, hit the authentication requirement and didn't do that for some reason, then probably came to try the authentication again later after receiving an email or something.
quick girder
Do we know why the payment failed? Did it fail 3ds? Or was the payment declined by the bank due to an expired card?
The payment intent failed event is not quite clear from on why It failed.
elfin oasis
Can you double check what you see in the last_payment_error hash in the failed payment Event?
https://dashboard.stripe.com/events/evt_3Rnib3B6RcW2vRiF19fipfxb
quick girder
The provided PaymentMethod has failed authentication. You can provide payment_method_data or a new PaymentMethod to attempt to fulfill this PaymentIntent again.
elfin oasis
Gotcha, so seems like the authentication challenge wasn't completed successfully.
quick girder
The expired card message threw me though
What's that about?
Its on the charges object in the event
elfin oasis
Ah, that's from the first payment attempt.
The Invoice was created and a payment was automatically attempted, which failed due to an expired card.
Then another payment was attempted from the customer portal, which required customer authentication be completed. That authentication was later failed, so the previous Charge was left in place.