Verify the service verification config on production

[sameh-farouk]

"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

[xmonader]

@sabrinasadik what do you suggest here?

[sabrinasadik]

Situation 1: suspicious doc - redo kyc with different identification document
Situation 2: expired doc - redo kyc with valid id