Once a user has successfully created his subscription, the service provider will typically use a cookie in his browser to identify him as a returning user to the content or service portal. Many also provide credentials (username and/or password) in case the session expires, the user has a new phone, or the cookie gets otherwise lost.
If all this goes wrong, service providers can use the User Identification API and corresponding flow to identify an unknown user. The flow will recognize the user automatically if he's using his mobile network internet connection or ask him to enter his MSISDN after which he will receive a SMS with a link to click.
The flow between the user, the service provider, Mpulse and the mobile operator is described in the sequence diagram below.
