<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Unpaid Orders in Restaurant Operations</title>
    <link>https://community.toasttab.com/t5/restaurant-operations/unpaid-orders/m-p/16503#M6904</link>
    <description>&lt;P&gt;I understand but there needs to be a solution for the Merchant rather than incurring thousands of $ in lost uncollectible tabs and orders. What is the TOAST Solution?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 25 Aug 2025 17:42:26 GMT</pubDate>
    <dc:creator>lmbc</dc:creator>
    <dc:date>2025-08-25T17:42:26Z</dc:date>
    <item>
      <title>Unpaid Orders</title>
      <link>https://community.toasttab.com/t5/restaurant-operations/unpaid-orders/m-p/16498#M6901</link>
      <description>&lt;P&gt;We have several hundred $ each week in uncollectible tabs that are the result of us doing a $25 Pre-Auth at Order then the order ends up being $100 and at closing the card declines. Why cant TOAST let us retry the card on file until it goes through? This is a major flaw in the card processing system imho. Our orders are placed at the bar or QR code from tables. We do no have servers closing tabs at table service.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Aug 2025 10:57:33 GMT</pubDate>
      <guid>https://community.toasttab.com/t5/restaurant-operations/unpaid-orders/m-p/16498#M6901</guid>
      <dc:creator>lmbc</dc:creator>
      <dc:date>2025-08-25T10:57:33Z</dc:date>
    </item>
    <item>
      <title>Re: Unpaid Orders</title>
      <link>https://community.toasttab.com/t5/restaurant-operations/unpaid-orders/m-p/16499#M6902</link>
      <description>&lt;P&gt;Thanks for reaching out to the community! This is a great question, Toast is PCI compliant, which means we do not store full card details beyond what is visible in the transaction details. Therefore, if a payment is denied, we cannot re-process the payment or retry the card on file. This is a limitation of the system to ensure security and compliance with payment processing regulations.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Aug 2025 14:32:08 GMT</pubDate>
      <guid>https://community.toasttab.com/t5/restaurant-operations/unpaid-orders/m-p/16499#M6902</guid>
      <dc:creator>Rob</dc:creator>
      <dc:date>2025-08-25T14:32:08Z</dc:date>
    </item>
    <item>
      <title>Re: Unpaid Orders</title>
      <link>https://community.toasttab.com/t5/restaurant-operations/unpaid-orders/m-p/16503#M6904</link>
      <description>&lt;P&gt;I understand but there needs to be a solution for the Merchant rather than incurring thousands of $ in lost uncollectible tabs and orders. What is the TOAST Solution?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 25 Aug 2025 17:42:26 GMT</pubDate>
      <guid>https://community.toasttab.com/t5/restaurant-operations/unpaid-orders/m-p/16503#M6904</guid>
      <dc:creator>lmbc</dc:creator>
      <dc:date>2025-08-25T17:42:26Z</dc:date>
    </item>
    <item>
      <title>Re: Unpaid Orders</title>
      <link>https://community.toasttab.com/t5/restaurant-operations/unpaid-orders/m-p/16504#M6905</link>
      <description>&lt;P&gt;some sort of adjusting pre-Auth that raises as the customer keeps spending more?&lt;/P&gt;</description>
      <pubDate>Mon, 25 Aug 2025 17:43:20 GMT</pubDate>
      <guid>https://community.toasttab.com/t5/restaurant-operations/unpaid-orders/m-p/16504#M6905</guid>
      <dc:creator>lmbc</dc:creator>
      <dc:date>2025-08-25T17:43:20Z</dc:date>
    </item>
  </channel>
</rss>

