<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>strictlyPHP &#187; paypal</title>
	<atom:link href="http://www.strictlyphp.com/blog/tag/paypal/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.strictlyphp.com/blog</link>
	<description>web development &#38; web analytics</description>
	<lastBuildDate>Tue, 08 Mar 2011 10:47:29 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>PayPal sandbox problems</title>
		<link>http://www.strictlyphp.com/blog/2008/10/12/paypal-ipn-problems/</link>
		<comments>http://www.strictlyphp.com/blog/2008/10/12/paypal-ipn-problems/#comments</comments>
		<pubDate>Sun, 12 Oct 2008 11:21:14 +0000</pubDate>
		<dc:creator>Sam</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[paypal]]></category>
		<category><![CDATA[php]]></category>

		<guid isPermaLink="false">http://www.strictlyphp.com/blog/?p=209</guid>
		<description><![CDATA[Implementing the PayPal &#8220;Website Payments Standard&#8221; (advanced &#8220;Buy Now button&#8221;) has proven to be an extremely painful process for me. In my opinion, they have a terribly bad system when compared to competitors and current web standards. I&#8217;ve been implementing the Instant Payment Notification (IPN) which basically sends feedback about a &#8220;Buy Now button&#8221; transaction. [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignnone size-medium wp-image-213" style="margin: 0 10px 10px 0;text-align: left;" title="paypal_logo" src="http://www.strictlyphp.com/blog/wp-content/uploads/2008/10/paypal_logo.jpg" alt="" width="125" height="60" /></p>
<p><em>Implementing the PayPal &#8220;Website Payments Standard&#8221; (advanced &#8220;Buy Now button&#8221;) has proven to be an extremely painful process for me. In my opinion, they have a terribly bad system when compared to competitors and current web standards.</em></p>
<p>I&#8217;ve been implementing the <strong>Instant Payment Notification</strong> (IPN) which basically sends feedback about a &#8220;Buy Now button&#8221; transaction.</p>
<p>Most importantly: it has had numerous bugs and downtime the last year or so (as you can see in their <a href="http://www.paypaldeveloper.com/blog?blog.id=sb" target="_blank">sandbox status blog</a>). Some desperate people even mentioned PayPal intentionally wanted you to test on their live system performing real payments.</p>
<p>Secondly, here is a list of problems they should solve or things they should improve:</p>
<ul>
<li>First of all, when accessing their cart, a pre-2000 JavaScript script performs a window resize. Why?</li>
<li>In sandbox mode, an invalid credit card number is prefilled: you cannot use it, why prefill?</li>
<li>The JavaScript page reload that is triggered after country change is a big no-no.</li>
<li>You have to sign in to the developer central in a different tab or window in order to test: why?</li>
<li>The whole sandbox is painfully slow (at least when accessing from Belgium).</li>
</ul>
<p>Does this again prove that big companies suffer from their size when building products? I cannot imagine this would happen over such a long period of time in a small business.</p>
<p><strong>Edit:</strong> it just happened again. You&#8217;re testing the IPN response and all of a sudden the exact same test order you made just does not work anymore. <em>Without changing a single thing.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.strictlyphp.com/blog/2008/10/12/paypal-ipn-problems/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

