DeviceSwap
Introduction
Lifecycle Status | INCUBATING |
|---|---|
API Category | Authentication and Fraud Prevention |
Sub Project | Number Insights |
Primary Contacts |
|
Maintainers | https://github.com/camaraproject/DeviceSwap/graphs/contributors |
Latest Release | |
Mailing List |
|
As Device swap joined Number Insights sub project in May 2025 previous meeting minutes could be find here: | |
| |
Comments
The scenario where the SIM card changes but the physical device remains the same should not be considered a Device Swap.
The Device Swap API monitors changes in the MSISDN–IMEI association, i.e. whether the phone number becomes associated with a different physical device. A SIM replacement that keeps the same MSISDN and the same IMEI changes the SIM/IMSI association, but not the MSISDN–IMEI association. Therefore, this scenario falls under the scope of SIM Swap, not Device Swap.
If both the SIM and the physical device change, then both events may be relevant: SIM Swap would detect the MSISDN–SIM change, while Device Swap would detect the MSISDN–device change. In short, Device Swap is triggered by a change of device, not simply by a change of SIM.
Thanks @Alberto Ramos Monaga for the clarification.
@All Query related to scope of DeviceSwap API. The API specification suggests the scope of this API is to check if SIM card associated with a user's phone number has been transferred to a different physical device. If that is the case then should we also include a scenario where customer is changing the SIM but the device remains the same. This may classify under SIM Swap but from DeviceSwap perspective, should the scenario be included because at the end the mapping of Device-User’s phone number / SIM is changing. Please clarify.