#daken-elements

1 messages · Page 1 of 1 (latest)

sacred lake
#

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

runic edge
#

Card Element

#

pi_3LP0b2CaIcMMXsqa1UxFIj3P
pi_3LP2GbCaIcMMXsqa0JqdOOBH

#

The first returned an error, but in reality it went OK, so the client did the second payment

sacred lake
#

Could you elaborate on what error the first one returned?

runic edge
#

No, they do not say the error, it's a generic one for the things we heard

sacred lake
#

So you can't reproduce, but some customer tell they see an error?

#

From Stripe log I don't see any error..

runic edge
#

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

sacred lake
#

Can you post your js code around the place of confirmation

#

It's difficult to diagnose without a screenrecord

runic edge
#

Yes

#

There you have

#

Its quite simple, if there is an error, then just show the error, if not, just redirect

sacred lake
#

Um, so where is the logic for

so the client thinks that the payment failed and tries again

runic edge
#

if(result.error)
props.SetError()

#

setError is an string that we show as a WARNING in the form

sacred lake
#

Yeah but that only shows. How does it try again?

runic edge
#

The client refresh the page and try again

sacred lake
#

Okie that's not something done automatically by your code then

runic edge
#

No no, the client sees the error and just tries again

#

but he doesn't know the frist payment was successful

sacred lake
#

Yes I know, so it's from a customer action, based on your site display

#

Do you have any kind of timeout timer?

runic edge
#

No timeout

#

I guess the default 15 seconds

sacred lake
#

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

calm wren
#

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

runic edge
#

We can not reproduce this, we can only see our logs and people complains

calm wren
#

What do you see in the logs?

runic edge
#

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

calm wren
#

Are you actually logging result.error anywhere?

#

You need to debug this further on your end, really

runic edge
#

Its only happening with stripe, not amazon pay, paypal or braintree, thats why im asking

#

But we'll look it further

calm wren
#

You should log those

#

How do you know that the if (result.error) block is being triggered?