#jrserqung_paymentintent-confirmerror

1 messages ¡ Page 1 of 1 (latest)

worthy flumeBOT
#

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

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

dark fractal
#

@nova oxide do you have a lot more specific details about what happened, what the exact error was, what they saw, what they did before/after? That PaymentIntent for example was confirmed once but updated many times

nova oxide
#

So from what the customer told us the scenario is the following:

  1. The customer has entered the card details
  2. Payment has been taken by Stripe, but the message of "unexpected error occured" came up so the customer has never been redirected to the "confirmation page"
  3. Customer tried to refresh the page and an other error occured with status of 400, but that is due to the fact that at that point the payment was succeeded so the amount cannot be updated which is normal.

The whole issue is related to the fact that the customer wasn't redirected, but the payment did go through.

dark fractal
#

jrserqung_paymentintent-confirmerror

#

Gotcha, so that can happen sometimes for example if there's a network error. So they press pay, we confirm the payment on our server but while we do that they lose their connection so they never get redirected. That's unfortunately something that is expected to happen when you accept online payments

#

In your code you should have received some error client-side since the redirect didn't happen. Usually it's the same path as when the card is declined

nova oxide
#

But let's assume there was a network error, in that scenario would it be normal for the customer to receive the "unexpected error occured" message?

#

This might just be an edge case, just wanted to see what your opinion on

#

is*

dark fractal
#

that error is the generic error we display when we don't know what happened so I think it's reasonable

nova oxide
#

That's fine then. Thanks a lot for the help with the little info I could provide.