<?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: Some thoughts about Amazon&#8217;s Flexible Payment System</title>
	<atom:link href="http://comments.deasil.com/2007/08/08/some-thoughts-about-amazons-flexible-payment-system/feed/" rel="self" type="application/rss+xml" />
	<link>http://comments.deasil.com/2007/08/08/some-thoughts-about-amazons-flexible-payment-system/</link>
	<description>escape colon w q</description>
	<pubDate>Mon, 01 Dec 2008 19:30:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: felix</title>
		<link>http://comments.deasil.com/2007/08/08/some-thoughts-about-amazons-flexible-payment-system/#comment-3277</link>
		<dc:creator>felix</dc:creator>
		<pubDate>Fri, 10 Aug 2007 15:10:33 +0000</pubDate>
		<guid isPermaLink="false">http://comments.deasil.com/2007/08/08/some-thoughts-about-amazons-flexible-payment-system/#comment-3277</guid>
		<description>Mavryk - thanks for stopping by. It's true that there's ways to mitigate this - it even shows the flexibility and power of the API that these are possible to do. But for me - it still isn't a viable solution. I still lose control over first time (and thus my most delicate) users as well as a potentially offputting request to pre-authorize many purchases that they might never make. Sigh.</description>
		<content:encoded><![CDATA[<p>Mavryk - thanks for stopping by. It&#8217;s true that there&#8217;s ways to mitigate this - it even shows the flexibility and power of the API that these are possible to do. But for me - it still isn&#8217;t a viable solution. I still lose control over first time (and thus my most delicate) users as well as a potentially offputting request to pre-authorize many purchases that they might never make. Sigh.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mavryk</title>
		<link>http://comments.deasil.com/2007/08/08/some-thoughts-about-amazons-flexible-payment-system/#comment-3264</link>
		<dc:creator>mavryk</dc:creator>
		<pubDate>Fri, 10 Aug 2007 04:10:10 +0000</pubDate>
		<guid isPermaLink="false">http://comments.deasil.com/2007/08/08/some-thoughts-about-amazons-flexible-payment-system/#comment-3264</guid>
		<description>I think in order to avoid the extra checkout steps of getting a single-use authorization (token) from the customer on every purchase through FPS, websites can probably have their "trusting" customers provide them with a multi-use token upto a particular limit and then use that to charge them for purchases. This way the redirect to Amazon UI (and the extra steps) shall not be required every time a returning customer makes a purchase.

I know this doesn't work for new customers but atleast its an option for returning (and trusting) customers.</description>
		<content:encoded><![CDATA[<p>I think in order to avoid the extra checkout steps of getting a single-use authorization (token) from the customer on every purchase through FPS, websites can probably have their &#8220;trusting&#8221; customers provide them with a multi-use token upto a particular limit and then use that to charge them for purchases. This way the redirect to Amazon UI (and the extra steps) shall not be required every time a returning customer makes a purchase.</p>
<p>I know this doesn&#8217;t work for new customers but atleast its an option for returning (and trusting) customers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
