SIM swap fraud works by taking control of a victim’s phone number and intercepting the codes sent to it. Which? has warned that unauthorised SIM swaps are rising, and it links the trend to widespread reliance on text-message one-time passwords. Once a fraudster controls the number, the codes follow.
The underlying issue is that SMS treats possession of a number as proof of identity. A delivered code shows only that a message reached a phone. It cannot show who holds the phone or whether the SIM was recently changed. Fraudsters exploit that gap through social engineering of carrier staff and through requests for SIM changes.
Network APIs approach the problem from the other side. Instead of asking whether a code arrived, they ask the operator. TelecomLead reports that the GSMA’s Open Gateway commercialisation update counts 64 commercial Number Verification deployments by March 2026, second only to SIM Swap among network APIs. Operators are now treating verification as a product.
NV1: Proving the Connection
NV1 confirms that the mobile data session belongs to the number. Nothing needs to be installed, and no SDK or SIM permission is required. It works in any app or web page on mobile data.
The network link can be RADIUS accounting from the operator’s packet gateway, SS7 MAP, or Diameter Sh. RADIUS suits operators that already produce accounting records. The platform processes only the subscriber, IP, APN, and session attributes it needs.
NV1 suits web sign-up, login, account recovery, and mobile-web checkout. Because the proof comes from the mobile connection, it requires mobile data rather than Wi-Fi.
NV2: Proving the SIM
NV2 confirms that the genuine SIM is in the device. It runs inside an app, through the phone’s built-in capability or the PAiCore SDK, and works on mobile data or Wi-Fi.
The network link is SS7 MAP or Diameter, using the STa and Sh interfaces. NV2 suits in-app sign-in, wallet and banking flows, and step-up checks where the user may be on Wi-Fi.
Matching the Method to the Journey
A browser journey on mobile data points to NV1. An app journey on Wi-Fi points to NV2. The strongest designs treat silent verification as one signal among several: a fresh check before a payment, a flag for a recent SIM change before a password reset, and SMS OTP as a fallback where silent methods do not apply.
Signalling APIs Beneath the Verification Layer
Both methods depend on signalling interfaces that operators already run. The same layer supports signalling APIs for authorised partners, which expose defined network operations such as session lookup. These are operation-level interfaces, not raw SS7 traffic, and they sit alongside the verification APIs rather than replacing them.
The Network API Gateway offers NV1 and NV2 among its eight CAMARA-aligned APIs. Explore the product at paicore.tech/platforms/network-api/network-api-gw, and find the source code at github.com/paicoretech/network-api-gateway.




