#sricar09_docs
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/1384619671650570251
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello
It's deprecated but it should still work
We don't actively block it because we know a lot of integrations are still using it
So there is likely some other reason behind it not showing up on your test site
We haven't made changes to the integration yet. The payment request button was rendering on our staging environment yesterday. Yet now when we visit it, we only see the following in the console
[Stripe.js] You're using a legacy wallets integration.
We released an improved way to boost conversion and integrate with wallets including Apple Pay, Google Pay, Link, and more. https://docs.stripe.com/elements/express-checkout-element/comparison
Learn how to upgrade your integration: https://docs.stripe.com/elements/express-checkout-element/migration
Hi, taking over as my teammate needs to step away. Let me catch up.
Hm, it works for me, I just tested it on my test integration I have with this legacy product
Thank you for sharing, unfortunately we did not make any code changes to the integration and we aren't seeing this behavior. We can continue to review but there isn't an error, just the console message I shared above. Is there any place available to subscribe to announcements for JS changes for reference?
You can sign up for developer updates here: https://docs.stripe.com/development. You should see 'Sign up' at the bottom of the page.
That message you shared should be for warning only to let you know that it's legacy and I see the same on my test page that it working as well
I can share a link to our product via dm so you can see the issue.
Because the button won't display on our test page, it'll only show the warning
Yes, we are not seeing this behavior
Can you share your test URL so I can attempt to reproduce that using your page?
Without being able to repro, it's really hard to debug
Yes, I will send you a message on this. I prefer not to share the link in the thread
How can I send the link without sharing our product information in the thread?
if the products are behind a log in, you can share your test login details here. Could you update the product information for something random since it's in test mode instead?
The page isn't behind a login. We're an enterprise customer, so it feels like it would be ideal to be able to share our test page where it isn't publicly searchable. can I delete my message?
I see that I can. I'll share it here
Sounds good
Are you able to see the Gpay button here?
Ok. That's good. It's the problem between chair and keyboard then. It's weird, folks in the team can't see it either. Cool
Do they have a valid card in their wallet?
I had a real card added to my wallet
If I remove it, I do not see it
Yeah, I was using the google test cards. It was working for me, but I'll see if that changed
maybe something happened there with their test wallet cards
Ohh, maybe
Yeah, I think that's what happened mostly likely. I've only ever used the google test cards
I think with non-legacy products, the test suites would work: https://docs.stripe.com/google-pay?platform=web#test-google-pay
Since this is a legacy product, it might behave differently
Glad we can confirm it's working
Do you want me to delete the screenshot? I made sure to only include what is pertinent and not share any URL data