Version 3.7
What's new
- Recommended Outcome: you can now use a single response parameter to easily interpret the document verification result and get outputs like "Accept", Reject", Manual Review", "Retry" and "Undeterminable"
- Use-case definition: going hand-in-hand with the Recommended Outcome, these new request parameters allow you to use just a few simple settings to define the product behavior (verification strategy, sensitivity etc) without touching all the match levels. The match levels are still available for more advance configuration
- Handling the fully cropped images. Fully cropped images often can not be verified and should not be accepted. This case is now handled as a processing status + a detailed message
- Photocopy change of behaviour: failure in the photocopy check will result in a failure within the verification object as well, making the logic simpler and easier to interpret
- We are introducing optionsUsed field in the response which lets you easily in one place see all the set options (all configuration) to make your iterations and analytics easier to implement
- We added the traceId field which binds the unique ID to each transaction, making the debugging easier
- Data formats coverage for US and Caribbean documents is increased
API changes
- Added the following optional fields to the request:
useCase
Other changes
- Increased the recommended resources for deployment in order to prevent the out of memory problem that can happen with the model serving service
Added the following fields to the response
useCaseUsedoptionsUsedrecommendedOutcomeinsideVerificationobjecttraceIdFullyCroppedDocumentvalue added to theProcessingStatusfield