<?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: CV2 versus Confirmation</title>
	<atom:link href="http://blog.mauveweb.co.uk/2008/02/18/cv2-versus-confirmation/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mauveweb.co.uk/2008/02/18/cv2-versus-confirmation/</link>
	<description>experiments in contemporary web development</description>
	<pubDate>Mon, 01 Dec 2008 22:31:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: mauve</title>
		<link>http://blog.mauveweb.co.uk/2008/02/18/cv2-versus-confirmation/#comment-19653</link>
		<dc:creator>mauve</dc:creator>
		<pubDate>Tue, 19 Feb 2008 11:56:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mauveweb.co.uk/2008/02/18/cv2-versus-confirmation/#comment-19653</guid>
		<description>Yes, this is applicable to server-to-server payment APIs only.</description>
		<content:encoded><![CDATA[<p>Yes, this is applicable to server-to-server payment <acronym title="	Application Programming Interface">APIs</acronym> only.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MJ Ray</title>
		<link>http://blog.mauveweb.co.uk/2008/02/18/cv2-versus-confirmation/#comment-19651</link>
		<dc:creator>MJ Ray</dc:creator>
		<pubDate>Tue, 19 Feb 2008 10:53:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mauveweb.co.uk/2008/02/18/cv2-versus-confirmation/#comment-19651</guid>
		<description>I believe OSCommerce behaviour will depend on which payment modules you are using.  IIRC, protx_form doesn't store any card details itself, for example.</description>
		<content:encoded><![CDATA[<p>I believe OSCommerce behaviour will depend on which payment modules you are using.  <acronym title="If I remember correctly">IIRC</acronym>, protx_form doesn't store any card details itself, for example.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
