Browser SDK Issues
Verisoul is undefined
Problem: The Verisoul script failed to load properly. Possible causes:- User is actively blocking Verisoul
- Slow network connection
- User is located in an OFAC or sanctioned country (Cuba, North Korea, etc.) that may be blocked by our CDN provider
- Retry loading the script tag
- If the issue persists, prevent the user from proceeding with the critical action
Unable to get session ID when calling Verisoul.session()
Problem: Cannot retrieve a Verisoul session ID. Context: Verisoul only returns a session ID after collecting the minimum information required to make a decision. This takes less than 500ms on most devices. The minimum payload only collects certain device/network attributes and sends that data to a globally deployed edge endpoint. Solution:- Retry the request
- If the session ID is still not returned after retrying, this may indicate that Verisoul is being blocked by a malicious user
- In this case, prevent the user from proceeding with the critical action
We are not aware of any ad blockers that would block Verisoul. If you are experiencing this issue, please reach out to us in the customer Slack channel.