#tristanoneil_best-practices
vivid tapirBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1249803799183228978
đ Have more to share? Add details, code, screenshots, videos, etc. below.
modest perch
Good question. Finding the docs with best practices. There are a couple details to keep in mind for implementing new payment methods
Are there specific things around security that you are trying to understand about that setup?
scarlet seal
Mostly just trying to make sure we don't miss anything.
or rather anything obvious.
modest perch
Okay the two main things that I am finding are that you need to set the iframe's allow attribute to payment * to give the iframe access to the browser payment API
https://docs.stripe.com/payments/accept-a-payment?platform=web&ui=elements#web-collect-payment-details
And you need to register both your iframe and page's domain for Apple Pay to work
https://docs.stripe.com/payments/payment-methods/pmd-registration?dashboard-or-api=api
We do support this flow, but having an iframe within an iframe can add a lot of complications and this flow isn't utilized much, so when enabling new payment methods there are sometimes issues with extra configurations like this that are needed.
scarlet seal
Ok, this is helpful. Thanks!
modest perch
Of course, I am not finding tips or common issues with this iframe setup at the moment. Definitely let us know if you have any other questions or if you run in to strange behavior when trying to add new payment methods