03. Is IPification Mobile Connect compliant?

Since November of 2018, IPification is Mobile Connect compliant. Any Service Provider/Merchant that has Mobile Connect protocol integrated can use IPification authentication as well. In addition, IPification also exposes Open ID Connect protocol to SPs as well in case they do not have MC protocol integrated/used before. 

We are working closely with the GSMA team in London, to extend the coverage of IPification to as many operators as possible globally. Some top IT companies have growing interests in using such service for seamless and secure authentication. At the moment, Mobile Connect gateways, which only provides one of the following Authenticators, encounter big challenges on the security, UX or distribution: 

– Header Enrichment (only works on HTTP!)

– USSD (requires user opt-in for the channel)

– SMS with embedded URL (SS7 vulnerability and bad UX)

– Sim Applet (very hard for distribution and large user adoption)

Mobile Apps which are failing short either on user experience or security. That’s why almost all Mobile Connect deployments so far, couldn’t manage to get commercialized and open up new revenue streams for Operators. We are changing this with IPification.

IPification is set to be an additional and potentially the best method (in terms of UX, privacy & security) for user authentication, as long as the user is on Cellular Data’s network (2G, 3G, 4G etc.)

IPification can be also as a standalone API business of Telecom, independent of Mobile

Connect, but if you already have MC deployed, we can add it easily as one of the

authentication layers which can be heavily monetized.MC Link (Channel partner of Mobile Connect and GSMA) is one of the first merchants/aggregators to buy IPification auth, as soon as it is available with any Telecom. They are already aligned with a dozen global merchants who are ready to use it.