No. The authentication is SIM-based, not network-based. It works over any internet connection including WiFi. The solution verifies through the physical SIM (or eSIM) on the device, so as long as the device has a SIM card and some form of internet connectivity, the flow will work.

On Android (TS.43), the Digital Credentials consent prompt lets the user choose which SIM to use for verification. On iOS, authentication works for both active SIMs on dual-SIM devices.

eSIM works the same as physical SIM for authentication. The carrier authenticates the eSIM profile identically.

The backend returns a carrier eligibility error. Implement a fallback authentication method (e.g., SMS OTP) for unsupported carriers. You can also check eligibility upfront before starting the flow.

Sessions have a timeout window. If exceeded, the session expires and the SDK returns a session error. Show a timeout message and offer to start over.

The backend returns a verification failure indicating the SIM phone number doesn't match the number provided. Show a clear message and let the user correct the number or switch to the Get Phone Number flow.

Since the authentication is SIM-based and works over any internet connection, roaming does not affect the flow. The SIM is verified regardless of which network the device is connected to.

The verification continues in the background. Results are delivered when the app returns to foreground. Make sure your state management handles delayed responses gracefully.

The mobile verification page or carrier flow will fail with an eligibility error. If using a mobile verification page, you can detect this early and show a message asking the user to use a supported device.

The SDK handles reconnection and resumes polling when connectivity returns. If the session has already expired by then, start a new flow.