<?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"
	>
<channel>
	<title>Comments on: SunTrust Bank</title>
	<atom:link href="http://www.thatsprettydumb.com/2007/07/16/suntrust-bank/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thatsprettydumb.com/2007/07/16/suntrust-bank/</link>
	<description>Highlighting the stupid things that businesses do to us.</description>
	<pubDate>Sat, 22 Nov 2008 01:36:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: mickey</title>
		<link>http://www.thatsprettydumb.com/2007/07/16/suntrust-bank/#comment-5</link>
		<dc:creator>mickey</dc:creator>
		<pubDate>Mon, 03 Sep 2007 02:01:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.thatsprettydumb.com/2007/07/16/suntrust-bank/#comment-5</guid>
		<description>It's getting worse.  I'm randomly having things get denied, and when I call they say "we don't see any denial here - it just be a problem on their end".  After insisting for a few minutes that they really did deny the charge, I have to just give up and try again later.

Later that day, I usually get an automated call from SunTrust asking if it was a legitimate purchase I was trying to make, thus proving that they did indeed really block it.

If this happened once, it'd be a simply mistake.  It's happened twice now, which points to a procedural and/or technical issue on their page.  Blech.</description>
		<content:encoded><![CDATA[<p>It&#8217;s getting worse.  I&#8217;m randomly having things get denied, and when I call they say &#8220;we don&#8217;t see any denial here - it just be a problem on their end&#8221;.  After insisting for a few minutes that they really did deny the charge, I have to just give up and try again later.</p>
<p>Later that day, I usually get an automated call from SunTrust asking if it was a legitimate purchase I was trying to make, thus proving that they did indeed really block it.</p>
<p>If this happened once, it&#8217;d be a simply mistake.  It&#8217;s happened twice now, which points to a procedural and/or technical issue on their page.  Blech.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
