SumSub: Enhancement - Prefill KYC applicant with the account email / phone - #2319
Open
cmgustavo wants to merge 1 commit into
Open
SumSub: Enhancement - Prefill KYC applicant with the account email / phone#2319cmgustavo wants to merge 1 commit into
cmgustavo wants to merge 1 commit into
Conversation
cmgustavo
force-pushed
the
feat/sumsub-applicant-conf-rn2904
branch
from
August 26, 2026 20:19
b4be648 to
33d4aa7
Compare
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
1 participant
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.
launchSumSubSdknow seeds the SumSub applicant with the authenticated BitPay account's email and phone, so the KYC flow no longer starts from blank, user-typed values.We were passing nothing to the SDK but the access token, locale and theme. Email and phone are the only applicant fields the SumSub RN SDK accepts, and we already have both on the account — there is no reason to make the user retype them, or to let the applicant record carry contact data that does not match the account it belongs to.
This came out of the RN-2904 investigation (country picker vs. uploaded document country). That bug is not fixable in this repo — the SDK exposes no
fixedInfoor applicant country field — so the fix goes to the SumSub Dashboard's Verification Level.