#barkman_unexpected
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/1374743018997022730
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Here's it working on direct load (https://widgets.universe.com/682dd5cc71da7e002debdb8d)
Here's it NOT working when loading from our event display page (https://www.universe.com/events/test-gbp-tickets-197RKX)
Hi ๐ taking a look
Hey toby! Good morning!
So are you iframing one page on another page?
Here are the domains registered on our GBP acc't
Yes we are
I feel like I'm missing something obvious
Gotcha, and are you setting allow="payment" for that iframe?
There are also limitations with what versions of Safari support Apple Pay in an iframe like that, but I don't see it on your page either and am pretty sure I'm using a new enough version to get access to this functionality.
https://docs.stripe.com/testing/wallets?ui=payment-element#(apple-pay)-register-all-domains-when-using-iframes
Oooo - it might be that simple. ๐คฆโโ๏ธ
did that allow="payment" markup change recently? Or semi-recently?
I think that requirement came out alongisde the release of Safari 17 that introduced support for Apple Pay in iframes, but I'm not confident about that.
yeah looks like that's in the release notes
Thanks Toby - I'll follow this allow="payment" thread here - sorry, feels like this is an obvious first thing to check!
No worries! It's only obvious to me because I spent months pulling together all the edge cases to build that wallet test page doc ๐
I hope adding that attribute solves this for you, but you know where to find us if it doesn't
Will do, appreciate your time.