#daken-elements
1 messages · Page 1 of 1 (latest)
Hi, it would need a bit more detail on the issue. Do you have an example Payment Intent Id? pi_xxx
Also, are you using Payment Element or the old Card Element
Card Element
pi_3LP0b2CaIcMMXsqa1UxFIj3P
pi_3LP2GbCaIcMMXsqa0JqdOOBH
The first returned an error, but in reality it went OK, so the client did the second payment
Could you elaborate on what error the first one returned?
No, they do not say the error, it's a generic one for the things we heard
So you can't reproduce, but some customer tell they see an error?
From Stripe log I don't see any error..
We knoe this is an error because this month we have 36 cases
And last month arround 40
And all customers say the same: "The website said that there was an errro with the payment, but I got charged"
And we dont have any logic, if the confirm is OK we redirect, if not, we show stripe error
Can you post your js code around the place of confirmation
It's difficult to diagnose without a screenrecord
Yes
There you have
Its quite simple, if there is an error, then just show the error, if not, just redirect
Um, so where is the logic for
so the client thinks that the payment failed and tries again
if(result.error)
props.SetError()
setError is an string that we show as a WARNING in the form
Yeah but that only shows. How does it try again?
The client refresh the page and try again
Okie that's not something done automatically by your code then
No no, the client sees the error and just tries again
but he doesn't know the frist payment was successful
Yes I know, so it's from a customer action, based on your site display
Do you have any kind of timeout timer?
I don't really know. The Payment succeed on our log. I can only say your API version is pretty old (2016). So maybe it's a good time to upgrade to latest version (2020) and try out our new Payment Element
Hey, is there somewhere where we can reproduce this issue? This behaviour does sounds strange, but nothing seems out of the ordinary from our end
We can not reproduce this, we can only see our logs and people complains
What do you see in the logs?
Our database, that people is using the same card after getting an error from stripe
cart*
With 10 minutes of difference
Could it be that in some cases the confirmCard function returns a false error?
Or stripe network is unreachable but in some way the request go though
Seems unlikely as the logs would reflect that with an error
Are you actually logging result.error anywhere?
You need to debug this further on your end, really
Its only happening with stripe, not amazon pay, paypal or braintree, thats why im asking
But we'll look it further
result.error will contain an API error object which will have more details about the error that's being thrown: https://stripe.com/docs/api/errors
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
You should log those
How do you know that the if (result.error) block is being triggered?