#rozig

1 messages · Page 1 of 1 (latest)

lime atlasBOT
hollow fog
#

Hello! Are you literally seeing {SETUP_INTENT_ID} in the URL like that?

frozen charm
#

Oh no, I redacted actual setup intent ID

#

If it is not a sensitive information I can share the actual setup intent ID here. What I want to know is what could be causing the confirmCardSetup() to fail but getting reported as successful on the stripe dashboard

hollow fog
#

Setup Intent ID s are not sensitive. Can you share one of the ones that had the error?

frozen charm
#

yes, here it is: seti_1MX7JBHcEDTg6I86eqyjMUDQ

hollow fog
#

Looking...

#

Hm, looks normal on our end, not seeing any errors.

frozen charm
#

yes, that is what I meant by looking successful on stripe dashboard ..

hollow fog
#

Perhaps the initial confirmation attempt failed client-side and the library automatically retried and it worked?

frozen charm
#

I can confirm that the initial confirmation attempt failed on the client-side and I have an error handling case implemented. Then customer entered their card again and the second time it worked successfully.

#

the error response I sent earlier was caught from the error handling

hollow fog
#

I think you need to add additional logging to find out why the fetch is failing. Is it timing out? Is there some kind of bad response? Is it failing before it even starts for some reason?

frozen charm
#

Can you elaborate on "additional logging"?
This error is caught from the /confirm API call. Is there any browser plugins/addons that doesn't work well with stripe component?

hollow fog
#

There are no popular/common ones that we know of that cause issues. I'm sure there's probably something out there that might conflict, but it's impossible to know for sure.

#

Can you reproduce the issue on demand?

frozen charm
#

I can try, the problem is it is working without any issues in test mode and this specific one is happening randomly so it is kind of hard to find a lead on the root cause

hollow fog
#

Ideally you'd be able to see what happens in the web browser's console when this error appears. That will likely give you the most information.

frozen charm
#

okay thank you. Also by any chance would it be possible to be caused with wrong implementation?

hollow fog
#

If most of your transactions are working correctly I doubt it.

frozen charm
#

I implemented confirmCardSetup() as a hook in react application and when the card information is filled out completely then I am initiating the call with onChange event

hollow fog
#

You're not triggering that with a button press or explicit action from the customer?

frozen charm
#

no

hollow fog
#

I recommend you use a button press or similar to trigger confirmation. That way people can do things like autofill the wrong card, realize their mistake, then fill in the right one before proceeding.

frozen charm
#

the CardElement component provides onChange event and event object has complete property, I am using this property to trigger it

hollow fog
#

Yeah, I strongly recommend against that.

#

The client-side confirmation process should be explicitly triggered by a user action, not implicitly triggered by filling out payment data.

#

Most people use the complete property to enable or show the button that allows you to confirm, for example.