#jess_paymentelement-googlepay
still flaxBOT
đ 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/1278851362456866836
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
normal raptor
@high sentinel there can be many different things that can disable GooglePay.
Not using HTTPS, having GooglePay disabled as a payment method in your Dashboard, not having the domain registered (see https://docs.stripe.com/payments/payment-methods/pmd-registration) and other things.
jess_paymentelement-googlepay
rapid magnet
we are using https, enabled googlepay as a payment method in our dashboard's wallet and registered the domain
When the endpoint v1/elements/sessions return the object that shows google_pay_preference as disabled, where is it getting that from?
normal raptor
it's purely internal, you'll have no way to debug this on your own further. Can you give me an exact PaymentIntent id pi_1234 so I can have a look?
rapid magnet
sure, one second
The paymentIntent creation is done by another team that's out for the day currently. Is there other information I can provide?
normal raptor
You are seeing the exact error right? So you should be able to find the exact PaymentIntent id used to render PaymentElement right?
It is possible you are not creating a PaymentIntent upfront and use our "deferred intent" integration where you render PaymentElement without a PaymentIntent's client_secret in which case I'd need to know
rapid magnet
Yes, we are not creating the paymentIntent upfront, we are creating the paymentIntent after payment collection from the payment element. We do not pass in payment intent client secret into the payment element
normal raptor
Okay, so can you share
- exactly how you initialize/load PaymentElement
- A URL where I can see the issue
rapid magnet
We load stripe using the stripe public key and we set up the elements instance using the component and providing it the options of mode = payment, paymentMethodCreation = manual and the related amount and currency
normal raptor
please share exact code instead, much easier to help you debug. We're all developers on my team
rapid magnet
okay, I am not allowed to share too much of the code but I can provide the options we used to initialize the elements component and the payment elements component
would that be whats crucial to know
normal raptor
there's not much that would be secret about the code. Unfortunately we can't really help without actionable details I'm sorry
still flaxBOT
normal raptor
At this point I'd recommend contacting our support team directly: https://support.stripe.com/contact and sharing detailed step by step instructions on how to reproduce the issue on your website end to end. They can also look at your Stripe account, the logs and narrow it down
But I don't think we can help in Discord with so few details
rapid magnet
I see, thats a good idea. Thank you!