<?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: Google Chrome OS:  what does it mean for commerce?</title>
	<atom:link href="http://tylerhannan.com/2009/11/google-chrome-os-what-does-it-mean-for-commerce/feed/" rel="self" type="application/rss+xml" />
	<link>http://tylerhannan.com/2009/11/google-chrome-os-what-does-it-mean-for-commerce/</link>
	<description>reflections from the intersection of technology and payments</description>
	<lastBuildDate>Thu, 29 Jul 2010 01:07:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: tylerhannan</title>
		<link>http://tylerhannan.com/2009/11/google-chrome-os-what-does-it-mean-for-commerce/comment-page-1/#comment-52</link>
		<dc:creator>tylerhannan</dc:creator>
		<pubDate>Wed, 25 Nov 2009 22:43:44 +0000</pubDate>
		<guid isPermaLink="false">http://tylerhannan.com/?p=189#comment-52</guid>
		<description>I agree...in part.&lt;br&gt;&lt;br&gt;The reason that what you/I would call hardware is required for PIN Debit&lt;br&gt;transactions is, truly, nothing more than a requirement from processors for&lt;br&gt;keyed firmware.  If that requirement wasn&#039;t in place, the process of&lt;br&gt;transaction encryption could easily be done &quot;on the wire&quot;.&lt;br&gt;&lt;br&gt;I think the bigger issue...and that to which I refer when I speak of&lt;br&gt;hardware vs. software....is the question of &quot;intelligence&quot;.  It&#039;s sort of a&lt;br&gt;poor choice of words, but the best I can come up with at present.&lt;br&gt;&lt;br&gt;The traditional terminal device was &quot;it&quot;.  The end-all/be-all of acceptance&lt;br&gt;methodologies.  Over time, the software based acceptance methods (be they&lt;br&gt;online, hosted, or local) were positioned as value-add for the features they&lt;br&gt;provide.  And yet, there is still a benefit (financially) in performing a&lt;br&gt;swiped transaction.&lt;br&gt;&lt;br&gt;So you leverage a USB card swipe.  Is that hardware?  Yes...but it is&lt;br&gt;hardware in the same fashion that a keyboard is hardware.  Hardware, of some&lt;br&gt;sort, is required to run and interact with software.*&lt;br&gt;&lt;br&gt;PIN Debit is a great example.  I need a certified PED if I&#039;m going to&lt;br&gt;perform PIN Debit transactions in a safe/compliant fashion.  The hardware,&lt;br&gt;however, is truly just an encryption and input device....designed to&lt;br&gt;interact with the software that is providing connectivity, routing,&lt;br&gt;transaction qualification, and business management functions.&lt;br&gt;&lt;br&gt;* At least until the Google OS Brain implant is released</description>
		<content:encoded><![CDATA[<p>I agree&#8230;in part.</p>
<p>The reason that what you/I would call hardware is required for PIN Debit<br />transactions is, truly, nothing more than a requirement from processors for<br />keyed firmware.  If that requirement wasn&#39;t in place, the process of<br />transaction encryption could easily be done &#8220;on the wire&#8221;.</p>
<p>I think the bigger issue&#8230;and that to which I refer when I speak of<br />hardware vs. software&#8230;.is the question of &#8220;intelligence&#8221;.  It&#39;s sort of a<br />poor choice of words, but the best I can come up with at present.</p>
<p>The traditional terminal device was &#8220;it&#8221;.  The end-all/be-all of acceptance<br />methodologies.  Over time, the software based acceptance methods (be they<br />online, hosted, or local) were positioned as value-add for the features they<br />provide.  And yet, there is still a benefit (financially) in performing a<br />swiped transaction.</p>
<p>So you leverage a USB card swipe.  Is that hardware?  Yes&#8230;but it is<br />hardware in the same fashion that a keyboard is hardware.  Hardware, of some<br />sort, is required to run and interact with software.*</p>
<p>PIN Debit is a great example.  I need a certified PED if I&#39;m going to<br />perform PIN Debit transactions in a safe/compliant fashion.  The hardware,<br />however, is truly just an encryption and input device&#8230;.designed to<br />interact with the software that is providing connectivity, routing,<br />transaction qualification, and business management functions.</p>
<p>* At least until the Google OS Brain implant is released</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: johnbfrank</title>
		<link>http://tylerhannan.com/2009/11/google-chrome-os-what-does-it-mean-for-commerce/comment-page-1/#comment-51</link>
		<dc:creator>johnbfrank</dc:creator>
		<pubDate>Wed, 25 Nov 2009 22:08:47 +0000</pubDate>
		<guid isPermaLink="false">http://tylerhannan.com/?p=189#comment-51</guid>
		<description>Interesting article. I noticed your PIN Debit reference.  I no longer make the Hardware vs. Software argument either.  There isn&#039;t one.  The only way to do PIN Debit is to capture the magnetic stripe.  Software can&#039;t do that.  Only Hardware can.</description>
		<content:encoded><![CDATA[<p>Interesting article. I noticed your PIN Debit reference.  I no longer make the Hardware vs. Software argument either.  There isn&#39;t one.  The only way to do PIN Debit is to capture the magnetic stripe.  Software can&#39;t do that.  Only Hardware can.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tylerhannan</title>
		<link>http://tylerhannan.com/2009/11/google-chrome-os-what-does-it-mean-for-commerce/comment-page-1/#comment-46</link>
		<dc:creator>tylerhannan</dc:creator>
		<pubDate>Wed, 25 Nov 2009 14:43:44 +0000</pubDate>
		<guid isPermaLink="false">http://tylerhannan.com/?p=189#comment-46</guid>
		<description>I agree...in part.&lt;br&gt;&lt;br&gt;The reason that what you/I would call hardware is required for PIN Debit&lt;br&gt;transactions is, truly, nothing more than a requirement from processors for&lt;br&gt;keyed firmware.  If that requirement wasn&#039;t in place, the process of&lt;br&gt;transaction encryption could easily be done &quot;on the wire&quot;.&lt;br&gt;&lt;br&gt;I think the bigger issue...and that to which I refer when I speak of&lt;br&gt;hardware vs. software....is the question of &quot;intelligence&quot;.  It&#039;s sort of a&lt;br&gt;poor choice of words, but the best I can come up with at present.&lt;br&gt;&lt;br&gt;The traditional terminal device was &quot;it&quot;.  The end-all/be-all of acceptance&lt;br&gt;methodologies.  Over time, the software based acceptance methods (be they&lt;br&gt;online, hosted, or local) were positioned as value-add for the features they&lt;br&gt;provide.  And yet, there is still a benefit (financially) in performing a&lt;br&gt;swiped transaction.&lt;br&gt;&lt;br&gt;So you leverage a USB card swipe.  Is that hardware?  Yes...but it is&lt;br&gt;hardware in the same fashion that a keyboard is hardware.  Hardware, of some&lt;br&gt;sort, is required to run and interact with software.*&lt;br&gt;&lt;br&gt;PIN Debit is a great example.  I need a certified PED if I&#039;m going to&lt;br&gt;perform PIN Debit transactions in a safe/compliant fashion.  The hardware,&lt;br&gt;however, is truly just an encryption and input device....designed to&lt;br&gt;interact with the software that is providing connectivity, routing,&lt;br&gt;transaction qualification, and business management functions.&lt;br&gt;&lt;br&gt;* At least until the Google OS Brain implant is released</description>
		<content:encoded><![CDATA[<p>I agree&#8230;in part.</p>
<p>The reason that what you/I would call hardware is required for PIN Debit<br />transactions is, truly, nothing more than a requirement from processors for<br />keyed firmware.  If that requirement wasn&#39;t in place, the process of<br />transaction encryption could easily be done &#8220;on the wire&#8221;.</p>
<p>I think the bigger issue&#8230;and that to which I refer when I speak of<br />hardware vs. software&#8230;.is the question of &#8220;intelligence&#8221;.  It&#39;s sort of a<br />poor choice of words, but the best I can come up with at present.</p>
<p>The traditional terminal device was &#8220;it&#8221;.  The end-all/be-all of acceptance<br />methodologies.  Over time, the software based acceptance methods (be they<br />online, hosted, or local) were positioned as value-add for the features they<br />provide.  And yet, there is still a benefit (financially) in performing a<br />swiped transaction.</p>
<p>So you leverage a USB card swipe.  Is that hardware?  Yes&#8230;but it is<br />hardware in the same fashion that a keyboard is hardware.  Hardware, of some<br />sort, is required to run and interact with software.*</p>
<p>PIN Debit is a great example.  I need a certified PED if I&#39;m going to<br />perform PIN Debit transactions in a safe/compliant fashion.  The hardware,<br />however, is truly just an encryption and input device&#8230;.designed to<br />interact with the software that is providing connectivity, routing,<br />transaction qualification, and business management functions.</p>
<p>* At least until the Google OS Brain implant is released</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: johnbfrank</title>
		<link>http://tylerhannan.com/2009/11/google-chrome-os-what-does-it-mean-for-commerce/comment-page-1/#comment-45</link>
		<dc:creator>johnbfrank</dc:creator>
		<pubDate>Wed, 25 Nov 2009 14:08:47 +0000</pubDate>
		<guid isPermaLink="false">http://tylerhannan.com/?p=189#comment-45</guid>
		<description>Interesting article. I noticed your PIN Debit reference.  I no longer make the Hardware vs. Software argument either.  There isn&#039;t one.  The only way to do PIN Debit is to capture the magnetic stripe.  Software can&#039;t do that.  Only Hardware can.</description>
		<content:encoded><![CDATA[<p>Interesting article. I noticed your PIN Debit reference.  I no longer make the Hardware vs. Software argument either.  There isn&#39;t one.  The only way to do PIN Debit is to capture the magnetic stripe.  Software can&#39;t do that.  Only Hardware can.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
