<?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: Paypal Shopping Cart Makes Spam</title>
	<atom:link href="http://www.merchantaccountblog.com/archives/152/feed" rel="self" type="application/rss+xml" />
	<link>http://www.merchantaccountblog.com/archives/152</link>
	<description>Merchant Accounts, Ecommerce, Processing Equipment</description>
	<pubDate>Wed, 19 Nov 2008 23:41:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: George</title>
		<link>http://www.merchantaccountblog.com/archives/152#comment-19360</link>
		<dc:creator>George</dc:creator>
		<pubDate>Fri, 07 Nov 2008 14:45:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchantaccountblog.com/archives/152#comment-19360</guid>
		<description>I would think it would be very easy for paypal to simply add an account number (16 digits ?) to every seller's account. Then have their program look for the "old" field "business" which contains the email of the account AND it could look for the new field "paypalacct" (or similar name) and it could use either. Simply a line or two where it would check ifexists paypalacct then proceed else ifexists business then proceed else improper websiteform would work.
Simple programming and addition of an acct number would allow old or new to be used. Web owners could quickly change to the new format by finding the old line and replacing with the new.
The new server side include?... that just might be tedious or cheap way of fixing the problem and it would still require a lot of work by the website owner. Paypal caused the problem by usage of email in their form, they should just get rid of it and in the easiest way for the seller who may not have adequate knowledge for using SSI. A simple copy and paste by the seller to fix old pages would be the easiest fix.</description>
		<content:encoded><![CDATA[<p>I would think it would be very easy for paypal to simply add an account number (16 digits ?) to every seller&#8217;s account. Then have their program look for the &#8220;old&#8221; field &#8220;business&#8221; which contains the email of the account AND it could look for the new field &#8220;paypalacct&#8221; (or similar name) and it could use either. Simply a line or two where it would check ifexists paypalacct then proceed else ifexists business then proceed else improper websiteform would work.<br />
Simple programming and addition of an acct number would allow old or new to be used. Web owners could quickly change to the new format by finding the old line and replacing with the new.<br />
The new server side include?&#8230; that just might be tedious or cheap way of fixing the problem and it would still require a lot of work by the website owner. Paypal caused the problem by usage of email in their form, they should just get rid of it and in the easiest way for the seller who may not have adequate knowledge for using SSI. A simple copy and paste by the seller to fix old pages would be the easiest fix.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PageDown Tech</title>
		<link>http://www.merchantaccountblog.com/archives/152#comment-1761</link>
		<dc:creator>PageDown Tech</dc:creator>
		<pubDate>Sun, 21 Jan 2007 23:00:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchantaccountblog.com/archives/152#comment-1761</guid>
		<description>PayPal has introduced a good solution to this, their new Express Checkout API offers a server side workaroudn to this, and a faster checkout... the older method in this article is slowly being phased out.</description>
		<content:encoded><![CDATA[<p>PayPal has introduced a good solution to this, their new Express Checkout API offers a server side workaroudn to this, and a faster checkout&#8230; the older method in this article is slowly being phased out.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
