Sumsub: Feat - Add Device Intelligence support#2224
Open
cmgustavo wants to merge 1 commit into
Open
Conversation
cmgustavo
force-pushed
the
feat/sumsub-device-intelligence-01
branch
from
July 10, 2026 19:36
fc89e5e to
eec0667
Compare
cmgustavo
marked this pull request as draft
July 13, 2026 20:00
cmgustavo
force-pushed
the
feat/sumsub-device-intelligence-01
branch
7 times, most recently
from
July 20, 2026 20:27
ecd4087 to
c7bcded
Compare
cmgustavo
marked this pull request as ready for review
July 20, 2026 20:34
cmgustavo
force-pushed
the
feat/sumsub-device-intelligence-01
branch
from
July 21, 2026 17:54
c7bcded to
a36266b
Compare
Collaborator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Wires up SumSub Device Intelligence to capture the device and report anti-fraud events for BitPay invoice flows and authentication.
Events reported
How it works
The device's unique id (getUniqueId) is sent to the backend as SumSub's sessionId; the backend mints the DI token (getDeviceAccessToken) and receives events (submitDeviceEvent), keeping the SumSub secret key server-side.
Authenticated calls go through the signed RPC; logged-out ones use the public variant. fisherman is init()ed once and re-pointed with updateAccessToken() on later events, since DI tokens are single-use and re-initializing degrades the SDK in RN.
Verified end-to-end on testnet (Android): logged-in events attach to the applicant (skipped:false); anonymous ones return skipped:true (no applicant), as expected.
Note: visitorId is empty until SumSub disables sandbox simulation and provisions a real FingerprintJS key.