#numan_unexpected

1 messages · Page 1 of 1 (latest)

stone lindenBOT
#

👋 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/1301156224254869667

📝 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.

autumn sinew
#

Why does the payment not automatically retry when it’s blocked by the bank, even after the user updates their card?
Depending on the decline code, the bank/issuer may recommended that we do not retry the payment
Is there a specific way to reproduce this scenario in test mode (e.g., specific card types or decline codes I can use to mimic a blocked payment and trigger this exact condition)?
Not sure if any of our decline cards will simulate that: https://docs.stripe.com/testing#declined-payments

Test card numbers

Use test cards to validate your Stripe integration without moving real money. Test a variety of international scenarios, including successful and declined payments, card errors, disputes, and bank authentication. You can also test non-card payment methods and redirects.

#

If you have an example I can confirm point 1

lament peak
#

yes on subscription showing this error

image.png
#

I manually retried it and it worked

autumn sinew
#

An ID, please. Screenshots aren't useful in this context

#

(you can see why we didn't re-attempt automatically in the tooltip)

#

If the payment was blocked by the user's bank and they then update their card, the payment does not automatically retry upon card update.
This is expected behaviour, yes. You'd need to manually re-attempt the payment whilst the customer is on-session by confirming the invoice intent

lament peak
#

Are you referring to a subscription ID or any other?

autumn sinew
#

The in_xxx ID of the invoice

#

But I think we know the answer here already as I've stated

lament peak
#

"id": "in_1QC6RaGJRTFjj5zfOpxE5eSC",

image.png
autumn sinew
#

Sure, so the payment failed and we were advised not to retry it

#

Your customer provided a new card, but that won't resume automatic retries – you need to manually retry the payment