New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Verify the service verification config on production #23

Open

sameh-farouk opened this issue Nov 13, 2024 · 0 comments

Assignees

Member

sameh-farouk commented Nov 13, 2024 •

edited by xmonader

Loading

"Verification": {
      "SuspiciousVerificationOutcome": "APPROVED",
      "ExpiredDocumentOutcome": "APPROVED", # this related to when a doc expires, do a user needs to re-do KYC, or our service can consider him a verified user as before

All networks are running with this verification config (it's configurable using env vars).

We need to verify that this is the intended behavior for KYC on production.

When idenfy flags someone with valid docs as suspicious which is one of their verification result, should we treat them as approved or not?
And when someone's documents are expired, right now we still treat them as approved

The text was updated successfully, but these errors were encountered:

sameh-farouk assigned sameh-farouk and xmonader and unassigned sameh-farouk

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment