Your browser is not supported. Please update it.

7 March 2013

APIs for billing and identity highlight the real cellco weapons

The key, they know, is to leverage advantages that are entirely reliant on their networks, and which can enable new services and attract developers. The most obvious is carrier billing, which is proven to drive usage and loyalty and ‘ unlike some other much-cited examples, like network-based location ‘ cannot easily be replicated by over-the-top players (though PayPal and Amazon have a good shot at strong alternatives). According to new calculations by Juniper Research, content paid for via direct operator billing will generate $13bn in revenue by 2017, up from $2.3bn last year.

Carrier billing offers all kinds of lessons to operators, most importantly that they do not need to be content providers. Having tried and failed many times to build their own portals and web experiences (remember Vodafone Live?), the wisest cellcos ‘ at least outside Asia, where there has been more acceptance of carrier web platforms – know that their real power lies in ensuring that transactions made in others’ storefronts go through their billing system, keeping the user tied in and generating revenue share. “While many operators have now abandoned the own-brand storefront approach, by leveraging their billing relationship with the end user they can retain a foothold in the content play,” said Windsor Holden, research director at Juniper.

More generally, this shows that WAC (Wholesale Application Community) was not entirely wrongheaded, although its structure and approach proved largely unworkable. It sought to create a common developer platform spanning the world’s main cellcos, and leveraging the advantages inherent in their networks, but was folded last fall. However, it did succeed in sharpening focus on the move for operators to open their network APIs (application programming interfaces) to partners.

Indeed, the WAC effort was folded into the GSM Association’s own effort in this area, OneAPI, (and its actual technology was acquired by Apigee, a specialist in systems to publish and manage APIs). Following up on its promises to continue to evolve a cross-platform mobile development platform, as envisaged by WAC when it was established in February 2010, OpenAPI was reporting progress at this year’s MWC. The GSMA unveiled OpenAPI Exchange, the latest element in the program to open up carrier APIs in a harmonized way, so that developers can use them in applications which then work on any participating network.

The new Exchange ‘ enabled by the Apigee platform – aims to make it easier for developers to integrate network-based features with their applications. Announced by Marcus Dormanns, senior director at the GSMA, the platform allows programmers to add these features to apps that run on Android, BlackBerry, iOS and Windows Phone as well as browser-based offerings. Developers can subscribe to an operator network API and then choose additional cellcos they would like their app to support. All billing, metrics and usage data are then processed through a single point, eliminating the need to sign a deal individually with each carrier.

Functionality will be added in phases, said Dormanns, starting with a standardized identity API, which allows users to register with applications without the need to share their identity and passwords with third parties. This will become available via the Exchange during the second quarter while a payment API will also go live this year, covering perhaps the operators’ greatest weapon against OTT, their bill. AT&T, Deutsche Telekom, Orange, Telefonica and Vodafone have all helped develop the platform.

This first step is highly significant because it turns the carriers into identity managers. Like the bill, identity and login credentials are a key point of power in the mobile web and apps chain. This Exchange API will not only run universally across all the cellcos’ networks, but will allow the operators to insert themselves into the apps value chain at this important point. They hope customers will start using their cellphone numbers, rather than their Facebook ID, as their universal log-in to many web services. That means offering an API for any app developer to use to authenticate users against a carrier’s subscriber identity data. So far AT&T, Orange, Deutsche Telekom, Telefonica and Vodafone have signed up.