Integrate auto-launching the app

  • Updated on Feb 23, 2026
  • Published on Feb 23, 2026
  • 1 minute(s) read
Prev Next

Users can launch the Mobile Authenticator Studio app and execute a defined action by clicking on a URL with the following format:

${scheme}://${actionName}

where:

  • ${scheme} is a string specified when customizing the Mobile Authenticator Studio app, according to iOS and Android scheme policies.

  • ${actionName} can be one of the following:

    • onlineactivationid

    • offlineactivationid (standard licensing)

    • actionid

The action name can be followed by the action parameters in the following format:

$scheme://${actionName}?
ActionParameterName1=ActionParameterName1Value&ActionParameterName2=ActionParameterName2Value

Action and parameter names are case-insensitive.

If the URL format is incorrect, the app will display an error message and terminate. Unknown parameters are silently ignored.

Online activation

When the digipass://MyOnlineActivationId URL is clicked, it launches the online activation with the MyOnlineActivationId identifier. This action supports the following parameters:

  • Identifier. This is the registration identifier. It is an alphanumeric string, limited to 40 characters.

  • ActivationPassword. This is the authenticator activation password. It is an alphanumeric string, limited to 40 characters.

All parameters are optional.

Offline activation (standard license activation)

When the ${scheme}://offlineactivationid URL is clicked, it launches the offline activation for the Mobile Authenticator Studio app. This action supports the following parameters:

  • SerialNumber. This is the authenticator serial number. It is composed of 3 letters and 7 digits.

    Do not use a serial number suffix (e.g. “1280189”) instead of the full serial number (e.g. “FDM1280189”) in the activation URL. The serial number prefix will be retrieved from the static vector. Thus, the serial number prefix can differ from the static vector that is hardcoded in the mobile app (e.g. “FDL”) and the authenticator BLOB used by the server (e.g. “FDM”). In this case, the authenticator instance will be properly activated, but the generated authenticator responses (i.e. one-time password and signature) will be invalid.

  • ActivationCode. This is the authenticator activation code. It is a hexadecimal character string.

  • ERC. This is the authenticator event reactivation counter. This value can be modified once it is displayed for validation.

All parameters are optional.