<?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: PayPal (Still) Looking To Mobile, But In The Wrong Places</title>
	<atom:link href="http://mobhappy.com/blog1/2006/02/03/paypal-still-looking-to-mobile-but-in-the-wrong-places/feed/" rel="self" type="application/rss+xml" />
	<link>http://mobhappy.com/blog1/2006/02/03/paypal-still-looking-to-mobile-but-in-the-wrong-places/</link>
	<description>Russell Buckley and Carlo Longino on mobile technology.</description>
	<lastBuildDate>Tue, 31 Jan 2012 19:56:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Mobile payments &#187; Some doubts about PayPal and mobile payments</title>
		<link>http://mobhappy.com/blog1/2006/02/03/paypal-still-looking-to-mobile-but-in-the-wrong-places/comment-page-1/#comment-2153</link>
		<dc:creator>Mobile payments &#187; Some doubts about PayPal and mobile payments</dc:creator>
		<pubDate>Sun, 12 Mar 2006 17:35:28 +0000</pubDate>
		<guid isPermaLink="false">http://mobhappy.com/blog1/2006/02/03/paypal-still-looking-to-mobile-but-in-the-wrong-places/#comment-2153</guid>
		<description>[...] To read the post: MobHappy  March 12th, 2006 [...]</description>
		<content:encoded><![CDATA[<p>[...] To read the post: MobHappy  March 12th, 2006 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Quintana Pearce</title>
		<link>http://mobhappy.com/blog1/2006/02/03/paypal-still-looking-to-mobile-but-in-the-wrong-places/comment-page-1/#comment-1643</link>
		<dc:creator>James Quintana Pearce</dc:creator>
		<pubDate>Sat, 04 Feb 2006 19:49:57 +0000</pubDate>
		<guid isPermaLink="false">http://mobhappy.com/blog1/2006/02/03/paypal-still-looking-to-mobile-but-in-the-wrong-places/#comment-1643</guid>
		<description>&quot;reverse billing to a mobile phone bill works pretty well for mobile content.&quot;

It works pretty well except that the carriers take a huge chunk of the proceeds. The expectation is that PayPal will take a much smaller percentage, equivalent to what they do online. If an online store is offering a mobile game for $4 if you have it charged to you phone bill or $2 if you use PayPal, I bet a significant number of people would choose the PayPal system. 

I assume that because you&#039;re accessing the mobile web through your phone PayPal can authenticate the device, which would be linked to your PayPal account. I see this being used to pay for mobile content via the mobile web rather than for payments in physical stores -- I&#039;m with you on that one.

And I agree that the interesting things in mobile banking are happening in Africa. There&#039;s one country that has a full bank accessible through mobile phones, which is way ahead of anywhere else...</description>
		<content:encoded><![CDATA[<p>&#8220;reverse billing to a mobile phone bill works pretty well for mobile content.&#8221;</p>
<p>It works pretty well except that the carriers take a huge chunk of the proceeds. The expectation is that PayPal will take a much smaller percentage, equivalent to what they do online. If an online store is offering a mobile game for $4 if you have it charged to you phone bill or $2 if you use PayPal, I bet a significant number of people would choose the PayPal system. </p>
<p>I assume that because you&#8217;re accessing the mobile web through your phone PayPal can authenticate the device, which would be linked to your PayPal account. I see this being used to pay for mobile content via the mobile web rather than for payments in physical stores &#8212; I&#8217;m with you on that one.</p>
<p>And I agree that the interesting things in mobile banking are happening in Africa. There&#8217;s one country that has a full bank accessible through mobile phones, which is way ahead of anywhere else&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William Volk</title>
		<link>http://mobhappy.com/blog1/2006/02/03/paypal-still-looking-to-mobile-but-in-the-wrong-places/comment-page-1/#comment-1641</link>
		<dc:creator>William Volk</dc:creator>
		<pubDate>Sat, 04 Feb 2006 18:08:53 +0000</pubDate>
		<guid isPermaLink="false">http://mobhappy.com/blog1/2006/02/03/paypal-still-looking-to-mobile-but-in-the-wrong-places/#comment-1641</guid>
		<description>Mobile content people who get all excited about the prospect of an alternative billing system for purchasing ringtones, wallpapers, games, and other mobile content items ... with the hope of smaller billing margins ... are forgetting some important issues:

1. Customers prefer content billed to their phone bill (P-SMS).  It&#039;s &quot;low friction&quot; and because the purchases are added to an existing phone bill it&#039;s almost &#039;painless.&#039;

2. The Carriers have no incentive to make a alternative payment system easy to use.  Therefore if you want to have SHORTCODE ordering, or even do a binary SMS WAP-PUSH of the content, you&#039;ll pretty much have to use P-SMS.  Want to make life difficult for your customers?  Force them to enter a lengthy URL into their WAP (mobile) browser.</description>
		<content:encoded><![CDATA[<p>Mobile content people who get all excited about the prospect of an alternative billing system for purchasing ringtones, wallpapers, games, and other mobile content items &#8230; with the hope of smaller billing margins &#8230; are forgetting some important issues:</p>
<p>1. Customers prefer content billed to their phone bill (P-SMS).  It&#8217;s &#8220;low friction&#8221; and because the purchases are added to an existing phone bill it&#8217;s almost &#8216;painless.&#8217;</p>
<p>2. The Carriers have no incentive to make a alternative payment system easy to use.  Therefore if you want to have SHORTCODE ordering, or even do a binary SMS WAP-PUSH of the content, you&#8217;ll pretty much have to use P-SMS.  Want to make life difficult for your customers?  Force them to enter a lengthy URL into their WAP (mobile) browser.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

