{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/baf6038105c342bb9a75da565e9bb099\" frameborder=\"0\" width=\"1112\" height=\"834\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":834,"width":1112,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":834,"thumbnail_width":1112,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/baf6038105c342bb9a75da565e9bb099-11e785741f94ebfe.gif","duration":135.873,"title":"Stripe Apple Pay - Cross domain issue","description":"In this video, I discuss an issue we're experiencing with our widget that allows users to embed our registration platform on their sites for ticket sales. Recently, with the release of Safari 17, we've been able to accept Apple Payments using the Allow Payments attribute on an iFrame. However, I've noticed a cross-domain issue where Apple Pay only appears when the domain is registered with our Payment Gateway. I need your insights on why this might be happening, as it seems to have worked previously. Please take a look and share any thoughts you may have."}