<?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: Usability review: Amtrak.com checkout process</title>
	<atom:link href="http://www.pathf.com/blogs/2008/01/usability-revie/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pathf.com/blogs/2008/01/usability-revie/</link>
	<description>Running commentary about agile development, user experience design and Ajax.</description>
	<pubDate>Wed, 19 Nov 2008 23:38:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Jamie</title>
		<link>http://www.pathf.com/blogs/2008/01/usability-revie/#comment-139</link>
		<dc:creator>Jamie</dc:creator>
		<pubDate>Thu, 10 Jan 2008 08:19:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=114#comment-139</guid>
		<description>&lt;p&gt;While I accept that the Amtrak site could certainly do with some work, it's worth noting that depending on what payment processor they're using and what PCI requirements they are meeting, it's possible that they are not permitted to persist the CCV value in the user session. No excuse for not flagging it up and eliminating all the other problems though.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>While I accept that the Amtrak site could certainly do with some work, it&#8217;s worth noting that depending on what payment processor they&#8217;re using and what PCI requirements they are meeting, it&#8217;s possible that they are not permitted to persist the CCV value in the user session. No excuse for not flagging it up and eliminating all the other problems though.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
