<?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: Receipt error?? in Payments Troubleshooting</title>
    <link>https://community.squareup.com/t5/Payments-Troubleshooting/Receipt-error/m-p/838633#M67081</link>
    <description>&lt;P&gt;&lt;a href="https://community.squareup.com/t5/user/viewprofilepage/user-id/762936"&gt;@EASAsouthwest&lt;/a&gt;&amp;nbsp;Your customer would be right. &amp;nbsp;This happens all the time with cards that are used with mobile wallets, and is a security feature that the international banking industry set up years ago. &amp;nbsp;When a mobile wallet (Apple, Google) is used to pay, the verification process spits out a random 4-digit code that only Square and your customer's bank know. &amp;nbsp;It is a one-time burner code that protects your customers' actual card number, or at least makes it harder for bad actors to compromise. &amp;nbsp;That is just one place where this happens.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you customer has an Apple Card, like I do, then Apple also uses this burner code system when Apple Cards are dipped or tapped.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm surprised your customer hasn't seen this before. &amp;nbsp;It has been the banking standard for many years, now. &amp;nbsp;Anyway, that's the explanation. &amp;nbsp;It is not an error at all.&lt;/P&gt;</description>
    <pubDate>Wed, 18 Mar 2026 18:01:00 GMT</pubDate>
    <dc:creator>TheRealChipA</dc:creator>
    <dc:date>2026-03-18T18:01:00Z</dc:date>
    <item>
      <title>Receipt error??</title>
      <link>https://community.squareup.com/t5/Payments-Troubleshooting/Receipt-error/m-p/838627#M67080</link>
      <description>&lt;P&gt;A customer just told me her receipt showed a different 4 number code from her actual credit card.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Mar 2026 17:44:59 GMT</pubDate>
      <guid>https://community.squareup.com/t5/Payments-Troubleshooting/Receipt-error/m-p/838627#M67080</guid>
      <dc:creator>EASAsouthwest</dc:creator>
      <dc:date>2026-03-18T17:44:59Z</dc:date>
    </item>
    <item>
      <title>Re: Receipt error??</title>
      <link>https://community.squareup.com/t5/Payments-Troubleshooting/Receipt-error/m-p/838633#M67081</link>
      <description>&lt;P&gt;&lt;a href="https://community.squareup.com/t5/user/viewprofilepage/user-id/762936"&gt;@EASAsouthwest&lt;/a&gt;&amp;nbsp;Your customer would be right. &amp;nbsp;This happens all the time with cards that are used with mobile wallets, and is a security feature that the international banking industry set up years ago. &amp;nbsp;When a mobile wallet (Apple, Google) is used to pay, the verification process spits out a random 4-digit code that only Square and your customer's bank know. &amp;nbsp;It is a one-time burner code that protects your customers' actual card number, or at least makes it harder for bad actors to compromise. &amp;nbsp;That is just one place where this happens.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you customer has an Apple Card, like I do, then Apple also uses this burner code system when Apple Cards are dipped or tapped.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm surprised your customer hasn't seen this before. &amp;nbsp;It has been the banking standard for many years, now. &amp;nbsp;Anyway, that's the explanation. &amp;nbsp;It is not an error at all.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Mar 2026 18:01:00 GMT</pubDate>
      <guid>https://community.squareup.com/t5/Payments-Troubleshooting/Receipt-error/m-p/838633#M67081</guid>
      <dc:creator>TheRealChipA</dc:creator>
      <dc:date>2026-03-18T18:01:00Z</dc:date>
    </item>
  </channel>
</rss>

