<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;CUQGQ3c9eCp7ImA9WhNUEUw.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344</id><updated>2013-01-01T23:55:22.960-08:00</updated><category term="best practices" /><category term="Mobile Payments" /><category term="subscription billing" /><category term="chargeback" /><category term="APSI" /><category term="Starbucks 2D Bar Code" /><category term="Carrier Billing" /><category term="Revolution Money" /><title>Payment Talk</title><subtitle type="html">A casual place for anyone who is interested in ecommerce or mcommerce payments to visit and chat.</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://paymenttalk.blogspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>71</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/blogspot/AuDw" /><feedburner:info uri="blogspot/audw" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry gd:etag="W/&quot;DkACSH85fip7ImA9WhdUGU8.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-1402573587698468598</id><published>2011-10-06T11:12:00.001-07:00</published><updated>2011-10-06T11:12:49.126-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-10-06T11:12:49.126-07:00</app:edited><title>NFC vs. Mag Stripe</title><content type="html">Who cares? Did you ever go to a Mag Stripe conference?  Why are there so many conferences now focused on NFC?  Stupid question!  Because it is the latest bandwagon and therefore conference organizers jump on it.  What really matters?  It isn't the technology.  It is the simple fact that the mobile phone is adding more and more value to our lives and regardless of the technical bridge used, it is obvious that using our phones as a proxy for our payment credentials has great promise.  Freeing consumers from having to carry around a lot of cash or providing (hopefully) responsible consumers with a credit facility is what matters.  This matters to both consumers and merchants.  So, lets all stop worrying about which technology is going to win and give the consumers and merchants what they want.  Bar codes, mag stripes, NFC, OTA are all going to co-exist for a very long time.  Damn, I was at a resort recently and they still used an old knuckle buster to capture my credit card info. p.s.  They had advanced to the carbonless version of the sales draft!&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/P9cRugWGthE" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/1402573587698468598/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=1402573587698468598&amp;isPopup=true" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/1402573587698468598?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/1402573587698468598?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/P9cRugWGthE/nfc-vs-mag-stripe.html" title="NFC vs. Mag Stripe" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>2</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2011/10/nfc-vs-mag-stripe.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0AHRngzfSp7ImA9WhdUF0s.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-5756753779797586508</id><published>2011-10-04T15:01:00.000-07:00</published><updated>2011-10-04T15:02:17.685-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-10-04T15:02:17.685-07:00</app:edited><title>Micropayments?</title><content type="html">I am in the midst of reading a new (&amp; well written) whitepaper on Mobile Payments from the Smart Card Alliance.&lt;br /&gt;&lt;br /&gt;I came across this defition of transaction sizes; "2.4.1.2 Transaction Size&lt;br /&gt;Transaction size affects the choice of mobile payment technology and approach. Mobile payments typically fit into one of two transaction size categories. Micropayments (less than $10-$25) are typical for paying for ring tones, music, parking, transit, coffee, and items in convenience stores. Macropayments (over $25) are typical for all other transactions, such as person-to-person domestic and international remittances, charitable donations, Web site purchases, bill payment and retail POS."&lt;br /&gt;&lt;br /&gt;I see things here a little differently.  I have always thought of micropayments as $1-$2 in size, minipayments as $3-$7 and normal or as they say macropayments as $8+.&lt;br /&gt;&lt;br /&gt;What are your thoughts?&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/1JZQU-fEet0" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/5756753779797586508/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=5756753779797586508&amp;isPopup=true" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/5756753779797586508?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/5756753779797586508?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/1JZQU-fEet0/micropayments.html" title="Micropayments?" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>3</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2011/10/micropayments.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkUERHk-eip7ImA9WhdTF0k.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-2757177542848105487</id><published>2011-07-15T08:17:00.000-07:00</published><updated>2011-07-15T08:36:45.752-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-15T08:36:45.752-07:00</app:edited><title>Try it, you'll like it (or maybe not)....</title><content type="html">I read press releases everyday about what are pitched as the latest and greatest innovations in payments.  But, then, I go behind the "lines" and sign up (if necessary), and actually try the product or service.  You need to do that too, before rendering an opinion.&lt;br /&gt;&lt;br /&gt;I have (or had if they have gone four paws to the sky) the following accounts; Serve &amp; the predecessor Revolution Money , Obopay, BlingNation, PayPal, Square, Mazooma, Kwedit, Rixty, Starbucks, PaybyTouch, Mobibucks, ClipperCard(BART NFC), Safeway echeck, Google Check-out, itunes, BillmeLater, Click n'Buy, Verified by Visa, Amazon PayPhrase, TwitPay, etc., way too many to name (but I tried).  &lt;br /&gt;&lt;br /&gt;There is one thing to keep in mind, though, when you do this.  In a prior phase of my career, it was important for me to have a credit card from every brand and every major bank since I was calling on all of them and it was awkward to take someone from Visa out to lunch and pay with an Amex card.  Once when applying for a mortgage, everything was excellent in my application but the one hit I took was having too many accounts.  :-)&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/44nJJIJIcWY" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/2757177542848105487/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=2757177542848105487&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/2757177542848105487?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/2757177542848105487?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/44nJJIJIcWY/try-it-youll-like-it-or-maybe-not.html" title="Try it, you'll like it (or maybe not)...." /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>0</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2011/07/try-it-youll-like-it-or-maybe-not.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEcNSXw_eCp7ImA9WhZaEEs.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-4943499649649928366</id><published>2011-06-17T14:57:00.000-07:00</published><updated>2011-06-25T22:28:18.240-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-06-25T22:28:18.240-07:00</app:edited><title>First NFC Payment Completed!!!</title><content type="html">Wow!  I actually found a merchant to use my NFC enabled Discover Card to pay for a recent purchase. It was at Mickey D's.  (BTW - I have been showing off my Discover NFC decal which I have applied to the back of my iPhone to everyone!)&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/XFVJkEEvlGk" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/4943499649649928366/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=4943499649649928366&amp;isPopup=true" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/4943499649649928366?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/4943499649649928366?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/XFVJkEEvlGk/first-nfc-payment-completed.html" title="First NFC Payment Completed!!!" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>2</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2011/06/first-nfc-payment-completed.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEYNRX08cCp7ImA9WhZaEEs.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-7562300585954376224</id><published>2011-05-13T13:24:00.000-07:00</published><updated>2011-06-25T22:29:54.378-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-06-25T22:29:54.378-07:00</app:edited><title>NFC (or Mobile Payments depending on your preferred spin) - My real life story</title><content type="html">So, I was in NJ on business this week.  I stopped in at a supermarket, picked up a few items and arrived at the check-out.  There was a Verifone (still brings a smile to my face everytime I see one considering my tenure there during their formative years)terminal with the necessary NFC attachment so since my iPhone was already in my hand (playing Words with Friends while waiting to pay) and is equiped with my recently received NFC decal from Discover, I thought GREAT, I finally found a place to use NFC.&lt;br /&gt;&lt;br /&gt;I started tapping my phone on the NFC reader.  The clerk looked at me like I was from MARS.  He had no idea what I was doing - "dah, have never seen that before".  Well, it did not work, so out came my credit card and a simple swipe and I was done.&lt;br /&gt;&lt;br /&gt;I contrast that with my experience (previously written about) at Starbucks using the iPhone 2D Bar Code app.  Bravo!!!!&lt;br /&gt;&lt;br /&gt;The point is, it isn't about the technology.  It is all in the execution.  And, the challenges of a successful execution at the very diverse and complex POS are staggering.  Under the best of circumstances, this is a 5-10 year evolution.  For God's sake, people are still writing checks at the supermarket register.&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/l9wD_K3sQzk" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/7562300585954376224/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=7562300585954376224&amp;isPopup=true" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/7562300585954376224?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/7562300585954376224?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/l9wD_K3sQzk/nfc-or-mobile-payments-depending-on.html" title="NFC (or Mobile Payments depending on your preferred spin) - My real life story" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>1</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2011/05/nfc-or-mobile-payments-depending-on.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CE4NSXsyeCp7ImA9WhZXFU8.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-5885330508402775823</id><published>2011-05-04T08:14:00.000-07:00</published><updated>2011-05-04T08:29:58.590-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-05-04T08:29:58.590-07:00</app:edited><title>Ouch, another major breach!  (Not an issue for Direct Carrier Billing!!!)</title><content type="html">One of the major benefits of DCB (Direct Carrier Billing) is that the merchant is not burdened by having to handle or store any sensitive information that could be used to create subsequent fraudulent transactions and therefore there is no PCI.  &lt;br /&gt;&lt;br /&gt;We talk often of the benefits to consumers;&lt;br /&gt;- no username/passwords to remember&lt;br /&gt;- everything they need to transact is in their heads and their hand&lt;br /&gt;- no enrollment&lt;br /&gt;- for someone to put a fraudulent charge on their bill, they would have to have their mobile phone in their hand at the exact moment of the tx and depending on the carrier, also have to know their billing Zip Code.  (note - this add'l 2nd factor of auth will be available on two of the four major carriers within a month and three of the four by late summer).&lt;br /&gt;&lt;br /&gt;But this is a major benefit to the merchant!&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/wK0chPpQJVg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/5885330508402775823/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=5885330508402775823&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/5885330508402775823?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/5885330508402775823?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/wK0chPpQJVg/ouch-another-major-breach-not-issue-for.html" title="Ouch, another major breach!  (Not an issue for Direct Carrier Billing!!!)" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>0</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2011/05/ouch-another-major-breach-not-issue-for.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEMCR3Y5fyp7ImA9WhZREko.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-8929622589858097861</id><published>2011-04-08T08:26:00.000-07:00</published><updated>2011-04-08T08:27:46.827-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-04-08T08:27:46.827-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Mobile Payments" /><category scheme="http://www.blogger.com/atom/ns#" term="Carrier Billing" /><title>Alternative Payment Systems Innovations Conference, San Francisco, 3/29-3/30</title><content type="html">I attended and moderated a panel at this conference on Alternative Payments.  The emphasis of the conference was Mobile, dah!  Isn’t every conference these days?  This was the 2nd annual version of this event and I would rate it a 7:10.  It attracted a very high quality group of speakers (present company excluded!).  It was missing a critical mass of attendees and especially prospective buyers in the form of merchants.  That is a common problem with most payments conferences, other than the Direct Response Forum and Merchant Risk Council which are both primarily merchant grass roots driven.&lt;br /&gt;&lt;br /&gt;The most profound thing that came out of this conference was a quote from a former colleague and now esteemed consultant, Richard Crone.    Richard stated; “the one who enrolls, is the one who controls” and further that “the carriers have the consumer’s payment info and access to leverage their device for security” and "are therefore in the best position to win in mobile payments".  I could not agree more with Richard and that is the why I came to BilltoMobile.  We are an extension of the carrier’s platform and leverage that existing enrollment and the ability to validate not only the phone but a 2nd factor of authentication, the billing zip code as well.&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/73-isXTMBgU" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/8929622589858097861/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=8929622589858097861&amp;isPopup=true" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/8929622589858097861?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/8929622589858097861?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/73-isXTMBgU/alternative-payment-systems-innovations.html" title="Alternative Payment Systems Innovations Conference, San Francisco, 3/29-3/30" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>3</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2011/04/alternative-payment-systems-innovations.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEAFSHk4cSp7ImA9WhZTGEg.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-8275857254080080487</id><published>2011-03-22T20:44:00.000-07:00</published><updated>2011-03-22T20:58:39.739-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-03-22T20:58:39.739-07:00</app:edited><title>Kindle Experience</title><content type="html">After 30 years having the Wall Street Journal delivered to my home and reading it every day, I switched to a Kindle subscription.&lt;br /&gt;They offer a 14 day trial and I am on day two.&lt;br /&gt;When I went to lunch today, I realized I did not have my Kindle with me but alas I had my iPhone which I had loaded the Kindle app on.&lt;br /&gt;I thought, GREAT, I can sit and eat and read the Journal.&lt;br /&gt;But, alas, it was not there. So, I emailed the customer inquiry link via the app and got a prompt answer back that newspaper and magazine subscriptions are only available on the Android Kindle app, not the iPhone Kindle app.  If this sort of thing persists, it could make consumers switch to a more open platform where they can have uninhibited access to content that they have rightfully paid for.&lt;br /&gt;This reminds me of a bygone era of closed systems (ie; Wang word processors and Sun servers that would only run Solaris, etc...) Well, we know what happened to Wang and Sun.&lt;br /&gt;What does this have to with payments?&lt;br /&gt;Well, this is a sensitive topic so I will leave it to your imagination.&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/saRlOAGUFdg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/8275857254080080487/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=8275857254080080487&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/8275857254080080487?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/8275857254080080487?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/saRlOAGUFdg/kindle-experience.html" title="Kindle Experience" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>0</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2011/03/kindle-experience.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Ck4CR3g8eip7ImA9Wx9bEEg.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-385864268329270143</id><published>2011-02-18T09:42:00.001-08:00</published><updated>2011-02-18T09:42:46.672-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-02-18T09:42:46.672-08:00</app:edited><title>Sprint Selects BilltoMobile to Enable Subscribers to Charge Online Purchases to Their Wireless Bill</title><content type="html">3 down, 1 to go!&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;&lt;a href="http://www.sys-con.com/node/1722563"&gt;Sprint Selects BilltoMobile to Enable Subscribers to Charge Online Purchases to Their Wireless Bill &lt;/a&gt;&lt;br /&gt;— BilltoMobile, the leading provider of mobile payments for web purchases, today announced a Direct Mobile Billing Gateway Service Provider agreement with Sprint (NYSE: S), which will allow Sprint customers to charge online purchases directly to their Sprint bill. Once implementation is complete in the coming months, merchants and payment resellers using BilltoMobile's mobile payment service will be able to offer this payment option to Sprint customers.&lt;/blockquote&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/5BZd1OuINIg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/385864268329270143/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=385864268329270143&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/385864268329270143?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/385864268329270143?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/5BZd1OuINIg/sprint-selects-billtomobile-to-enable.html" title="Sprint Selects BilltoMobile to Enable Subscribers to Charge Online Purchases to Their Wireless Bill" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>0</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2011/02/sprint-selects-billtomobile-to-enable.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUQHRX86fip7ImA9Wx9UFk4.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-3534910988074469168</id><published>2011-02-13T13:39:00.000-08:00</published><updated>2011-02-13T13:42:14.116-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-02-13T13:42:14.116-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="APSI" /><title>Alt Payments Systems Innovations Conference</title><content type="html">http://paymentinnovations.net/&lt;br /&gt;Hope to see you at this conference coming up in late March.&lt;br /&gt;Last year was the first in this series and I went (hey it was 10 minutes from my house) with my normal skepticism.&lt;br /&gt;Well, it was a very pleasant surprise.&lt;br /&gt;And, since I am speaking this year, I am looking forward to contributing to its value.&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/nQzDphEmQaI" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/3534910988074469168/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=3534910988074469168&amp;isPopup=true" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/3534910988074469168?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/3534910988074469168?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/nQzDphEmQaI/alt-payments-systems-innovations.html" title="Alt Payments Systems Innovations Conference" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>1</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2011/02/alt-payments-systems-innovations.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEYAQXw4fSp7ImA9Wx5aFUU.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-692531641168184224</id><published>2010-11-12T08:59:00.000-08:00</published><updated>2010-11-12T09:15:40.235-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-11-12T09:15:40.235-08:00</app:edited><title>meCommerce</title><content type="html">I thought, why not, it was almost Friday the 13th, how about coining a new phrase!  So, here you go, meCommerce - the convergence of m and e commerce with a cute spin.&lt;br /&gt;&lt;br /&gt;With all the spin about mobile and especially mobile payments, I thought I would have us think about what really matters and that is "me", the consumer side of me.  After all, this is the "me" economy isn't it?&lt;br /&gt;&lt;br /&gt;All that really matters to the consumer is that they have as seamless an experience as they can have across all the platforms and devices they utilize to maximize their time and money. &lt;br /&gt;&lt;br /&gt;As ecommerce evolved, those merchants who figured out how to blend the benefits of bricks and clicks delivered the most value to their customers.  Now, we have bricks, clicks and pockets (? - perhaps someone can contribute something better!!).&lt;br /&gt;&lt;br /&gt;Mobile, with the proliferation of smartphones which are just computers in your pocket that happen to also sometimes work as phones, present enourmous possibilites for enhancing the overall experience for the consumer.&lt;br /&gt;&lt;br /&gt;As it relates to payment, the only hang up is the explosion of "Walled Gardens 2.0" which serve to restrict the consumer from the freedom to pay how they wish and merchants the freedom to choose which payment methods they want to take and their ability to negotiate the best rates their volumes deserve.  These perhaps serve a purpose during an initial formative phase but they will disintegrate as the power shifts from the few to the many.&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/uru1BM4rBQA" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/692531641168184224/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=692531641168184224&amp;isPopup=true" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/692531641168184224?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/692531641168184224?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/uru1BM4rBQA/mecommerce.html" title="meCommerce" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>1</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2010/11/mecommerce.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkEGQHc_eSp7ImA9Wx5bGUo.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-4505480474918446505</id><published>2010-11-05T09:26:00.000-07:00</published><updated>2010-11-05T09:30:21.941-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-11-05T09:30:21.941-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Mobile Payments" /><category scheme="http://www.blogger.com/atom/ns#" term="Carrier Billing" /><title>Article on Direct Mobile Billing in Digital Transactions</title><content type="html">I am pleased to report that an article I authored is available in this month's issue.&lt;br /&gt;&lt;br /&gt;If you click on this link and then choose the November issue, you can read it;&lt;br /&gt;&lt;br /&gt;http://digitaltransactions.net/index.cfm?pageid=3&lt;br /&gt;&lt;br /&gt;It is on page 22.&lt;br /&gt;&lt;br /&gt;Would welcome your comments!&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/p0_MUCcZD9w" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/4505480474918446505/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=4505480474918446505&amp;isPopup=true" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/4505480474918446505?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/4505480474918446505?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/p0_MUCcZD9w/article-on-direct-mobile-billing-in.html" title="Article on Direct Mobile Billing in Digital Transactions" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>3</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2010/11/article-on-direct-mobile-billing-in.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEcMQn47eSp7ImA9Wx5bE0o.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-2674111932603127554</id><published>2010-10-29T10:03:00.000-07:00</published><updated>2010-10-29T10:08:03.001-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-10-29T10:08:03.001-07:00</app:edited><title>BilltoMobile Adds ATT (Only provider with both ATT &amp; Verizon)</title><content type="html">This has been a big week for the advancement of carrier billing for ecommerce purchases!  The company I work for BilltoMobile (powered by Danal Ltd, Korea) announced and launched support for ATT mobile users.  This is in addition to our previously announced and launched support for VZ users.  We now have 2/3rds of the US mobile user market covered and more to come!  We are the only provider that can provide the superior capabilities (ie; dynamic pricing, real-time auth and verification, limit management, dramatically lower dispute rates) and lower costs of Direct Mobile Billing (carrier billing 2.0 versus the legacy PSMS approach used by others) on both Verizon and ATT!!!&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/qmv-3FuBUHc" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/2674111932603127554/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=2674111932603127554&amp;isPopup=true" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/2674111932603127554?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/2674111932603127554?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/qmv-3FuBUHc/billtomobile-adds-att-only-provider.html" title="BilltoMobile Adds ATT (Only provider with both ATT &amp; Verizon)" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>3</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2010/10/billtomobile-adds-att-only-provider.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0AMQ3o-fyp7ImA9Wx5bE0o.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-3390777822761605025</id><published>2010-10-29T10:00:00.000-07:00</published><updated>2010-10-29T10:03:02.457-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-10-29T10:03:02.457-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Starbucks 2D Bar Code" /><title>Starbucks Extends Mobile Payments to Nearly 300 More Stores</title><content type="html">"(October 25, 2010) In the biggest expansion yet of mobile payments to its standalone stores, Starbucks Coffee Co. on Monday said it has equipped almost 300 company-owned stores in New York City and parts of Long Island to accept transactions using 2-D bar code technology. This expansion follows the Seattle-based coffee chain’s move this spring to install the technology in outlets located within more than 1,000 Target Corp. stores (Digital Transactions News, April 8). Starbucks started its mobile-payments pilot 13 months ago at 16 standalone stores, eight in Seattle and eight in California’s Silicon Valley."&lt;br /&gt;&lt;br /&gt;This is great news!  Only one problem!  I do not live in NYC anymore!  This approach overcomes a lot of issues that have plagued other approaches to connecting the physical world payment card to the mobile phone.&lt;br /&gt;&lt;br /&gt;Hopefully they will get back around to expanding in the Bay Area!&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/H1vPiXEVcS0" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/3390777822761605025/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=3390777822761605025&amp;isPopup=true" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/3390777822761605025?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/3390777822761605025?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/H1vPiXEVcS0/starbucks-extends-mobile-payments-to.html" title="Starbucks Extends Mobile Payments to Nearly 300 More Stores" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>1</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2010/10/starbucks-extends-mobile-payments-to.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkABQXs7eSp7ImA9Wx5SGE4.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-6898216484079100560</id><published>2010-08-14T17:55:00.000-07:00</published><updated>2010-08-14T18:12:30.501-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-08-14T18:12:30.501-07:00</app:edited><title>NFC vs 2D Bar Code for Mobile Retail POS?</title><content type="html">I know that this is not ecommerce related (at least not for the moment), but since Mobile Payments is the topic du jour, I thought I would comment on it.  So, what is it going to be?  NFC has been struggling for meaningful deployment for more than a few years and I think the time has passed.  Merchants (that matter) have already embraced bar code technology at the POS and if they are not already 2D capabable upgrading to it probably would not be as painful as installing single purpose (credit card network controlled) NFC readers.  They can then be in control of their own destiny at their POS and leverage the enhanced bar code technology for other purposes.  &lt;br /&gt;Why did NFC fail?  When you combine the fact that most large merchants (supermarkets and big boxers) had turned the terminals to the consumer so they could swipe the card themselves combined with the card brands new rules around no signature for under $25 transactions, a lot of the motivation for NFC which was checkout speed evaporated.&lt;br /&gt;The virtual Starbuck's stored value card iPhone app is the best example I have seen of such a deployment.  I only wish it was in more street locations.  I know it is now in all the Target based Starbucks but Target is not someplace I stop into on my way to work in the morning.  However, this is an interesting point as to why the Target locations were deployed so quickly as they already had the 2D bar code technology and a simple software upgrade accomplished the task.&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/gAELOXNNrws" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/6898216484079100560/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=6898216484079100560&amp;isPopup=true" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/6898216484079100560?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/6898216484079100560?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/gAELOXNNrws/nfc-vs-2d-bar-code-for-mobile-retail.html" title="NFC vs 2D Bar Code for Mobile Retail POS?" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>1</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2010/08/nfc-vs-2d-bar-code-for-mobile-retail.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkUBSXc8fCp7ImA9Wx5SEUg.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-1718356774773066881</id><published>2010-08-06T21:43:00.000-07:00</published><updated>2010-08-06T22:17:38.974-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-08-06T22:17:38.974-07:00</app:edited><title>Facebook Credits bought by Mobile Payments...Disclosure Needed or Not?</title><content type="html">I decided it was time to check out Facebook Credits.  Last nite I navigated my way to buying some not because I need any but just to see what the payments experience is.  I was curious if they were surcharging their "friends" when paying with a Mobile payment instead of credit card.  They are to the tune of roughly 50%.  The consumer gets 1/2 the number of Facebook Credits when they pay by charging to their mobile phone number.&lt;br /&gt;&lt;br /&gt;I realize that their merchant cost is high due to the carrier's fee and therefore it is not completely unreasonable to do this.&lt;br /&gt;&lt;br /&gt;What I do find unreasonable is that there is no clear disclosure of what the deal is.&lt;br /&gt;You have to click back and forth between the choices when wanting to pay with credit card and wanting to pay by Mobile and have to do the math in your head.&lt;br /&gt;&lt;br /&gt;When I shop at the supermarket, I expect to be able to look at the labels on the shelves and see that the Coke Zero in the 12 oz bottle costs me $.05/ounce and $.04/ounce in the 20 oz bottle.&lt;br /&gt;&lt;br /&gt;It is one thing for some low life elixer company to pull this sort of deception, but another for a company like Facebook that should care about their reputation and credibility.  And it should not require the government or some other body to monitor and enforce reasonable and ethical behaviour.&lt;br /&gt;&lt;br /&gt;The Mobile Marketing Association guidelines prohibit surcharging the consumer.  But, no one is enforcing those.  Of course, this reminds me of an earlier post about Visa rules being ignored right under Visa's nose;  http://paymenttalk.blogspot.com/2008/05/rules-are-made-to-be-broken.html &lt;br /&gt;&lt;br /&gt;What do you think?&lt;br /&gt;&lt;br /&gt;BTW, I am going to dispute this transaction.  I tried cancelling it afterwards following the instructions in the text by texting back "STOP" and even got a text seemingly confirming that the transaction had been "discontinued", but since the 16 credits I bought did not get taken from my Facebook Credits balance, I am presuming either this is a delayed process or simply does not work.  I will call the mobile payments company first and see how they handle it.  Then I guess I get to call Facebook and then if all else fails, AT&amp;T.  Stay tuned!&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/0OyPVG-w2LM" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/1718356774773066881/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=1718356774773066881&amp;isPopup=true" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/1718356774773066881?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/1718356774773066881?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/0OyPVG-w2LM/facebook-credits-bought-by-mobile.html" title="Facebook Credits bought by Mobile Payments...Disclosure Needed or Not?" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>2</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2010/08/facebook-credits-bought-by-mobile.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DU4HQXc7cCp7ImA9WxFbF0Q.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-6106697801254842590</id><published>2010-07-10T14:31:00.000-07:00</published><updated>2010-07-10T14:38:50.908-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-10T14:38:50.908-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Mobile Payments" /><title>Mobile Payments ... Uuh?</title><content type="html">There is a lot of buzz in the "mobile payments" space.  But, of course, there is also a lot of BS.  But, the issue for this post is simply the issue of the category name.  Unfortunately this term has come to be used for such a wide variety of types of payments that it has totally lost its meaning.  Just because a credit card processing app happens to sit on an iphone, does that really qualify as some kind of breakthrough?  As they would say in S. CA - pleeeeeeeeeeeeeeeeeeeease!&lt;br /&gt;&lt;br /&gt;Of course, if you are out looking for money or free PR, you want to be associated with a hot category.  And the pundits just eat it up.&lt;br /&gt;&lt;br /&gt;So, I have not written in awhile since I just switched to a Mobile Payments company.  ha ha!  www.billtomobile.com&lt;br /&gt;&lt;br /&gt;Actually, we are doing REAL mobile payments where the charge is placed on the wireless carrier bill, not just using some mobile device as a proxy for a credit/debit card.&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/FwlzzBUM6no" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/6106697801254842590/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=6106697801254842590&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/6106697801254842590?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/6106697801254842590?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/FwlzzBUM6no/mobile-payments-uuh.html" title="Mobile Payments ... Uuh?" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>0</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2010/07/mobile-payments-uuh.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEAASHk5eSp7ImA9WxFXGE0.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-1718046229371906218</id><published>2010-05-25T08:50:00.000-07:00</published><updated>2010-05-25T08:52:29.721-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-05-25T08:52:29.721-07:00</app:edited><title>Facebook's Rich Valuation Based On E-Payments</title><content type="html">Facebook's Rich Valuation Based On E-Payments That May Never Come &lt;br /&gt;http://industry.bnet.com/technology/10008222/is-facebooks-valuation-based-on-e-payments-that-will-never-come/ &lt;br /&gt;&lt;br /&gt;This is an entertaining article.  Anyone who lists Obopay as a leader in this domain is only looking at it from the perspective of having raised a lot of money versus actually accomplishing anything in the market.  And, while Amazon is an incredibly successful ecommerce merchant, as a payment platform provider to others, not so much.  PayPal, no argument.  And as compelling as Facebook is to some, the likelyhood that if neither Google or Amazon can make their payment initiatives meaningful after pouring hundreds of millions of dollars into them, take a guess at my prognosis.  There is nothing wrong inherently with Facebook credits, but it is unlikely to rock the payments world.   It is just another layer on top of an already complicated and competitive landscape.  p.s.  As others have found out, the devil is in the details and the devil is expensive in the form of customer service and managing fraud and disputes.  Playing around in your social network is entertaining and sometimes productive, but when you touch the user's wallets the rules change.&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/0TxiuivWRxg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/1718046229371906218/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=1718046229371906218&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/1718046229371906218?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/1718046229371906218?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/0TxiuivWRxg/facebooks-rich-valuation-based-on-e.html" title="Facebook's Rich Valuation Based On E-Payments" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>0</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2010/05/facebooks-rich-valuation-based-on-e.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkYEQHwzeCp7ImA9WxFSGEQ.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-6753673217315654898</id><published>2010-04-21T15:48:00.000-07:00</published><updated>2010-04-21T15:48:21.280-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-04-21T15:48:21.280-07:00</app:edited><title>Paying with Plastic - pymnts.com</title><content type="html">&lt;a href="http://pymnts.com/paying-with-plastic"&gt;Paying with Plastic - pymnts.com&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Just read this free first chapter and based on my knowledge of the payments industry it is one of the best I have read.  Great job!&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/kbZbi9_iyh8" height="1" width="1"/&gt;</content><link rel="related" href="http://pymnts.com/paying-with-plastic" title="Paying with Plastic - pymnts.com" /><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/6753673217315654898/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=6753673217315654898&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/6753673217315654898?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/6753673217315654898?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/kbZbi9_iyh8/paying-with-plastic-pymntscom.html" title="Paying with Plastic - pymnts.com" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>0</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2010/04/paying-with-plastic-pymntscom.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEIFQ307cCp7ImA9WxFSGEg.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-1759773830513758784</id><published>2010-04-21T06:25:00.001-07:00</published><updated>2010-04-21T06:28:32.308-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-04-21T06:28:32.308-07:00</app:edited><title>Visa paying $2B for payments processor CyberSource</title><content type="html">Congrats to CyberSource!!!&lt;br /&gt;I take a great deal of pride from having developed, signed and managed the relationship with Visa 11 years ago in spite of much skepticism both internally and externally!!!  Visa invested $1.5m in CyberSource pre-ipo and agreed to the joint product, CyberSource Advanced Fraud Screen Enhanced by Visa.  :-)  Oh, the stories I could tell you!&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/MxlKmaMko1I" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/1759773830513758784/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=1759773830513758784&amp;isPopup=true" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/1759773830513758784?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/1759773830513758784?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/MxlKmaMko1I/visa-paying-2b-for-payments-processor.html" title="Visa paying $2B for payments processor CyberSource" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>1</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2010/04/visa-paying-2b-for-payments-processor.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0UCQXw4eyp7ImA9WxFSE0g.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-2078664385932663490</id><published>2010-04-15T09:36:00.000-07:00</published><updated>2010-04-15T10:07:40.233-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-04-15T10:07:40.233-07:00</app:edited><title>Data Portability in a PCI Crazy World!</title><content type="html">I have written previously about service providers such as gateways and payment processors holding their customers data hostage using PCI as the excuse.
&lt;br /&gt;&lt;meta equiv="Content-Type" content="text/html; charset=utf-8"&gt;&lt;meta name="ProgId" content="Word.Document"&gt;&lt;meta name="Generator" content="Microsoft Word 12"&gt;&lt;meta name="Originator" content="Microsoft Word 12"&gt;&lt;link rel="File-List" href="file:///C:%5CDOCUME%7E1%5Csklebe%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"&gt;&lt;link rel="themeData" href="file:///C:%5CDOCUME%7E1%5Csklebe%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"&gt;&lt;link rel="colorSchemeMapping" href="file:///C:%5CDOCUME%7E1%5Csklebe%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;  &lt;w:worddocument&gt;   &lt;w:view&gt;Normal&lt;/w:View&gt;   &lt;w:zoom&gt;0&lt;/w:Zoom&gt;   &lt;w:trackmoves/&gt;   &lt;w:trackformatting/&gt;   &lt;w:punctuationkerning/&gt;   &lt;w:validateagainstschemas/&gt;   &lt;w:saveifxmlinvalid&gt;false&lt;/w:SaveIfXMLInvalid&gt;   &lt;w:ignoremixedcontent&gt;false&lt;/w:IgnoreMixedContent&gt;   &lt;w:alwaysshowplaceholdertext&gt;false&lt;/w:AlwaysShowPlaceholderText&gt;   &lt;w:donotpromoteqf/&gt;   &lt;w:lidthemeother&gt;EN-US&lt;/w:LidThemeOther&gt;   &lt;w:lidthemeasian&gt;X-NONE&lt;/w:LidThemeAsian&gt;   &lt;w:lidthemecomplexscript&gt;X-NONE&lt;/w:LidThemeComplexScript&gt;   &lt;w:compatibility&gt;    &lt;w:breakwrappedtables/&gt;    &lt;w:snaptogridincell/&gt;    &lt;w:wraptextwithpunct/&gt;    &lt;w:useasianbreakrules/&gt;    &lt;w:dontgrowautofit/&gt;    &lt;w:splitpgbreakandparamark/&gt;    &lt;w:dontvertaligncellwithsp/&gt;    &lt;w:dontbreakconstrainedforcedtables/&gt;    &lt;w:dontvertalignintxbx/&gt;    &lt;w:word11kerningpairs/&gt;    &lt;w:cachedcolbalance/&gt;   &lt;/w:Compatibility&gt;   &lt;w:browserlevel&gt;MicrosoftInternetExplorer4&lt;/w:BrowserLevel&gt;   &lt;m:mathpr&gt;    &lt;m:mathfont val="Cambria Math"&gt;    &lt;m:brkbin val="before"&gt;    &lt;m:brkbinsub val="&amp;#45;-"&gt;    &lt;m:smallfrac val="off"&gt;    &lt;m:dispdef/&gt;    &lt;m:lmargin val="0"&gt;    &lt;m:rmargin val="0"&gt;    &lt;m:defjc val="centerGroup"&gt;    &lt;m:wrapindent val="1440"&gt;    &lt;m:intlim val="subSup"&gt;    &lt;m:narylim val="undOvr"&gt;   &lt;/m:mathPr&gt;&lt;/w:WordDocument&gt; &lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;  &lt;w:latentstyles deflockedstate="false" defunhidewhenused="true" defsemihidden="true" defqformat="false" defpriority="99" latentstylecount="267"&gt;   &lt;w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Normal"&gt;   &lt;w:lsdexception locked="false" priority="9" semihidden="false" unhidewhenused="false" qformat="true" name="heading 1"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 2"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 3"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 4"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 5"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 6"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 7"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 8"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 9"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 1"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 2"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 3"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 4"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 5"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 6"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 7"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 8"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 9"&gt;   &lt;w:lsdexception locked="false" priority="35" qformat="true" name="caption"&gt;   &lt;w:lsdexception locked="false" priority="10" semihidden="false" unhidewhenused="false" qformat="true" name="Title"&gt;   &lt;w:lsdexception locked="false" priority="1" name="Default Paragraph Font"&gt;   &lt;w:lsdexception locked="false" priority="11" semihidden="false" unhidewhenused="false" qformat="true" name="Subtitle"&gt;   &lt;w:lsdexception locked="false" priority="22" semihidden="false" unhidewhenused="false" qformat="true" name="Strong"&gt;   &lt;w:lsdexception locked="false" priority="20" semihidden="false" unhidewhenused="false" qformat="true" name="Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="59" semihidden="false" unhidewhenused="false" name="Table Grid"&gt;   &lt;w:lsdexception locked="false" unhidewhenused="false" name="Placeholder Text"&gt;   &lt;w:lsdexception locked="false" priority="1" semihidden="false" unhidewhenused="false" qformat="true" name="No Spacing"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" unhidewhenused="false" name="Revision"&gt;   &lt;w:lsdexception locked="false" priority="34" semihidden="false" unhidewhenused="false" qformat="true" name="List Paragraph"&gt;   &lt;w:lsdexception locked="false" priority="29" semihidden="false" unhidewhenused="false" qformat="true" name="Quote"&gt;   &lt;w:lsdexception locked="false" priority="30" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Quote"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="19" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="21" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="31" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Reference"&gt;   &lt;w:lsdexception locked="false" priority="32" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Reference"&gt;   &lt;w:lsdexception locked="false" priority="33" semihidden="false" unhidewhenused="false" qformat="true" name="Book Title"&gt;   &lt;w:lsdexception locked="false" priority="37" name="Bibliography"&gt;   &lt;w:lsdexception locked="false" priority="39" qformat="true" name="TOC Heading"&gt;  &lt;/w:LatentStyles&gt; &lt;/xml&gt;&lt;![endif]--&gt;&lt;style&gt; &lt;!--  /* Font Definitions */  @font-face 	{font-family:"Cambria Math"; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:roman; 	mso-font-pitch:variable; 	mso-font-signature:-1610611985 1107304683 0 0 159 0;} @font-face 	{font-family:Calibri; 	panose-1:2 15 5 2 2 2 4 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:swiss; 	mso-font-pitch:variable; 	mso-font-signature:-1610611985 1073750139 0 0 159 0;}  /* Style Definitions */  p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-unhide:no; 	mso-style-qformat:yes; 	mso-style-parent:""; 	margin:0in; 	margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:12.0pt; 	font-family:"Times New Roman","serif"; 	mso-fareast-font-family:Calibri; 	mso-fareast-theme-font:minor-latin;} a:link, span.MsoHyperlink 	{mso-style-noshow:yes; 	mso-style-priority:99; 	color:blue; 	text-decoration:underline; 	text-underline:single;} a:visited, span.MsoHyperlinkFollowed 	{mso-style-noshow:yes; 	mso-style-priority:99; 	color:purple; 	mso-themecolor:followedhyperlink; 	text-decoration:underline; 	text-underline:single;} .MsoChpDefault 	{mso-style-type:export-only; 	mso-default-props:yes; 	font-size:10.0pt; 	mso-ansi-font-size:10.0pt; 	mso-bidi-font-size:10.0pt;} @page Section1 	{size:8.5in 11.0in; 	margin:1.0in 1.0in 1.0in 1.0in; 	mso-header-margin:.5in; 	mso-footer-margin:.5in; 	mso-paper-source:0;} div.Section1 	{page:Section1;} --&gt; &lt;/style&gt;&lt;!--[if gte mso 10]&gt; &lt;style&gt;  /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-priority:99; 	mso-style-qformat:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin:0in; 	mso-para-margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:"Times New Roman"; 	mso-fareast-theme-font:minor-fareast; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} &lt;/style&gt; &lt;![endif]--&gt;
&lt;br /&gt;There are two new efforts underway to raise the awareness of these inappropriate practices;
&lt;br /&gt;
&lt;br /&gt;portabilitystandard.org
&lt;br /&gt;
&lt;br /&gt;groups.google.com/group/credit-card-data-portability
&lt;br /&gt;
&lt;br /&gt;Please check out these two web pages and join the Google group on the subject.
&lt;br /&gt;
&lt;br /&gt;Welcome your feedback!!!
&lt;br /&gt;
&lt;br /&gt;Note - that the story I wrote about last fall is still not resolved.
&lt;br /&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/xSqOhMeXS1U" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/2078664385932663490/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=2078664385932663490&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/2078664385932663490?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/2078664385932663490?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/xSqOhMeXS1U/data-portability-in-pci-crazy-world.html" title="Data Portability in a PCI Crazy World!" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>0</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2010/04/data-portability-in-pci-crazy-world.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0EDR349fSp7ImA9WxFSEUQ.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-7598157018143257107</id><published>2010-04-13T14:51:00.001-07:00</published><updated>2010-04-13T14:54:36.065-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-04-13T14:54:36.065-07:00</app:edited><title>Do Not Assume Payment Methods Are Universal! Neither Demographically or Geographically!</title><content type="html">One of the challenges we all face is being able to step out of what works for us and understand what any one or group of our customers is going to have a preference for. This is especially true for payment choices. The closest thing we have to “universal” in ecommerce is Visa/MasterCard. But, if you are selling to Germans, you better support something called ELV which is a form of direct debit or move on to another country. And, as a person with a marketing degree I have a hard time saying this, but surveying your customers to ask them what payment methods they want or what is most important about those choices, may lead you down the wrong path. What people say they want and how they act in this regard can be significantly disconnected. ie; Is security important to you? Who is going to say “no”? But, many payment methods have fallen flat on their face if the hurdles to usability are significant due to security. What was one of the things that made PayPal grow incredibly fast? All you needed was an email address. Of course, their fraud rates were through the roof too but they had the luxury of taking in a whole bunch of VC money and being able to tolerate the cost and eventually they dug themselves out of the hole. Two of the most important questions you have to ask yourself are; 1) what is my target demographic and 2) what geographies do I want to serve?  Then and only then can you seriously research the options and start making decisions about what to offer.&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/e4mizYBqKQg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/7598157018143257107/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=7598157018143257107&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/7598157018143257107?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/7598157018143257107?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/e4mizYBqKQg/do-not-assume-payment-methods-are.html" title="Do Not Assume Payment Methods Are Universal! Neither Demographically or Geographically!" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>0</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2010/04/do-not-assume-payment-methods-are.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0INRH86fSp7ImA9WxBaGEU.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-7673207617937409584</id><published>2010-03-29T09:32:00.001-07:00</published><updated>2010-03-29T09:53:15.115-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-03-29T09:53:15.115-07:00</app:edited><title>More on New Text Alert System...</title><content type="html">So, there it was this morning, the email from Wells about this transaction that took place last Thursday.&lt;br /&gt;&lt;br /&gt;The only comment that I would make about this new mobile text alerting system from Visa that Wells has now deployed is that it should have been automatic that when I enrolled for that, the previous (and mostly useless) email alerting enrollment should have been cancelled or at least I should have been able to modify/cancel it.&lt;br /&gt;&lt;br /&gt;My guess is that I was actually enrolling for the mobile alerts on a Visa hosted page, branded Wells Fargo.  Even if it is not hosted by Visa on Well's behalf, it is clear that the two systems are not in synch.  I had to go this morning and de-select the overlapping alerts.  The site is; &lt;a href="https://rapidalerts.wellsfargo.com/rapidalerts/"&gt;https://rapidalerts.wellsfargo.com/rapidalerts/&lt;/a&gt; .&lt;br /&gt;&lt;br /&gt;Referencing my background dealing with Phishing issues (ie; PassMark Security), the Catch-22 with all of these things is the possibility that something potentially good, like these real-time text alerts, can be just another oppty for phishing attacks.  A url like the one above could (or should) make someone like me suspicious of if I am really at a legit Wells Fargo page or not.   It is also interesting to note that Wells (or Visa) chose not to invest in a "secure" url for such a sensitive page as this.    You know those green urls from Verisign and others called Extended Validation SSL Certificates.  While I do not put much stock in these (or any of the "trust" seals), I doubt they cost considerably more and I guess they cannot hurt.&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/0ix-myo41jw" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/7673207617937409584/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=7673207617937409584&amp;isPopup=true" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/7673207617937409584?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/7673207617937409584?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/0ix-myo41jw/more-on-new-text-alert-system.html" title="More on New Text Alert System..." /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>2</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2010/03/more-on-new-text-alert-system.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CE8BRnc4fip7ImA9WxBaFUg.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-1674243575148933385</id><published>2010-03-25T14:13:00.000-07:00</published><updated>2010-03-25T14:34:17.936-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-03-25T14:34:17.936-07:00</app:edited><title>Fair is Fair....Hats off to Visa...Genuine progress in fraud prevention!</title><content type="html">Wells Fargo announced a few days ago that they were taking advantage of a new Visa feature. Of course, I had to immediately enroll. You then receive text message alerts when certain types and size of transactions occur. The idea is that if it isn't you, you can immediately respond and become part of the fraud prevention paradigm. I was somewhat skeptical, as usual, but as it turned out hours later I was picking up my wife's BMW from the shop (ouch $1200!!!) and while I was still standing at the check-out desk, my phone got a text reporting the transaction to me. It was very descriptive, telling me that my "Wells Fargo Card ending in xx was used at xxx Motors in xxx town for $xxxx.xx ....&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;This is real progress.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;I had previously enrolled in their alerting offer but due to the number of different acquirers and issuers and the batch nature of credit card processing, these often did not arrive until days later.&lt;br /&gt;&lt;br /&gt;Since, Visa's switch is involved in the authorization of all Visa transactions, these alerts can go out literally in real time.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Of course someone will try and call this a mobile payment! (see my article in Venture Beat!)&lt;br /&gt;&lt;a href="http://venturebeat.com/2010/03/10/what-will-it-take-to-make-mobile-payments-mainstream-in-the-us/" target="_blank"&gt;http://venturebeat.com/2010/03/10/what-will-it-take-to-make-mobile-payments-mainstream-in-the-us/&lt;/a&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/ba-UzlTRGko" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/1674243575148933385/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=1674243575148933385&amp;isPopup=true" title="6 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/1674243575148933385?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/1674243575148933385?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/ba-UzlTRGko/fair-is-fairhats-off-to-visagenuine.html" title="Fair is Fair....Hats off to Visa...Genuine progress in fraud prevention!" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>6</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2010/03/fair-is-fairhats-off-to-visagenuine.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0UGRn86eip7ImA9WxBbEE0.&quot;"><id>tag:blogger.com,1999:blog-533875004410874344.post-385821612091807142</id><published>2010-03-07T15:33:00.001-08:00</published><updated>2010-03-07T15:40:27.112-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-03-07T15:40:27.112-08:00</app:edited><title>Progress...Finally!</title><content type="html">Interesting tidbit in the WSJ yesterday - The Fed is down to one site in Cleveland, Ohio from forty five sites 7 years ago that processed paper checks. I specifically recall sitting with the CEO of the company I worked for back in the early '80s as he proclaimed we would be completely checkless within that decade. And you wonder where I get my skepticism about the pace of change in payments!!!!&lt;img src="http://feeds.feedburner.com/~r/blogspot/AuDw/~4/gh49uvrVdG0" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://paymenttalk.blogspot.com/feeds/385821612091807142/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=533875004410874344&amp;postID=385821612091807142&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/385821612091807142?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/533875004410874344/posts/default/385821612091807142?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/AuDw/~3/gh49uvrVdG0/progressfinally.html" title="Progress...Finally!" /><author><name>SKlebe</name><uri>http://www.blogger.com/profile/02019096269180273665</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="21" height="32" src="http://2.bp.blogspot.com/-KubBIX_kEMs/TVhSOfc6u2I/AAAAAAAAAIg/HKZdYm6Dzl4/s220/mayer_008.JPG" /></author><thr:total>0</thr:total><feedburner:origLink>http://paymenttalk.blogspot.com/2010/03/progressfinally.html</feedburner:origLink></entry></feed>
