<?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: A Token Effort Might Be The Right Approach</title>
	<atom:link href="http://blogs.gartner.com/john_pescatore/2009/08/12/a-token-effort-might-be-the-right-approach/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gartner.com/john_pescatore/2009/08/12/a-token-effort-might-be-the-right-approach/</link>
	<description>A member of the Gartner Blog Network</description>
	<lastBuildDate>Sat, 04 Feb 2012 17:10:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Chuck Riegel</title>
		<link>http://blogs.gartner.com/john_pescatore/2009/08/12/a-token-effort-might-be-the-right-approach/comment-page-1/#comment-1438</link>
		<dc:creator>Chuck Riegel</dc:creator>
		<pubDate>Wed, 23 Sep 2009 16:37:12 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/john_pescatore/?p=778#comment-1438</guid>
		<description>Great brief - lot&#039;s of confusion.  Most payment gateways have had Token capabilities for some time.  The Token really has an impact on certian types of transactions - Auth/Capture, repeat customers, recurring and subscriptions are the main transaction used where data needs to be stored somewhere for follow on activity.  One issue is that the data from the POS is in the clear as the Token is created so encryption at the swipe is needed.  Reduce cost of PCI - absoutely, protecting access to useable card data - only part of what is needed.</description>
		<content:encoded><![CDATA[<p>Great brief &#8211; lot&#8217;s of confusion.  Most payment gateways have had Token capabilities for some time.  The Token really has an impact on certian types of transactions &#8211; Auth/Capture, repeat customers, recurring and subscriptions are the main transaction used where data needs to be stored somewhere for follow on activity.  One issue is that the data from the POS is in the clear as the Token is created so encryption at the swipe is needed.  Reduce cost of PCI &#8211; absoutely, protecting access to useable card data &#8211; only part of what is needed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

