Handling Journey Auto Blocking in WebSDK

Overview

Journey Auto-Blocking is a security feature in IDWise that stops the onboarding process when one or more high-risk conditions are detected. This helps prevent suspicious or non-compliant sessions from proceeding further.

For example, when Device Intelligence is enabled, the SDK evaluates smart signals such as rooted devices, emulators, or VPN usage. If any configured condition is not met, the journey is automatically blocked, and the user is shown a clear error message.

📘

Info

Minimum SDK Version that supports this feature is 5.4.0

Implementation

If you're using the Standard SDK, IDWise automatically:

• Evaluates all preconditions on start of the journey.
• Notifies the user if the device is blocked.
• Displays an in-app error screen explaining the issue.

Example: Rooted Device Error Screen

Optional Callbacks for Journey Blocked

In addition to the built-in error screen, you can listen for the onJourneyBlocked callback to take additional action in your app logic.

Callback Behavior

• Triggered when a journey is blocked
• onJourneyCancelled will not be triggered in this case
• Useful for analytics, user notifications, or custom UX

You can subscribe to this callback to be notified if the user faced a block and can no longer proceed further:

<script>
  let global_idwise;

  function onJourneyBlocked(journeyBlockedDetails) {
    console.log("IDWiseSDKCallback journeyId:", journeyBlockedDetails.journeyId);
    console.log("IDWiseSDKCallback blockedTransaction:", journeyBlockedDetails.blockedTransaction);
    // IDWise SDK already informed the user of the block reason
    // Optionally you can add extra logic here to do extra handling if you need
  }
  //...
  
  const eventHandlers = {
    //...
    onJourneyBlocked: onJourneyBlocked,
    //...
  };

  function resume() {
    global_idwise.resumeJourney({
      flowId: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
      mount: "#idwise-mount",
      journeyId: "xxxxxxxxxxxxxxxx",
      eventHandlers,
    });
  }

  function start() {
    global_idwise.startJourney({
      flowId: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
      mount: "#idwise-mount",
      referenceNo: "xxx",
      eventHandlers,
    });
  }

  IDWise.initialize({
    clientKey: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
    locale: "en",
  })
    .then(idwise => {
      global_idwise = idwise;
      // if this is the first time the user tries to do verification
      start();
      // or the user already started a verification session and interrupted it before finishing. We can resume it.
      resume();
    })
    .catch(error => {
      alert(error);
    });
</script>

Data Structures

JourneyBlockedInfo

BlockedTransaction

BlockReason

Block Reason Codes

📘

Note

Only the pre-conditions you enable on your Device Intelligence block in your flow will be checked. Any conditions that are turned off will not be checked.