<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Duplicate Debit Debacle Hits Best Buy, Macys. Who&#8217;s Next?</title>
	<atom:link href="http://www.storefrontbacktalk.com/supply-chain/duplicate-debit-debacle-hits-best-buy-macys-whos-next/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.storefrontbacktalk.com/supply-chain/duplicate-debit-debacle-hits-best-buy-macys-whos-next/</link>
	<description>Techniques, Tools and Tirades about Retail Technology and E-Commerce</description>
	<lastBuildDate>Wed, 10 Mar 2010 17:25:32 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bruce Daughtry</title>
		<link>http://www.storefrontbacktalk.com/supply-chain/duplicate-debit-debacle-hits-best-buy-macys-whos-next/comment-page-1/#comment-57101</link>
		<dc:creator>Bruce Daughtry</dc:creator>
		<pubDate>Thu, 19 Mar 2009 20:43:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.storefrontbacktalk.com/?p=2596#comment-57101</guid>
		<description>Interesting that this double posting issue with debit cards keeps happening.   My daughter&#039;s debit card was double billed by AT&amp;T when she bought the iPhone 3G.   Apparently only debit cards were affected, according to AT&amp;T, and happened to a lot of people.</description>
		<content:encoded><![CDATA[<p>Interesting that this double posting issue with debit cards keeps happening.   My daughter&#8217;s debit card was double billed by AT&amp;T when she bought the iPhone 3G.   Apparently only debit cards were affected, according to AT&amp;T, and happened to a lot of people.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Terry Bouvier</title>
		<link>http://www.storefrontbacktalk.com/supply-chain/duplicate-debit-debacle-hits-best-buy-macys-whos-next/comment-page-1/#comment-57076</link>
		<dc:creator>Terry Bouvier</dc:creator>
		<pubDate>Thu, 19 Mar 2009 15:05:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.storefrontbacktalk.com/?p=2596#comment-57076</guid>
		<description>Almost all banks/transaction processors in the world have the inherent flaw that caused the scenario described above.  They approve the credit/debit transaction and then pass this message to the POS and then assume they&#039;ve done their part and all is well.  There are some additional checks behind the scenes to determine if the message was successfully received, but there is still a small window of opportunity for failure.
HSBC is the only bank I&#039;ve seen whereby they require the POS system to respond with a message stating &quot;Yes, I&#039;ve received your approval message and here is the approval code you just sent me which proves I actually received your message - all is well&quot;.  If the bank does not receive this message within a certain time, it will assume all was not well and will reverse the last transaction.
The chance of failure in this scenario is about the same as in the scenario at Best Buy and Macy&#039;s however, the liability is shifted from the consumer to the retailer.  Instead of the customer being double/triple charged, it is possible they walk out with free merchandise.  This of course, raises the argument is it better to annoy a loyal customer (who will notice being overcharged) or take the hit where it might not be noticed (unless the retailer is diligently monitoring their suspense/settlement files).  Most retailers prefer the former since they know they can make amends.  If a customer walks away with free merchandise, it may be impossible to ever collect that money.
The bottom line - monitor your bank statements regularly and refute all questionable transactions.  The onus is on the retailer to prove you authorized the charges.</description>
		<content:encoded><![CDATA[<p>Almost all banks/transaction processors in the world have the inherent flaw that caused the scenario described above.  They approve the credit/debit transaction and then pass this message to the POS and then assume they&#8217;ve done their part and all is well.  There are some additional checks behind the scenes to determine if the message was successfully received, but there is still a small window of opportunity for failure.<br />
HSBC is the only bank I&#8217;ve seen whereby they require the POS system to respond with a message stating &#8220;Yes, I&#8217;ve received your approval message and here is the approval code you just sent me which proves I actually received your message &#8211; all is well&#8221;.  If the bank does not receive this message within a certain time, it will assume all was not well and will reverse the last transaction.<br />
The chance of failure in this scenario is about the same as in the scenario at Best Buy and Macy&#8217;s however, the liability is shifted from the consumer to the retailer.  Instead of the customer being double/triple charged, it is possible they walk out with free merchandise.  This of course, raises the argument is it better to annoy a loyal customer (who will notice being overcharged) or take the hit where it might not be noticed (unless the retailer is diligently monitoring their suspense/settlement files).  Most retailers prefer the former since they know they can make amends.  If a customer walks away with free merchandise, it may be impossible to ever collect that money.<br />
The bottom line &#8211; monitor your bank statements regularly and refute all questionable transactions.  The onus is on the retailer to prove you authorized the charges.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Patrick</title>
		<link>http://www.storefrontbacktalk.com/supply-chain/duplicate-debit-debacle-hits-best-buy-macys-whos-next/comment-page-1/#comment-57050</link>
		<dc:creator>Greg Patrick</dc:creator>
		<pubDate>Thu, 19 Mar 2009 10:25:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.storefrontbacktalk.com/?p=2596#comment-57050</guid>
		<description>When you swipe your swipe your card.  Ask for an error message,  call your bank before swiping your card again. If you are going to use a debit card,  do not write checks.</description>
		<content:encoded><![CDATA[<p>When you swipe your swipe your card.  Ask for an error message,  call your bank before swiping your card again. If you are going to use a debit card,  do not write checks.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
