#djachim_paymentelement-googlepay
1 messages ¡ Page 1 of 1 (latest)
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.
- djachim_code, 1 day ago, 17 messages
- djachim_code, 2 days ago, 9 messages
đ 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/1273342748086243419
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
djachim_paymentelement-googlepay
hum I have never heard of that error before. But also it doesn't make sense to me that you are trying to use the 4242 card. That's our test card on Stripe, it is not compatible with GooglePay. You are supposed to use your real card (which we won't charge)
Ok, I will try a real card.
Is there any difference between using Google Pay on the payment element vs expressCheckout element?
no
Thank you for your help. Using a real credit submitted successfully. I just didn't like the idea of using a real credit card.
yeah it's definitely surprising. But the idea is more that most devs would already have GooglePay with their real card and so we just use their normal account and swap the real card for the 4242 internally in Test mode
definitely a cryptic error that you got though
ok, thanks again