<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/baf6038105c342bb9a75da565e9bb099&quot; frameborder=&quot;0&quot; width=&quot;1112&quot; height=&quot;834&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>834</height><width>1112</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>834</thumbnail_height><thumbnail_width>1112</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/baf6038105c342bb9a75da565e9bb099-11e785741f94ebfe.gif</thumbnail_url><duration>135.873</duration><title>Stripe Apple Pay - Cross domain issue</title><description>In this video, I discuss an issue we&apos;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&apos;ve been able to accept Apple Payments using the Allow Payments attribute on an iFrame. However, I&apos;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.</description></oembed>