#jose-fernndez_unexpected
old mulchBOT
đź‘‹ 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/1464252972358828054
đź“ť Have more to share? Add more details, code, screenshots, videos, etc. below.
fluid sage
You just need to select any purchase option and continue. On the next form, fill in all the fields and then press the button with the Google Pay or Apple Pay logo.
keen egret
I do see Google Pay in Chrome:
for Apple/Google Pay to appear, you need to make sure you are using a compatible browser, and have a card saved in your wallet.
fluid sage
keen egret
can you check if you follow all requirements listed here: https://docs.stripe.com/testing/wallets?ui=payment-element#device-requirements
fluid sage
Have you been able to verify Apple Pay?
keen egret
yes:
so your Stripe integration is fine!
the issue is with your device/browser/wallet.
fluid sage
In the test environment, Google Pay shows up, but not in the Elements modal. I don’t understand why this is happening or why it wasn’t an issue a few days ago.
Express checkout too
keen egret
strange, having a look
fluid sage
And what’s even stranger is that I had tested it before and it was working fine.
keen egret
are you using Goole Chrome?
fluid sage
yes
keen egret
if you open this page, you see Google Pay? https://docs.stripe.com/testing/wallets?ui=payment-element
but you don't see it on your own website?
fluid sage
yes
in console:
Framing 'https://pay.google.com/' violates the following report-only Content Security Policy directive: "frame-ancestors 'self'". The violation has been logged, but no further action has been taken.
keen egret
I don't see this error on my end when visiting your website. so that's interesting.
old mulchBOT
cedar flume
Hey there, stepping in for soma who had to step away, but i observe the same behaviour myself. Google Pay appears on your page after i enter an email etc to get to the payment element.
fluid sage
It’s strange because it used to show up for me before, but now it doesn’t. How can I test Apple Pay on Windows and Chrome to see if it’s working?
cedar flume
That wont appear, the cross browser (chrome) support for apple pay is only on apple devices currently
eg, macos, ios
I see some indication of using checkout sessions in your code, is this a custom checkout integration, or if not can you share how you initialize elements?
fluid sage
It works for me locally using ngrok, but not in the test environment. The concern is that if it fails for some users, our integration could be rejected.
cedar flume
What do you mean rejected?
fluid sage
What I meant is that if, say, it fails for some users, then they might not allow this type of integration internally, because it could lose credibility.
I’m handling it by creating a Checkout Session from the backend and then using a CheckoutProvider on the frontend. I’ll share the modal code with you.
But I’m not sure if it’s related to security. I mean, like I showed you earlier, the console is throwing a warning, and I don’t know if that might be the reason why the payment method isn’t showing up for me.
One more thing: on the frontend I’m working with TanStack Start.
cedar flume
I don't think its security or it wouldnt work for us either
Since you're using custom checkout, have you tried opening the elements inspector? It might include helpful diagnostics here for google pay/apple pay
click that "stripe" button in the bottom right corner
fluid sage
Yes, but I didn’t see any relevant information. I don’t get anything like an error or a warning telling me something is wrong. Everything seems fine.
If you want to ask me to check anything or follow some steps, feel free.
I’ve added these lines (as shown in the image), and it’s been fixed.
cedar flume
The CSP rules?
fluid sage
{
httpEquiv: "Content-Security-Policy",
content: [
"frame-src 'self' https://js.stripe.com https://hooks.stripe.com https://pay.google.com https://apple-pay-gateway.apple.com",
"connect-src 'self' https://api.stripe.com https://*.stripe.com https://pay.google.com https://apple-pay-gateway.apple.com",
].join("; "),
},
yes
cedar flume
Interesting, I never got those same CSP errors. THat's quite odd, but I'm happy its working for you!
fluid sage
đź‘Ť
