Would You Trust This Number? XConnect and Honey Badger Show the Trust Layer Live
A room full of industry experts would not trust a phone number, even once it was proven valid, active and able to receive a one-time password. Yet that is the basis on which much of the industry authenticates people every day. Mark Harvey and Matt Salisbury showed what a real trust decision looks like, live on stage.

Mark Harvey of XConnect and Matt Salisbury of Honey Badger HQ at CASA26, with a live demonstration of a risk decision built on network signals
Mark Harvey put a Dutch mobile number on the screen and asked the CASA26 room a simple question: would you trust it? No hands. He told them it was a valid number. Still no hands. He proved it was active on the network. Nothing. He showed it could receive a one-time password. A couple of hands went up, slowly, like bids at an auction.
The point landed. Much of the industry sends one-time passwords to thousands of people on exactly that basis, yet a room full of experts would not trust the number themselves. XConnect’s Chief Identity Officer has spent more than a decade in the API business, and his frustration is that the industry still asks whether there is real money in network APIs. There is, he said. It is happening.
Every number tells a story
XConnect does not stop at those first checks. It builds trust layers for enterprises: whether the number has been ported, behavioural context, network APIs, and other data such as whether a device has been reported stolen. Every number tells a story: its validity, its suitability, its tenure, how often and how recently it is used, whether it has been recycled or appeared in a breach. Tenure matters more than people think. Fraudsters sometimes get a number into an enterprise and leave it dormant for a year or two, no calls, no messages, waiting for the attack.
Of the network signals, SIM swap is the most used, in every country XConnect works in, with banks and financial institutions moving fastest. Call forwarding checks are catching up, starting with UK operators and now requested elsewhere. Know-your-customer checks are used heavily. And here Mark disagreed with the analysts: number verification offers a wonderful user experience, but it is technically complex to roll out and versions vary. His advice was to lower expectations.
From signals to a decision
Then Matt Salisbury, CEO of Honey Badger HQ, did what few people in the room had ever done: built a live risk playbook of the kind credit card companies, lenders and contact centres use in production.
First, enrichment checks running in parallel: SIM swap, call forwarding, and in some markets roaming, because organised fraud often involves phones bought in one country and used from another. Network data alone does not make a decision on a loan or a credit card, so the playbook adds open-source intelligence on the person’s digital footprint, a reverse lookup against a verified data set, and an identity check with a third party. All of it feeds a scorecard that weights each signal into low, medium or high risk, with a report for audit.
The most important part comes after. Smart teams feed real outcomes back: these applicants defaulted, those turned out to be fraud. The system then retrains the scorecard, with a human approving changes, because a wrong scorecard can turn away good customers or let bad ones through.
The live run
Matt ran the number from the start of the session through the playbook. The SIM had been swapped, but long ago, which is fine; what matters is a swap in the last day or two. No call forwarding, which fraudsters increasingly use instead of SIM swap because they know businesses check for it. Not roaming. A long-standing, legitimate-looking digital footprint.
Then the turn. The verified data set pointed to a different person than the open-source footprint suggested, with a different name and age. That pattern is typical of synthetic identity fraud, where real and fake information are mixed. The scorecard returned a medium risk: proceed with caution, perhaps ask for more information. Customers run decisions like this many times a second, all through APIs. Tag the outcome later, and the system suggests giving more weight to multiple identities next time.
Keep the API list away from enterprises
Mark closed with advice for the industry. Showing enterprises the full CAMARA API list is like taking a child into a sweet shop. They pick one that is not available, or one that only one operator in a market supports. XConnect keeps the list away from enterprises and talks about solutions instead. Like several speakers at CASA26, he does not much like the phrase network APIs either.
Nobody trusts a number because it exists. They trust it because the story behind it checks out. Our thanks to Mark and Matt for doing it live, and to XConnect, a CASA26 partner.
More from CASA26
CPaaSAA members have every CASA26 session in full in the member community.
Not a member yet? Find your fit in one minute and see which membership suits your company.
Following the series? New sessions appear here every week until Mobile World Congress. Subscribe on YouTube to catch each one.
CASA26 ran 21–23 September 2026 at the Tobacco Theater in Amsterdam, hosted by CPaaSAA. This is part of our Thursday series on Trust.
