3615, L’arrivée d’internet dans le monde de la finance – [French]

Sean Park and myself had the chance to be invited to the swiss radio show 36 15: http://www.facebook.com/3615emission to speak Finance innovation and startups.

While recorded in the English speaking swiss radio, it is in French only (well frenglish …)

EPCA Payment Summit – Innovation in the Payment space

I had the chance to be invited by the team of the EPCA Payment Summit to present on how innovation is changing the way we pay. Here is the Prezi of my talk:

The startups mentioned are:
http://squareup.com
http://paypal.com
http://izettle.com
http://movenbank.com
http://bill.com
http://tradeshift.com
http://xero.com
http://simple.com
http://stripe.com
http://braintreepayments.com
http://kabbage.com
http://facebook.com
http://bitcoin.org
http://picomoney.com

also referenced:
http://carlotaperez.org
http://www.shirky.com

The Core of the Machine – Banking as a Utility

I have been a strong partisan of Banking as a Service and posted several times on the topic on this blog. Recently I have posted more on the shiny outer layers that could be / are created in such a stack but not so much of the core services under it. So it was with interest that I saw @giyom‘s tweet

A banking utility doesn’t buy debts, issue liabilities nor do maturity transformation, it only is a trusted accountant btw borrowers&debtors

It’s an interesting view, a pure banking utility would provide the pipes to connect depositors and borrowers and maintain the accounting trust between the two, whether direct, in a P2P lending type model, or indirect by reporting aggregated assets and loans. @giyom pointed me also to Dan Kaminsky analysis of  Bitcoin: http://www.slideshare.net/dakami/bitcoin-8776098 - slide 14 and 15 are interesting in his analysis that supernodes in Bitcoin are effectively banks.

In parallel, a second French bank announced the launch of its API: AXA Banque (Credit Agricole was the first one with CAstore). I had the chance to talk with people there and while the current API is READ only, the mention of WRITE capabilities was not rejected from the outset. A Bank that proposes a READ/WRITE API is in effect giving up on a part of the their customer access and accepting its role as a utility for other services (as I pointed out before, it is something well know in the banking industry)

It seems that from both end of the spectrum, whether its is the  technology enabled P2P or traditional Banking, we are moving toward the creation of banking utilities. But what would be the business model of such players?

On one hand, in the P2P lending example and as specified by giyom, the role of the core provider is track and ensure the relationships between borrowers and lender as well as provide additional services such as transparency in the capacities of the borrowers and loan recovery in the situation of a default. In this system, the trusted core providers would have no leverage nor insurance (as deposit accounts are currently protected). In theory, insurance could be provided by an external provider up to certain amount and based on the lenders selected. The business model of such a platform is fee based.

This is the system adopted by platforms such as Zopa,

On the other hand, in a banking platform world, the bank uses the top layer as a deposits aggregators. It can provide non-interest bearing accounts and base interest bearing accounts the aggregator, as well as transaction facilities to help move money between various accounts. It provides the underlying regulated insurance to the end users. This source of deposits become a part of its core assets mix, which can be leveraged for lending. The same or other providers could be provided these lending facilities, with various rates based on risk etc.. The business model of such a platform is spread based.

This is the system adopted by platforms such as Friendsclear

The distinction made above is not as pure in reality. Zopa, LendingClub etc are using banks to manage cash accounts, payments etc..

I think the total disintermediation for banks is not for now and the two systems will live at the same time. What do you think?

Quick ramblings on Mobile Wallet UI

MWC is going full speed in Barcelona and each day has its new payment solution, mobile wallet, magic integrator. I was particularly interested in hearing more from Isis, the Super PAC of US mobile networks (AT&T, T-Mobile and Verizon Wireless).

ISIS wallet solution starts with a list of cards, based on the real world wallet paradigm. This is based on a constraint of  the real world. All your cards have to physically be present in your wallet and you choose them based on the provider (hence the leather wallet cards organization). This requires a particular thinking on the user side, reviewing cash level and benefit of each card vs the payment to be made.

Note: the feed is interesting, I could not find much details. It seems like people will be able to follow businesses for offers and information.

Google Wallet follows a rather similar scheme, with cards put upfront, and a swipeable Wallet. The history is the equivalent of the receipts mess in the wallet, though in a much organised way.

For me, this shows either in the best case a conservative fear of changing things for customers or in the worst case a difficulty to understand how much the mobile platform offers. Because the wallet looked like this for centuries does not mean it is supposed to look like this on a mobile.

It may be cliché but worth repeating:

A modern cell phone has more computer power than all of NASA back in 1969, when it placed two astronauts on the moon.

I would add that: not only that but it has an incredible array of captors: camera, GPS,etc.. and access to information and computing power via internet connectivity.

Lets use Square Card Case as an example:

From the outside it looks just the same: Wallet (with skeuomorphism – thanks @aden_76 for the word), Slots, Card. Except they are not Credit Card, they are Store Cards…. As I have said before Card Case is built around the Buying Experience, not the Payment Experience so it makes sense they highlight merchants and products.

“But wait, there are tons of merchants, how would they fit on my phone screen?” Why would they need to all be on your screen? The merchants’ cards can dynamically adjust based on location, time during the day (restaurants put forward during lunch time), past buying experience. Sponsored merchants could be given a preferred space in the wallet.

This is one possibility, but there are others. As Brett King pointed out in Mobile Banking vs. The Mobile Wallet

Whether it is simply the fact that I can see my balance before and after I make a payment (not possible with plastic, cheques or cash) or whether you can start to advise me day-to-day on how to utilize my money better – the opportunity for mobile is not the wallet, and not mobile banking. It is re-imagining the utility of banking from a mobile perspective.

The technology offer us the opportunity to help people in doing what they currently almost without thinking try to do (badly). What is my balance, what are the advantages of each card, what should I pay with? Not only a big part of this logic is better computed by a machine than by a person, but a well designed UI can inform and help in this decision.

Instead of showing cards the mobile wallet could show payment options cost and opportunities.

I am hopeful we will see more and more of the latter, designed by people who have no preconception on how it should look like. 

The receipt revolution!

I am mad about receipts. As I have written before:

- The receipt is the perfect example of a broken experience, as defined by Seth Godin.

Seth Godin at Gel 2006 from Gel Conference on Vimeo.

Look at any typical receipt and you would have a hard time understanding most of it. Batch numbers, RRN, Terminal Id, Merchant #, and other random pieces of numbers and letters. In most cases the product name is not even recognizable and the merchant name is broadly defined. If you try to remember where you bought a product, how much it was etc, chances are al receipt will not help you because it is not designed for the customer.

But improving the receipt is not just about making it more clear, sending it by email, putting it on the web… Making receipts an experience may become a key aspect of mobile payments. The question is : what needs to happen when payments disappear?

One of the goals of Square (and Card Case is a first step in this direction) is to change the payment experience:

“This is truly the most seamless way to pay,” said Megan Quinn, director of products for Square. “It becomes more about the interaction between customer and merchant and that relationship rather than the actual act of the payments. We want to make payments fade away. People don’t appreciate that; they enjoy making a purchase and feeling like a regular at places they shop.”

Square’s “magic” has nothing to do with its dongle but is with its capacity to be the first coherent and complete link between the merchant and the customer. Controlling the all experience is key to extract the most benefit from the payment graph : always accurate product catalog, real identity, metadata on payment (localization, time, previous payments and patterns), all these elements create a rich data set for each payment, that can benefit both the merchant and the customer. In the middle of this, as a memento of each purchase made, is the receipt. But a purchase is not/ should not be a static event. If your best customers are regular customers, you need to maintain a constant relationship with them and they may be interested as well in engaging more with your business. Receipts could become implicit social graphs.

The first and most obvious use of social in receipt is for guarantees, support and repairs. No more digging around for a piece of paper when your computers fail, no more search for cryptic reference numbers (most people have a printer at home, not a HP Laserjet P2015-G). This becomes even more important for companies that aim at sustainable product management such as Patagonia: Patagonia Asks Its Customers To Buy Less.

“We realized that what was really needed was a mutual responsibility between company and customer for the full lifecycle of stuff,” Rick Ridgeway, Patagonia’s environment VP. “So we would try to reduce the amount of stuff that people buy, fixing products if they were broken, and asking people to clean out their garages and closets, so that if you have clothes you are no longer using, you put them back into circulation.”

Receipts are also the best resource to create community of users around products. These communities already exist, in a relatively unstructured way, in forums, blog posts … a central point of reference per product would help structure this content, link it together or link to a platform maintained by the producer. Receipts could also be used in collaborative consumption to track the use of a product when it is reshared, recycled with others.

In VRM, intelligent receipts could play an important role, as it empowers customers with data that represent their relationship with a merchant. This information could be leverage by them to reverse their relationship with merchants.

Using this data is not new … some digital companies have been doing it for some time. Tripit is a good example. It mines data contained in flight / hotel receipts to create a travel plan or even share this information with others. In theory, it could also mine price data to determine if you are overpaying for your trip.

Interest in receipts is growing and several companies are trying to position themselves in this market. Onereceipt, Lemon, Slice are all trying to aggregate users receipts and transform them in usable data. Most focus on expenses management for users, but I am not sure this is the best angle to adress this market.

Hopefully these will be soon definitely something of the past.