Skip to the content
IPification - Mobile authentication solutions
Menu
Menu
Have a Question?
Search
11. Dual SIM Devices
01. *Dual SIM scenarios: As we have come to know about this issue during our discussion with Sabay. I have been talking to Milan on the same & have some idea of the issue, but it would be great to have a download from the product team so that the BD team is aware of this issue. we could look at the following scenarios in dual sim cases:
02. *The user has one SIM on mobile data & other SIM (both different telcos) not active on mobile data & he tries to register using the sim which is not on mobile data, punching the MSISDN active on mobile data & we are live with only one telco i.e. the one with active mobile data. as per my understanding, we will return a false verification to the SP & they would be charged for the same. Please clarify.
03. *The same use case mentioned above but both the SIMs are from the same telco with which we are live. So if a user is trying to register via the SIM, not on mobile data, we will send them a failed verification report, correct?
04. *What happens if the user has 2 SIMs of different telcos, both active on mobile data ( it would be very less %, but it still could be a case) & we are active with the telco with sim 1 but the user uses sim2 to punch in the number of sim 1. What happens in this scenario? we will again return false verification & charge the SP
05. *Milan is working out a solution for Sabay in Cambodia, where we would also share the details about the network along with the API call to Sabay & they then accordingly will redirect the user to the SMS/OTP option if the telco is not live with us, therefore, saving the authentication fee to IP. But this would only work till the time MNP is not implemented, correct? How do we tackle this issue in countries where MNP is implemented?
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?
07. *As Per Mike's input, there are quite a lot of users using dual SIM in Cambodia, therefore we have proposed the solution wherein we would share the network details along with the API call to enable Sabay to redirect the user to SMS/OTP so that they are not charged for false verification (which is what Mike wants that they are charged only for successful authentications). I wanted to know along with the network details via our coverage API, do we also share the status of mobile data i.e. whether the Sim used for registration is active on mobile data or not? If I recollect correctly, we will share the mobile data status as well, @Milan Radojkovic?
08. *The user has 2 SIMs, one with active data & one with only voice calling. We are live with the operator of the sim active with mobile data. While registration the end-user uses SIM no 2 i.e. sim with only voice to punch in the MSISDN of sim no 1 which is active with mobile data, in this case also the SP would be sent a false verification & charged for the same. Am I Correct?
You are here:
Main
11. Dual SIM Devices
Category - 11. Dual SIM Devices
Articles
01. *Dual SIM scenarios: As we have come to know about this issue during our discussion with Sabay. I have been talking to Milan on the same & have some idea of the issue, but it would be great to have a download from the product team so that the BD team is aware of this issue. we could look at the following scenarios in dual sim cases:
02. *The user has one SIM on mobile data & other SIM (both different telcos) not active on mobile data & he tries to register using the sim which is not on mobile data, punching the MSISDN active on mobile data & we are live with only one telco i.e. the one with active mobile data. as per my understanding, we will return a false verification to the SP & they would be charged for the same. Please clarify.
03. *The same use case mentioned above but both the SIMs are from the same telco with which we are live. So if a user is trying to register via the SIM, not on mobile data, we will send them a failed verification report, correct?
04. *What happens if the user has 2 SIMs of different telcos, both active on mobile data ( it would be very less %, but it still could be a case) & we are active with the telco with sim 1 but the user uses sim2 to punch in the number of sim 1. What happens in this scenario? we will again return false verification & charge the SP
05. *Milan is working out a solution for Sabay in Cambodia, where we would also share the details about the network along with the API call to Sabay & they then accordingly will redirect the user to the SMS/OTP option if the telco is not live with us, therefore, saving the authentication fee to IP. But this would only work till the time MNP is not implemented, correct? How do we tackle this issue in countries where MNP is implemented?
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?
07. *As Per Mike's input, there are quite a lot of users using dual SIM in Cambodia, therefore we have proposed the solution wherein we would share the network details along with the API call to enable Sabay to redirect the user to SMS/OTP so that they are not charged for false verification (which is what Mike wants that they are charged only for successful authentications). I wanted to know along with the network details via our coverage API, do we also share the status of mobile data i.e. whether the Sim used for registration is active on mobile data or not? If I recollect correctly, we will share the mobile data status as well, @Milan Radojkovic?
08. *The user has 2 SIMs, one with active data & one with only voice calling. We are live with the operator of the sim active with mobile data. While registration the end-user uses SIM no 2 i.e. sim with only voice to punch in the MSISDN of sim no 1 which is active with mobile data, in this case also the SP would be sent a false verification & charged for the same. Am I Correct?
IPification - Mobile authentication solutionsIPification - Mobile authentication solutions