Have a Question?
06. *For offering SIM swap API solutions to our clients, we first need to implement the same with the respective telco, right? Once we have the Sim swap API deployed with a particular telco, then do we get to know about the sim swap in real-time as and when it happens?
Of course, we need to have solutions implemented on the telecom side in order to offer to the client :). Our current SIM Swap API solution we are deploying with China Mobile HK for example, or with Swisscom, is one of the several options Telecoms are exposing (I think we went through this before, I am copying it again):
| Output | Notes/Implications |
| 1) SIM Change Timestamp | This is the easiest out of them all. By getting the exact change timestamp, SP can do the calculations on our side. |
| 2) SIM Change Buckets (e.g. < 1 day, < 2 days, < 7 days, < 14 days, < 30 days, >= 30 days) | These are examples of change buckets. If you have other breakpoints in mind, then we can probably work with that. |
| 3) SIM Change Challenge | We provide a MSISDN and timestamp to you, and you return a Y/N whether there has been a change since the timestamp. |
| 4) SIM Token | Doesn’t matter what the token is, as long as it is persistent (it can’t change randomly). |
Usually, Telecoms will expose and allow us to use 2) or 3) models. With Swisscom for example we have the number 1) exact SIM Change Timestamp API to call – when we send them MSISDN they return the exact Date/Timestamp when the SIM card has been last activated/swapped.
