Neustar Modernizes Telecom Billing Behind a REST API

The Challenge

Every phone call, fax, and computer connection in North America depended on infrastructure Neustar ran. The company had rescued the ten-digit telephone numbering plan with a solution the FCC mandated, and every telephone company on the continent held a physical interface into Neustar’s directory system. Carriers treated that directory the way banks treat a settlement ledger. Neustar had earned the right to be boring.

Neustar’s ambitions had moved past the directory by then. The company sold cloud services to enterprises and stood up a group called NexGen to expand that portfolio across new technologies and platforms. Billing stood in the way. Every cloud offering Neustar wanted to launch had to meter usage and charge for it, and the company’s billing capability predated the portfolio it now had to serve.

Billing also tolerates less error than most software. A wrong charge lands on a carrier’s accounts payable desk and turns into a dispute. A missed charge never comes back as revenue. Neustar needed an interface that teams across the company could call over plain HTTP, and it needed the existing billing behavior to survive the move intact.

Vidya’s Approach

Vidya joined the NexGen group as part of a team of senior engineers and rebuilt billing as a service any product could call over plain web requests. The team packaged that service so it shipped as a single self-contained unit rather than something an operator had to install into shared server software. Neustar’s operators gained a release path with one moving part and one fewer class of failures on the way to production.

Neustar’s product teams would depend on whatever design shipped for years, so Vidya weighed every decision with that in mind. The team designed the service so a client could safely retry a failed request without charging anyone twice, which matters most on the day a network hiccups in the middle of a transaction. Money got the same scrutiny. Halfway through the engagement, Vidya published Zero Tolerance on a subtle way that routine money math in Java quietly returns the wrong answer. A billing service cannot ship a bug that charges the wrong amount. That same discipline still anchors Vidya’s software architecture practice.

Vidya also chose the deployment approach Neustar’s staff already ran every day rather than a container technology that had only just shipped its first stable release. A revenue-bearing service is the wrong place to prove out an immature runtime. Every code change then ran through an automated build and test, and a broken build surfaced within minutes of the change that caused it, so Neustar’s engineers kept their attention on billing rules while the release mechanics ran themselves.

Neustar’s own engineers owned the number directory and the carrier interfaces into it, and Vidya’s team never touched them. Vidya’s scope stayed inside the NexGen group’s cloud portfolio. That boundary is worth naming, because a national number portability directory and a billing API are different engineering problems with different consequences when they fail.

What Changed

Neustar’s product teams reached billing with a plain web request from any language and any platform in the cloud portfolio, which meant a new offering could meter and charge for usage without standing up a billing project of its own. The engagement ran about three years, long enough for Vidya to carry the API past its first release and into the unglamorous work of keeping a revenue-bearing service healthy on Amazon EC2. Neustar got a billing capability its roadmap could depend on.

The sequence still holds for any team modernizing a system other groups depend on. Vidya makes the old capability callable behind a clear, stable interface the consuming teams can build against, then keeps each piece small enough for one team to own end to end. The legacy implementation moves behind that contract on a schedule the business picks. Organizations running a revenue system they are afraid to change can start that sequence inside a single quarter, and Vidya runs it today across commercial platforms and federal legacy system modernization programs alike.