Billing Platforms are Not that Big an Issue, Really

Some retail connectivity provider issues never seem to go away. The old adage that “you cannot sell what you cannot bill for” is correct, as far as that goes. But it also is true that an entity cannot bill for what it does not own or control. 

And that seems the more fundamental problem. Some of you might recall the hope about using telco billing systems to support business partners offering microservices, in the older sense of products costing very little, not the current usage of the architecture upon which modern applications are built. 

Use of telco billing platforms to support third-party applications basically has remained unfulfilled. Part of the issue is that the whole architecture of how apps and services are accessed using the internet has changed the dynamics.

Since app providers do not need an access provider’s permission to conduct business with users and customers, there is scant--if any--value to using a telco billing platform. Usage--as such--tends not to drive monetization models. 

Subscription charges are easily supported using other payment and billing systems. Ad-supported models use a variety of engagement metrics. Commerce models likewise use other established retail payment systems. 

source: STL Partners 

Even if a connectivity provider owns its own industrial automation, gaming, water or electrical utilities, unmanned aerial vehicle systems, operates retail fleet management services provided to third parties or owns monitoring platforms for any range of business operations, the connectivity billing platform is simply not set up to support those types of operations. 

Were a connectivity provider the owner of such assets, such a provider would use the industry-standard and existing rating mechanisms. 

And where a connectivity provider partners with a firm that does offer such services, the necessary rating platforms would be those used by the third parties. There is scarce--if any--need for using the telco rating systems. 

The obvious areas where connectivity providers require new capabilities are for new connectivity services such as network slicing, which might have to support “on-demand” usage capabilities. But that has almost nothing to do with supporting third party applications. 

It seems marketing staffs never are happy with legacy connectivity billing systems. But aside from new connectivity-specific services, there still appears little practical value for new rating systems that support the third-party transactions and products that will use connectivity networks. 

Loosely-coupled architectures have largely made that unnecessary.