#mhdev
1 messages · Page 1 of 1 (latest)
Hello, do you have your issue narrowed down or are you still unsure of what exactly might be causing this?
And can you send me the ID of connect account you have been trying to use here? I can check to see if your apple pay domains are set up properly here
Hi @modest terrace! The issue is that the apple pay option isn't showing up. We have added the domains. The connect account id: acct_1LABHTIHkg9cPLLo
If you hit this url can you debug and let us know if you see anything from your end? https://sawtheexperience.com/tickets/?payment_secret=pi_3LulqfIHkg9cPLLo1z0NJeTf_secret_JyV67DamzdlhzJOVIk3dPqADv
Still looking in to this. I see that the domain is registered properly and the accounts are connected properly. Also seeing GPay in Chrome so wallets should show up if set up. Trying to think of what the other potential breaks here are
Ok, thanks. Yeah, we would love to get a solution for this. Been working on it for a while now and can't figure out the root cause
thanks for helping us debug
Of course! Still looking. It looks like you are instantiating Stripe.js properly client side as well. You definitely seem to have all the bases covered that I normally check. Trying to look in to what else might be preventing the button from showing here
yeah, we are using loadStripe with the connect account id.
is it something to do with iframe?
do you see any errors in your console?
related to iframe. i dont see any but a stripe dev said they saw some a few days ago
Don't see iframe errors at the moment, just your debug log lines. Is your page using iframes other than the one that Stripe adds as part of the payment element?
yeah, the payment element is inside a widget/iframe
if you search for 'widget-onthe-stage-iframe' in the console
Thank you, double checking that that pattern works. It should because the payment element itself is an iframe but I know that can affect things
Ok, thanks
Definitely should work as far as I can see in my testing and it looks like the domain the iframe is going to is registered properly as well.
As a quick test can you try adding the PaymentElement or payment request button directly to that page?
hmm. we dont have access to that page. our iframe is embedded in our clients site
just to confirm, we dont need the payment request button if we are using payment element? it should show automatically if we use the card payment method, right?
Correct, no need for it, that was just a debugging thing. And yes should show up as long as you include card payments unless you specifically disallow wallets
This would be the setting that could disable Apple Pay but not google pay. I can't see your relevant js code to check that it isn't there but I am guessing it isn't https://stripe.com/docs/js/elements_object/create_payment_element#payment_element_create-options-wallets
Trying to think on that.
Do you know if there is any URL I can use at that ots-widget URL that would allow me to see the payment element directly?
Also I am guessing this is a pattern that is already working on other sites that your widget is on?
We don't have it set to never for apple pay.
Try this link - https://widget-customer-immersive-test.surge.sh/
Not yet. We recently moved from using stripe checkout session to paymentintent/payment element. Before apple pay used to show up with checkout session, but not we have the problem that apple pay is not showing up when using payment element. It is a big blocker for us atm
Thank you. That site doesn't have that button either but it looks like the apple pay domain isn't registered for the test account on that site so that is probably why that is not showing up there.
At this point I think I will need to take this to my colleagues for a more in depth investigation. Can you write in to our support team about this and then DM me your email? I can grab the email and get back to you with what we can find
Can you let me know if you see it?