<?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/f57cc658c1904b5f87cc9985aca42052&quot; frameborder=&quot;0&quot; width=&quot;1892&quot; height=&quot;1419&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1419</height><width>1892</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1419</thumbnail_height><thumbnail_width>1892</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/f57cc658c1904b5f87cc9985aca42052-2b3f808ad34f98b9.gif</thumbnail_url><duration>279.701</duration><title>Fixing Failed Payments After Card Updates</title><description>This Loom explains how to handle PayPal or payment method updates for customers in Spiffy and Stripe after a payment change or failure. The presenter checks the customer’s Grow account, reviews the most recent Stripe payment, and sets the correct card as default because Spiffy may not retain the updated card and Stripe defaults can revert to a non-default card. They then remove older cards so only the correct default remains to avoid repeated months of failed payments. They repeat the same verification for another customer, confirming a card proactively changed and noting the existing default card is set to expire 3 33 and will likely be expired by the next charge.</description></oembed>