<?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>thread Re: customer charged multiple times in Orders, Menu Items, Catalog &amp; Fulfilment</title>
    <link>https://community.squareup.com/t5/Orders-Menu-Items-Catalog/Why-was-my-customer-charged-multiple-times/m-p/221825#M7022</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.squareup.com/t5/user/viewprofilepage/user-id/117350"&gt;@MountainFreak&lt;/a&gt;&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":waving_hand:"&gt;👋&lt;/span&gt; Thanks for reaching out to us here on the Seller Community! Good to hear from you again.&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Sorry for the confusion here. This kind of temporary authorization is something that we see often - especially with customers using debit cards. If an attempt at a transaction is unsuccessful, a temporary authorization will process on the customers statement but will not actually post to the account due to the transaction not going through.&lt;BR /&gt;
&lt;BR /&gt;
While these authorizations tend to fall off of a statement in 24 to 48 hours, your customer can have them removed more quickly by reaching out to their card-issuing bank.&lt;/P&gt;</description>
    <pubDate>Tue, 24 Nov 2020 13:09:00 GMT</pubDate>
    <dc:creator>Joe</dc:creator>
    <dc:date>2020-11-24T13:09:00Z</dc:date>
    <item>
      <title>Why was my customer charged multiple times?</title>
      <link>https://community.squareup.com/t5/Orders-Menu-Items-Catalog/Why-was-my-customer-charged-multiple-times/m-p/221639#M7021</link>
      <description>&lt;P&gt;My retail customer was charged 3 times for one trasaction.&amp;nbsp; She bought the item in the store on Saturday.&amp;nbsp; Her statement on Monday showed she had been charged 3 times.&amp;nbsp; On Monday morning one of the extra charges had been credited.&amp;nbsp; My trasaction and banking history shows only one charge.&amp;nbsp; How can I rectify this extra charge?&amp;nbsp; The money did not go to my account and isn't registering in my POS system.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 20 Sep 2025 11:50:39 GMT</pubDate>
      <guid>https://community.squareup.com/t5/Orders-Menu-Items-Catalog/Why-was-my-customer-charged-multiple-times/m-p/221639#M7021</guid>
      <dc:creator>MountainFreak</dc:creator>
      <dc:date>2025-09-20T11:50:39Z</dc:date>
    </item>
    <item>
      <title>Re: customer charged multiple times</title>
      <link>https://community.squareup.com/t5/Orders-Menu-Items-Catalog/Why-was-my-customer-charged-multiple-times/m-p/221825#M7022</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.squareup.com/t5/user/viewprofilepage/user-id/117350"&gt;@MountainFreak&lt;/a&gt;&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":waving_hand:"&gt;👋&lt;/span&gt; Thanks for reaching out to us here on the Seller Community! Good to hear from you again.&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Sorry for the confusion here. This kind of temporary authorization is something that we see often - especially with customers using debit cards. If an attempt at a transaction is unsuccessful, a temporary authorization will process on the customers statement but will not actually post to the account due to the transaction not going through.&lt;BR /&gt;
&lt;BR /&gt;
While these authorizations tend to fall off of a statement in 24 to 48 hours, your customer can have them removed more quickly by reaching out to their card-issuing bank.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Nov 2020 13:09:00 GMT</pubDate>
      <guid>https://community.squareup.com/t5/Orders-Menu-Items-Catalog/Why-was-my-customer-charged-multiple-times/m-p/221825#M7022</guid>
      <dc:creator>Joe</dc:creator>
      <dc:date>2020-11-24T13:09:00Z</dc:date>
    </item>
  </channel>
</rss>

