#churcho-verifications-ip

1 messages · Page 1 of 1 (latest)

cold olive
#

Hey! We don't expose the IP address from Verification Session via the API, no

waxen sphinx
#

I thought about that but it looks to me like metadata would be set before the actual verification runs. So if a user opts to complete verification on another device you still infer the 'old' IP address and not the one where the actual verification is run. Hence my issue.

cold olive
#

I thought about that but it looks to me like metadata would be set before the actual verification runs.
You'd set it on the creation of the session, yes

#

I guess your use case isn't really a fit for the product. It's intended to verifiy the identity of an individual, not necessarily their location

waxen sphinx
#

This issue actually arose from the fact that the verification modal allows the user to verify on another device so you can have a user send that verification to be performed by someone else.

What I am trying to do is ensure that the person who is using the app is the same one verified but having an option to resent to a different medium effectively means using the app can be done by someone else and then they have the verification completed 'offsite'

cold olive
#

This issue actually arose from the fact that the verification modal allows the user to verify on another device so you can have a user send that verification to be performed by someone else.
Right, but our concern is only to verifiy the identity of the person who completes the session. Regardless of who initiated the initial session

#

What if they complete the verification session on a different network, but it's the same person?

#

Their IP will be different – should it fail?

waxen sphinx
#

The issue is not fail | pass, it's just a recording of where an activity was handled from.

I think the focus is: VERIFICATION
Does it do that? Yes

Now I need to figure out how to solve this business problem.
Thanks.