[Tech]: Reworking KYC Status Handling

[Tieumsan]

Problem

Various issues exist in the current management of different KYC statuses.

Solution

Implement the correct handling procedures.

Requirements and Sub-tasks

Backend

• [x] https://github.com/soramitsu/sora-card-backend/issues/295

Client Applications

The KYC workflow should be adjusted according to this diagram.

Web

• Design
  • [x] https://github.com/sora-xor/sora-card/issues/101
• Development
  • [x] https://github.com/sora-xor/sora-card-web/issues/34

Mobile

• Design
  • [x] https://github.com/sora-xor/sora-card/issues/102
• Development
  • [x] https://github.com/sora-xor/sora-card-ios/issues/87
  • [x] https://github.com/sora-xor/sora-card-android/issues/133

[bgodlin]

Blocked by https://github.com/sora-xor/sora-card/issues/96

[2bogd]

Example of implementation (web):

[Alexey-N-Chernyshov]

Example of iOS implementation:

var userStatus: SCKYCUserStatus {
    // do not use kycStatus, it may be any state:
    // kycStatus == .Successful or kycStatus == completed or kycStatus == failed
    if verificationStatus == .accepted {
        // KYC verification completed, waiting for IBAN
        return .successful
    }

    if kycStatus == .Completed {
        // KYC docs were sent, waiting for KYC verification
        return .pending
    }

    if kycStatus == .Retry {
        // retry
        return .rejected
    }

    if kycStatus == .Started {
        // KYC wasn't completed, reuse reference_number from KYC
        return .userCanceled
    }

    if kycStatus == .Failed {
        // KYC wasn't completed, reuse reference_number from KYC
        return .userCanceled
    }

    if kycStatus == .Rejected {
        // KYC was rejected, start a new one with a new reference_number
        return .rejected
    }
}