Case Keeper v1.4 Release Notes

In this release, we have included the following improvements:

KYC module

Front ID card verification process improvements

Added configuration options for fake front ID card validations

We've added configuration options in the frontIdCardConfig to validate fake ID cards.

To enable fake ID validations, you can add the validations array field in frontIdCardConfig and specify the validation keys as below.

As per the current release, only fake ID card validations can be configured. All other validations will always be run, such as comparison, expired, etc.

It is recommended to also specify validations that are not related to the fake ID card in this array for already planned future updates.

// current available validations for frontIdCardConfig
"validations": ["hologram", "idCardFont", "hologram", "recapture", "redLine"]

// recommended, remove the validations you do not want to validate
"validations": ["comparison", "expired", "idCardFont", "hologram", "microprint", "mugshot", "recapture", "redLine", "restrictedAge"]

Updated fake front ID card detection result

We have enhanced our fake front ID card detection mechanisms to yield better results.

As per the result, The font detection now returns a boolean response instead of the previous version where the response was a number. Further, we also return a list of keys that were found to have an incorrect font.

The following new fields are added to the frontIdCardResult.response.result object:

authentic_liveness: Verification of whether the ID card photo is taken from the actual card or from other sources such as a computer or smartphone screen. true: It's the actual card. false: It's taken from other sources such as a computer or smartphone screen
authentic_card: The system presents the final result, indicating whether each feature has passed the verification process and confirms the authenticity of the ID card. true: It's the actual card. false: It's possible that the input doesn't contain the authenticated card

microprint detection has been removed for improvements.

Previous Version

"frontIdCardResult": {
  "response": {
   ...
   "result": {
    ...
    "thailand_id_authentication": {
        "result": {
          "non_microprint": 91.17647058823529,
          "non_thai_card_font": 0,
          "recapture": 0,
          "non_hologram": 100
        }
      },
    },
  },
}

New Version

"frontIdCardResult": {
  "response": {
   ...
   "result": {
    ...
    "thailand_id_authentication": {
        "result": {
            "authentic_details": {
                "authentic_liveness": true,
                "authentic_fonts": {
                    "authentic_fonts_result": true,
                    "authentic_fake_keys": []
                }
            },
            "authentic_card": true
        }
     },
   },
  },
}

Added a new Face Comparison result in the Dip Chip process

Initially in the DipChip process, we store 2 face-comparison results with the similarity percentages.

verification.dipChipResult.response
verification.dipChipResult.idCardResponse

In this release, a new face comparison result has been added to the dipChip process. It's the comparison result between "the Customer's face taken by the Rider while doing Dip Chip" and "Card owner's facial information from card reader"

The new comparison result will be stored in verification.dipChipResult.faceComparison.

{
  "dipChipResult": {                  
    "faceComparison": {
      "$metadata": { ... },
      "FaceMatches": [
        {
          "Face": { ... },
          "Similarity": 99.22173309326172
        }
      ],
      "UnmatchedFaces": [],
      "SourceImageFace": { ... }
    },
    ...
  }
}