-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ApplePay within an iframe #707
Comments
👋 Thanks for reaching out. I'm genuinely curious: why do you need to load ApplePay within an iframe? Any info on your use case would be helpful, thanks. |
Hi @hollabaq86 . Due to technical reasons and how the project architecture has been designed web app A loads a different web app B (the one responsible of payments) and this payments app is loaded through an iframe. |
Hello @hollabaq86 or any member from the Braintree team, could you tell me if you are actively tracking this issue or if you would have a fix in the roadmap by any chance? thank you |
I have the same problem and issue. Any one got a fix? |
Is there an update on this? I also have this existing issue. |
Looking to get a response from Braintree on this one to. |
We have a solution involving pulling in the braintree and apple pay scripts in the parent page, using Post Messages to communicate between parent page and iFrame, which is working but undesirable. As above, it would be good if we can get some formal docs around this from Braintree. Thanks. |
General information
Issue description
I am trying to test Apple Pay support in an iframe on the latest version of Safari (Apple Pay support in an iframe was added here PR and it was released on September 18, 2023 for Safari 17. Release logs)
Historically, Apple Pay does not work in an iframe. It was updated to work with the
allow=payment
attribute in the above PR.Steps to reproduce:
allow="payment"
attribute added to the iframe.Loading sub domain B in a new window and testing the payment flow has no issues.
Is there any documentation or guide to make this work?
Thank you!
The text was updated successfully, but these errors were encountered: