Direct to Mobile Billing – More than just an API
by gillian on 06.05.2011The continuing growth in popularity of in-application billing was not unexpected and is the obvious revenue model for developers in the face of declining application prices driven by ever-growing competition among developers offering applications through the popular app stores. With revenues from the four major app stores forecasted to grow by 77.7% in 2011 to reach $3.8 billion and $8.3 billion in 2014, and with in-application billing expected to be a key driver of that growth (see http://cnet.co/k1Wr1N), the market opportunity for Service Providers offering a facility for in-application payments is clearly significant.
However, the emergence of this new model is also causing concern among both consumers and the App Store providers that developers will exploit the facility to maximize revenue through hidden or “less than explicit” charging resulting in large, unexpected bills to the consumer and headaches for the app store providers. In many ways this can be compared to the tarnished reputation around premium SMS several years ago as a result of similar behavior, and several recent high profile legal actions related to In-Application billing (see http://bit.ly/fTNztW for an example) serve to highlight this.
In-application billing now accounts for up to 50% of the revenues for many popular mobile applications and games, and many analysts believe that this proportion is set to increase significantly as the “Freemium” business model for the sale of applications increasingly becomes the dominant model. However, as we’ve seen from recent legal actions, in-application billing brings with it certain operational challenges that Service Providers need to address up-front, before choosing and implementing a direct-to-mobile billing platform.
One of these challenges is associated with the fact that once downloaded, many applications run on the handset independently (i.e. there is no interaction with an application provider’s server), therefore the in-app billing request passes directly from the handset application to the Service Provider’s Payment API. This introduces the need for security mechanisms that ensure that the application is both authenticated and authorized to carry out the payment request on behalf of the user. In addition, the In-Application billing facilities should support charging in a non-intrusive, yet secure, manner to provide maximum flexibility for the widest range of usage scenarios. Aepona has been working closely with industry bodies such as WAC (Wholesale Applications Community) to define a solution for this security mechanism, and our proposal based on the OAUTH standards (being developed by the Internet Engineering Task Force, IETF), has been accepted by WAC as the preferred approach.
However, the operational challenges for Service Providers presented by in-application billing go beyond security issues. As recent legal action shows, even if an application has been correctly authenticated and authorized, there is still the potential for users to run up large bills for in-application goods or services, without the bill payer’s consent. In one extreme case, a child playing a popular mobile game was reported to have spent over $1,400 on virtual goods.
To address these challenges, Service Providers must ensure that their Direct-to-Mobile Billing platform includes the essential capabilities required for a commercial service. In many instances, Service Providers provide a Payment API without the operational features that are needed – they focus on the set of parameters supported by the API and spend little time thinking about how to commercialize their service offering.
A successful Direct-to-Mobile billing service needs to balance the consumer protection with the benefits of convenience that in-app billing offers to both application providers and end users. It has been clearly demonstrated that such a low-friction billing mechanism greatly improves sales conversation rates for applications, so it’s vitally important that Service Providers optimize both the consumer and developer user experience to ensure success.
Aepona is focused on helping Service Providers to get this balance right. The advanced Payments and Settlement component of our Universal Service Platform has been designed from the outset as a full commercial solution for direct-to-mobile billing, and in-application billing in particular. This includes features such as control of spending limits, parent-child hierarchies, fraud management, monitoring, subscription management, repudiation management and customer self-service.
The challenge in implementing a successful Direct-to-Mobile billing service, including In-Application billing, is not simply in the design or exposure of a payment API. As recent legal cases have shown, offering a commercial Payment Service involves so much more than this. Service Providers need to ensure they can enable users to control how, when and by whom they are charged, whilst maintaining the required level of simplicity and convenience.



