#trokas_code

1 messages ¡ Page 1 of 1 (latest)

spice copperBOT
#

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

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

glad bobcat
#

hi there!

#

well the error message is pretty clear:

You cannot confirm this SetupIntent because it has already succeeded.

#

you need to update your code to make sue users can only click on the button once.

spice copperBOT
distant frost
#

Ok I see. In the Dashboard where can I find what it was created? Can I delete also, or will this create problems?

real trail
#

hi! not sure what you mean by "what it was created". And you can't delete a SetupIntent object like this, not sure if that answers the question

distant frost
#

Let me explain to you. For a user for example test@gmail.com I tried to run the script that I provide earlier. Something went wrong, I do not know what and after that I received error 400 for the reason soma answered. My question is can I re do the process and try it again, or I have to delete something from the dashboard?

#

Also I am using a test card here and my test keys. This is ok right? not causing any problem?

real trail
#

Something went wrong, I do not know what and after that I received error 400 for the reason soma answered
what happened is you clicked the button once, called confirmSetupIntent, that succeeded, and then either you called confirmSetupIntent another 10 or so times, or the user clicked the button multiple times. Hard for us to say but should be something you can debug in the code.

Technically you don't have to redo anything. The call to confirmSetupIntent succeeded and you have the outcome you wanted, it's just that after that, you tried again multiple times after it already succeeded.

distant frost
#

Ok got it. I refreshed the page, open inspect, made one click and I found this

Request URL:
https://api.stripe.com/v1/setup_intents/seti_1QMpHO4WhyiLEhnidDy6AXQ8/confirm
Request Method:
POST
Status Code:
200 OK
Remote Address:
34.241.202.139:443
Referrer Policy:
strict-origin-when-cross-origin

and after a little bit

Request URL:
https://api.stripe.com/v1/setup_intents/seti_1QMpHO4WhyiLEhnidDy6AXQ8/confirm
Request Method:
POST
Status Code:
400 Bad Request
Remote Address:
34.241.202.139:443
Referrer Policy:
strict-origin-when-cross-origin

Is this a normal behaviour? To have two confirms with one one click. Take into consideration that my js code only runs once. I debug it

real trail
#

if can only really happen if your code is calling confirmCardSetup twice, I would say

distant frost
#

The same feature, in the live enviroment with a real card worked correctly. Does maybe 3d secure cause this problem. I used the test card 4242 4242 4242 4242