In particular, I like the way The Pirate Bay (and others) have used QR codes to facilitate easy payments and donations. The QR codes contain only three variables - the payment method (BitCoin), the destination, and a message. As this is a donation there is no value set. There is a full specification for a BitCoin URI scheme which I think is fairly well designed.

I envisage a day when, on asking for the bill at a restaurant, I am presented with a paper slip totting up my purchases with a neat QR code printed at the bottom. Scanning the code will pull up my banking or credit card app and allow me to make a payment. A verifiable receipt is either shown on screen or sent directly to the restaurant.

For example:

PAY:
 WHO:Pizza Palace
 IBAN:GB29NWBK60161331926819
 CUR:EUR
 VAL:27.35
 REF:123456qwerty
 TIME:1370886496

That's enough human readable information - and machine data - to ensure the correct payment gets from one person to another. I'm sure there are some other fields which may be advantageous to add; tax rate, specific location, etc. But it certainly all fit within a QR code.

QR codes can easily be printed out using the current infrastructure of mobile POS terminals. Those terminals already have mobile network access so can be alerted in real-time when the payment is made. IBAN means we have an easy(ish) way to uniquely identify payment destinations. And, in the UK at least, we have a fairly rapid payments infrastructure.

What's needed is a simple standard and mobile banking and credit card apps to support it.

Simple...

Last year I blogged about how easy it would be to pay for parking via QR code. Now it looks like Islington Council have partnered with Verrus to make this a reality.

But is it any good? Well.... nearly. Let's take a look.

The Initial Impression

The QR code is fairly clear and I was able to scan it without issue underneath street lighting. Sadly, there is no call to action. What does scanning the code do? (My camera has somehow mangled the photo. Sorry!)

Code Density

They've used the highest level of error correction ("Q") which is a good idea. In an external environment codes can get damaged or dirty. The higher the EC, the more chance the code will be readable.

However, they've shot themselves in the foot by using an absurdly long URL for analytics purposes.

http://m.paybyphone.co.uk/?
   utm_source=islington&
   utm_medium=qrcode&
   utm_campaign=mweb

Surely this could be made more efficient?

http://m.paybyphone.co.uk/?s=islngtn&m=qr&c=2

Or even better

http://m.paybyphone.co.uk/123456&s=qr

Because, you see, the code only goes to the main payment site - leaving the user to type in the parking bay's ID number.

Code Destination

After scanning the code, this is what the first time user sees.

Annoyingly they've hardcoded the zoom - so users with impaired vision (or fat fingers) won't be able to use the site.

<meta name="viewport" content="width=320,
   target-densitydpi=160,
   maximum-scale=1.0" />

The site is a little bland - and the "sign up" button is hidden out of the way - but it's the functionality which concerns me the most.

Registering

If you've never used the system before, you need to register on this screen. While it's good that they'll take payment from international users, it's plain dumb to require someone to type in a credit card number.

What if there's a gang of vicious hoodies waiting to snatch credit cards from unsuspecting users? How fiddly is it to type out a 16 digit number when you're in a hurry to park? Who is going to remember yet another password or PIN?

(Incidentally, take a look at the above screenshot. Is their branding "paybyphone" or "PayByPhone"?)

Solutions?

Here's how I would set the scheme up...

1. URL in the QR code reflects the location it is in. E.G. http://m.paybyphone.co.uk/123456
2. User scans code, selects the amount of parking they want to pay for. Clicks "Pay".
3. A mobile payment solution charges the amount to the user's bill, or deducts it from their credit.
4. User walks away happy. No need to register or remember a Personal PIN Number for identifying herself.

Scan, select, click. No typing, no memorising, no hassle. Surely that's better than fiddling around with credit cards?

Overall

A little disappointing. A great first step, but it could be made so much easier with mobile payments.

Disclaimer:

I currently work for InMobi who have a product called SmartPay. There are several other cross-network payment solutions like Boku or Beem.

This blog is personal and does not represent my employers in any way.

After playing around for a bit, I discovered that it was easy to block The Times from reading a blog, but I couldn't find an easy way to disable the paywall on receipt of payment.

So, I've set up a voluntary paywall.  It's in the sidebar - and looks something like this...

This was partly a way for me to play with the Google Checkout API - which is surprisingly easy to integrate and works flawlessly on mobile. It's also partly a way to earn some money.  I did consider flattr which - while cool - doesn't seem to have much momentum behind it yet.  I know that PayPal has some great APIs, but I find them to be overkill for what I need.

How Is This Different From A "Donate" Button?

It is, granted, a question of semantics.  I run a business - I'm not asking for handouts or donations.  You are paying my business in return for reading this blog.

I'm pretty sure this is an original idea.  At the very least, I've conquered the SEO for "voluntary paywall".

How? Why? What?

Ideally, I'd like people to name their own price for what they think this blog is worth.  Unfortunately, as Cory Doctorow and I found out - that's not that easy to do yet.

Cory Doctorow NONCONSENSUAL BLUE TICK

@doctorow

Thanks to all who replied to my #GoogleCheckout request with suggestions for kludging variable price (esp @edent http://tinyurl.com/33j73rr)

---

I don't claim this blog to be the best thing since sliced-bread.  At best, I reckon it's slightly more coherent than the hideous cloaca that is Richard Littlejohn.

There's also a good deal of technical content which, if my blog stats are anything to go by, is still interesting to the geeks of the world.

Occasionally I get linked to by some big names like Reddit, or Wired, or Boing Boing, or The Guardian, or any of the other fabulous blogs out there.  It's a bit like getting name-checked by a celebrity; I know it shouldn't mean much - but it does put a smile on my face.

Overall, as I reach the third anniversary of this blog, I'm pretty happy with it.  If you're happy with it, chuck a few coppers in the box.  It won't make me rich, it may not even pay for the hosting costs, but it will let me know you enjoy what I do.

As ever, I'm happy to answer questions on how this paywall works, how you can set one up yourself, what the fees are, etc.  Just leave a comment.

Bootnote

A big round of applause to Philip Oakley - who has just become my first paying customer.  I guess that means I can stick "Professional Blogger" on my CV now...