#Maxv
remote mango
feral sleet
👋 happy to help
I'm not sure what the behavior is with Incognito mode to be honest
instead of using Incognito mode I would rather test with different profiles on chrome
brave junco
Hi there 👋 jumping in as my teammate needs to step away soon. It is expected for Google Pay to not be displayed when using incognito mode. Doing so blocks access to your Google Pay wallet, so our checks that run to ensure you have a card already in your wallet fail and we don't display the Google Pay option.
slim owl
Hey Tobi and Tarzan,
but in the API it sates that using the Wallets parameter will show the button even if there is no payment
from the API:
By default, the Express Checkout Element displays all payment methods possible as a result of your Dashboard configuration.
However, wallets like Apple Pay and Google Pay have additional configurations that Stripe can show them. These wallets show when the customer is using a supported platform and when we determine it's advantageous for your conversion. This is the auto behavior, and it's the default choice for all wallets.
If you want to always show the wallets when the customer is using a supported platform, you can set its property in wallets to always.
If you don't want to show a given wallet as a payment option, set its property in wallets to never.
brave junco
In short, you should not use incognito mode for wallets. In my experience it does not work well, for instance with Apple Pay in private windows I see the Apple Pay button displayed even if it is not configured correctly.
When setting them to always, do they appear as expected in non-incognito/private windows?
slim owl
Didn't try in non-incognito as I have a wallet there. will try to remove it.
Isnt private window is an incognito window?
Ok it works in non incognito window.
Thank you!
Any chance you can help me with the other questions?
brave junco
Yup, looking.
For the second question, I agree that I'm not seeing a way to disable the element after click, but clicking on the buttons while the browsers payment widget is open is not doing anything. Are you seeing different behavior where clicking on the buttons while the widget is open is resulting in an action being taken?
For the last question, I don't recall offhand if those wallets require a redirect when they complete, but you can try setting redirect to if_required when confirming the Payment Intent. If the wallets don't require a redirect, then that should avoid one happening allowing you to handle the redirect as you like:
https://stripe.com/docs/js/payment_intents/confirm_payment#confirm_payment_intent-options-redirect
slim owl
When the modal is open the behaviour is ok, but after the modal is closed because the payment succeded it sometimes takes a few second to redirect to a new page, and in that time the button is clickable(nothing will happen as we are protecting vs double payment) but it makes a weird UX.
I tried with is_requred, and unfortunately it still requires the return_url param
brave junco
Ah, apologies for not being clear, return_url will still be required, but your customer may not be directed there.
Hm, I see what you're saying about the buttons, and I'm not finding a good way to disable them so far since they're in an iframe that you can't really interact with. Thank you for flagging this, I'm going to raise this feedback to the appropriate team as I think it is something we could improve upon.
slim owl
Got it, I maybe I will be able to cover it with glass pane or something as a walkaround.
Thank you for your help!
brave junco
In the meantime, a possible approach would be to unmount the element on successful payment.
slim owl
Hmmm so it will remove it entirely? I could propose this to our product manager
brave junco
Yup, it completely removes the element and buttons within it from page. It doesn't destroy the element though so it could be remounted if wanted.
https://stripe.com/docs/js/element/other_methods/unmount
slim owl
got it.
Thank you!
brave junco
Any time!
slim owl
Another question, can you think of a reason that the express checkout wont be clickable in mweb?
brave junco
Not offhand, I'm not familiar with what mweb is.
slim owl
Mobile Web, opening the browser on mobile
brave junco
Hm, my suspicion would be that the device isn't fully set up for the wallet trying to be used, but I'm not confident about that. Are you seeing any alerts thrown or errors printed to console when you try to use it?
slim owl
no no errors.
btw if I try to open the elements here:
https://stripe.com/docs/elements/express-checkout-element#supported-browsers
they are also not clickable in mweb.
Only the link is clickable:
Ok so it seems that this is the case when im trying to simulate mweb on Desktop. Looks like on a real phone it works.
So no issues, sorry
brave junco
All good, glad to hear you got to the bottom of it!