ben-jamin-87_unexpected

[heavy sleet]

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

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[foggy glen]

Yeah this looks like a decline from the card/bank I'm afraid. Unrelated to 3DS/auth

Your customer should speak to their bank

[feral raven]

Thanks - so setting up a setup intent against the customer record, to replace the existing payment record is unlikely to resolve this? We also found it a little odd that stripe where raising two charges when we attempted payment?

[foggy glen]

so setting up a setup intent against the customer record, to replace the existing payment record is unlikely to resolve this?
Outcome is unlikely to differ with the same card details. If you look at the charge.failed event you can see the network_decline_code and with a Google search you'll see the 'reason' they returned to us

We also found it a little odd that stripe where raising two charges when we attempted payment?
Totally normal really. Each payment attempt that is declined will generate a new Charge object

[feral raven]

Cool, thank you - wanted to check our integration was setup correctly before getting back to the customer.

[foggy glen]

Yeah seems fine overall

[feral raven]

Great, thanks 👍