#sb_custom-checkout-google-pay
final skyBOT
👋 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/1367120432934817812
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
quasi mural
hi there!
copper cloud
Hi Soma 🙂
quasi mural
can you share a link to your payment page?
copper cloud
final skyBOT
quasi mural
do I need a login/password? can you share one?
copper cloud
Yes sure,
email:demo@stripe.com
password:demo@stripe.com!
We prepared a specific cart
quasi mural
I'm guessing you expect the Google Pay button to appear here?
copper cloud
Absolutely
Please allow me to remove the "Jesus Campos" product to prevent unwanted notifications.
With safari, apple pay works like a charm
solemn tiger
Hi there 👋 I'm jumping in as my teammate needs to step away. Bear with me a moment while I catch up here.
Just making sure I'm looking at things correctly, this is an Express Checkout Element integration, right?
I think I see the problem, just need a moment to confirm.
copper cloud
yes
solemn tiger
Looking at the Element on the page, it looks like it's being initialized with Google Pay explicitly disabled and Apple Pay forced to show.
&publicOptions[paymentMethods][applePay]=always&publicOptions[paymentMethods][googlePay]=never&
Do you use variables to populate paymentMethods.applePay and paymentMethods.googlePay when creating the Express Checkout Element?
copper cloud
we followed those documentations:
const expressCheckout: ExpressCheckout = checkout.createExpressCheckoutElement({
paymentMethods: {
applePay: 'always',
googlePay: 'always'
},
layout: {
maxRows: 2,
}
});
I can share the whole script if you prefer
solemn tiger
Hm, the maxRows aligns with what I see on your page, but the paymentMethods don't. I see that everything but applePay is being set to never.
copper cloud
Can you confirm whether both Apple Pay and Google Pay are visible on your end?
solemn tiger
I only see Apple Pay, because it looks like Google Pay is being explicitly suppressed
solemn tiger
Are you able to reproduce this behavior on a simple one page test page?
And by chance, have you compared this to an Express Checkout Element integration rather than a Custom Checkout integration?
I'm starting to wonder if this is something specific about the ECE within a Custom Checkout flow.
copper cloud
We staged a release using the Custom Checkout integration with Payment Intents. It works as expected in staging, but we’re currently unable to deploy it to production.
And we prefer fix ECE
solemn tiger
I'm sorry, I'm not sure I'm grasping that. Your page is currently using a Custom Checkout integration right? That would align with the code that you shared above.
Ooohhh, no, the code you shared doesn't seem to be the same code running on your page.
copper cloud
solemn tiger
Wait, maybe it is, maybe I'm moving too fast.
copper cloud
Thats our file
I production we use Express Checkout Element integration but google pay fails
So we prepared a POC with Custom Checkout integration in staging, and google pay works. But we're unable to deploy it in production
solemn tiger
Okay, hang on, I'm a little lost.
The site you shared, is that your production site or your staging site?
copper cloud
production
solemn tiger
Is that site using the code you shared earlier? I'm asking because that code is using Custom Checkout in addition to the Express Checkout Element.
copper cloud
yes
_stripe-express-checkout.ts is actually in production
we've followed this documentation
solemn tiger
Gotcha, so Production is using Custom Checkout+Express Checkout Element, and that's where you're not seeing Google Pay displayed as expected.
Out of curiosity, what changes did you make in what you have staged currently? I'm wondering if maybe that change will give me some insight into what could be going wrong here.
I'm checking to see if a teammate has a test integration like this stood up already that we can do some testing with. If not, I'll stand up my own, just that will take some time.
copper cloud
No, no — Production is using Custom Checkout with the Express Checkout Element. The implementation has been live for 10 days, and everything was working as expected even yesterday!
But since this morning, Google Pay has suddenly disappeared without any apparent reason...
In conclusion, not a single line of code has changed in the past 10 days.
But during our development phase, we explored different approaches, and among them, we prepared a draft using the Express Checkout Element with a Payment Intent.
Since we're comfortable working with the Checkout Session token, we chose to go with the Custom Checkout combined with the Express Checkout Element.
¯_(ツ)_/¯
solemn tiger
Okay okay, I understand now. What was being described didn't seem like it was lining up with what I was seeing, but I have a grasp of the situation now.
copper cloud
Can you explain why the implementation was working yesterday? Was there any update in our codebase or something else that could have caused this?
solemn tiger
Not sure yet
final skyBOT
copper cloud
any news ?
edgy sun
Hi there we're looking into it still
copper cloud
ok
edgy sun
Sorry for the delay, but I do have a colleague looking into this still
I'll let you know when I hear more
copper cloud
ok
copper cloud
ok great, do you think it'll fix today ?
edgy sun
Hopefully
But I can't promise anything
They're actively working on it right now
Actually they said it should be fixed now!
Can you confirm on your side?
Do a hard refresh in chrome (shift+ctrl+r)
final skyBOT