#ali-shan_error
1 messages Β· Page 1 of 1 (latest)
π 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/1422458092049661992
π 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.
- ali-shan_error, 21 hours ago, 9 messages
Hi there, is there a public URL that I can visit and reproduce the issue?
https://Rottenhand.com
This is the link and website is currently in the testing mode first time you use the invalid card (real card with wrong password) this gives error that you can't use the real card in testing mode after this you use the any testing card then this happend.
- after this you reload the page and then use the testing card again this time this works. Thanks
Two shirts. Zero compromise. Ethically made in India with fair wages. Built to last decades, not seasons. Why buy garbage when you can buy forever?
I have shared the screenshot in this chat
#dev-help message
HTTP 400: - {"errors":[{"message":"Cannot query field \"settleStripePayment\" on type \"Mutation\".","locations":[{"line":3,"column":11}],"extensions":{"http":{"status":400,"headers":{}},"code":"GRAPHQL_VALIDATION_FAILED"}}]}``` I encountered this error after clicking the "Place Order" button
There was a developer was fix the issue may be he did some changes, let me revert there changes, and i will let you know,
sorry for late , kindly check the issue again, now this issue happing.
Let me take a look
"We ran into a problem with payment!
Failed to initialize payment. Please try again."
The payment element isn't showing at all
I saw the same error in browser console
when this happend? first time or second time?
can you clear you cache and try it , i try this and then asked you to check this
did you fill the above information
Yes
I was able to click the button before, and that's how I got the error
But now I can't even click on the button
please recheck the above form. may be you are missing something.
I have them all filled up
i think you have added the Test in the place of the State.
you can fill the form as above i have shared the screenshot
this works when i use the testing card first time. but i face the issue when i use any invalid card (real card with wrong password) this give you error that you can't use the real card in testing model after this you again fill the form with correct testing card this time this give you can error
Hey! Taking over for my colleague. Let me catch up.
Before I go. @merry bolt This is expected because you can't use actual card in test mode
You can only use test mode cards (https://docs.stripe.com/testing) in test mode
first time it give me error that you can't use the testing card that good but why second time it give me error even i use the testing card,
you can also see that this highlight the fields also
What testing card are you testing with here ? I see none
4242 4242 4242 4242
if i reload the page and first time i use this card then this works, but i first time i use the invalid card and then use this then error comes
OK, let me take a look at the page you shared
Yeah, I see the same issue. The checkout loads for a while and then the page refreshes and shows this error.
It looks like you may be calling confirmPayment() in the JS when the page loads, if you're getting this error
you can check this, i fill the form and then submit.
here is code snipt which i am using.
hey there, taking over from my colleague and just getting caught up on this thread at the moment
looking at your code, it seems like your integration is calling confirmPayment twice , when an invalid card is used, and the page is refreshed - I'd recommend debugging to check why this is happening
also, are you able to provide a version of the site with Javascript non-minified - this will allow us to add break points to debug and see when the confirmPayment is called
i have added the console logs on the live site please check them maybe that will help
thanks! just tried another attempt, and this time the validation error isn't showing when the page reloads
could you try again and confirm if you're still facing the same issue?
in first attempt this works, i already told many time that if i use the invaild card first time and then use the valida card this this happend, mean you use the real card(with wrong passwork) and then use the real (testing card) then this happend
the file i shared with you is older , sorry for that , there is new code in which i am facing the issue
I've just tried another reproduction and this was the PaymentIntent generated: pi_3SCzvQ5TAqA4yxs40iNZI66O
checking the logs, I can see a few points:
-there are two calls to update the PaymentIntent's amount
-there is one call to confirmPayment (with the 'live' card)
-there is no second call to confirmPayment (i.e. when trying with the Stripe test card, after the page loads)
can you share any context around why the second attempt to pay did not result in a confirmPayment call?
since this thread has been ongoing for quite a while, it might be best to open a case directly with our team
I'm going to create a link for you to open a case with us, and from there you can work with our team via email to debug this
Hello @merry bolt, we have sent you a direct message, please check it at https://discord.com/channels/@me/1422523083188867101
- πThe message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.