Evrotrust Release Notes (Official Release v.24.7.0)

PRODUCTION RELEASE: May 7, 2025

Dear Evrotrust customers and partners, we’re happy to announce the release of Evrotrust v.24.7.0. Production release is planned for Apr 29, 2025, and is expected to start at 23:30 EET with approximately 3 hours of downtime. Details on the improvements and changes are below.

I. MOBILE APP

{IMPROVED}

Data attributes improvements for registrations with Romanian & Albanian ID documents:

Romania: Date of issue is now an obligatory field.
Albania: Place of birth is now an obligatory field.

Included support for Android v.15 and iOS v.18.

II. Web ID (SDK)

The new version of the documentation is available.

{NEW}
Liveness check and face match results

100% of the responses for /onetimeidentification/getdata now will return:

personPresence: shows the person’s presence and compares it to the photo from the document in %.

value liveness: Shows the liveness of the person:

0—The check has not been done
1—Unsuccess
2—Success

faceMatch: Compares the person to the photo from the document.

2—Success

0—The check has not been done

1—Unsuccess

{NEW}
Get a short video from the identification

A new parameter is added for /onetimeidentification/getdata – „secretVideo“

Set the parameter to true to get a short (up to 10s) video we take during the identification process.

{NEW}
Use Web SDK via WebView in iOS & Android

Added instructions on how to use the Web SDK via the WebView control for iOS & Android.

{NEW}
Control the document type support for the identification process

Start the Web SDK identification flow by adding the required document type (enc_data: user_document_type),and we will validate that the required document type is used during document scanning.

It can be either:

ID card
Passport

If there is no match, the user will see an error message on the screen, and new result code is returned: unsuccess_reason: 108 – Document Type not match with input.

{NEW}
Get a detailed status of the identification via a new API request

Check the detailed status for each identification to set better logic for the user’s next action: /onetimeidentification/status

Check whether:

Process is finished	processFinish
User has passed the face recognition step	isIdentified
User identification is reviewed	isSupervised
User has canceled the process	cancelProcess
User identification is rejected	isRejected
unsuccessReason	View code list

Example response:

{IMPROVED}
Returned selfie is now improved with better image quality.

{CHANGE} Address is now returned in separate fields (only for BG documents)

III. API

The new version of the API documentation is available here: 1.0.252

{NEW}
OTP eSign: Choose the SMS type via an API parameter

You can now choose the required SMS type for the integrated process via an API parameter: „smsType“, values: 1,2,3

Value	Type	SMS text
1	Code	For signing with QES e-signature with Partner X, use code {{code}}
2	Link	For signing with QES e-signature with Partner X, click: {{link}}
3	Both	For signing with QES e-signature with Partner X, use code {{code}} or click: {{link}}

Added to:

/document/doc/offline
/document/doc/offline/file
/document/group/offline
/document/group/offline/file
/hash/offline/init
/hash/offline/file/init
/hash/group/offline/init
/hash/group/offline/file/init

III. Mobile SDK—Basic & Enhanced One-time IDV

{NEW}
New parameters are added for user data to both methods

Now the list of user data that can be returned is:

Allowed parameters	Basic	Enhanced
Names, national transliteration	Y	Y
Latin names	Y	Y
Identification number	Y	Y
Document number	Y	Y
Document country	Y	Y
Document type	Y	Y
Document validity date	Y	Y
Document issue date	–	Y
Document issuer name	–	Y
Date of birth	Y	Y
Place of birth	–	Y
Address	Y	Y
Nationality	–	Y
Sex	–	Y
Pictures:User photoID doc photosVideoLiveness (Y/N)Face match (Y/N)Person presence (%)	Y	Y

{NEW}
Get data via API

If you are using our basic IDV solution via the mobile SDK integration, now you can request the PII data of the user via API request:

/onetimeidentification/mobilesdk/getdata

{NEW}
Status check via API

Get a detailed status of the identification via new API request:

/onetimeidentification/mobilesdk/status

Process is finished	processFinish
User has passed the face recognition step	isIdentified
User identification is reviewed	isSupervised
User has canceled the process	cancelProcess
User identification is rejected	isRejected
unsuccessReason	View list code

Example response:

{NEW}
Control the document type support for the identification process

Start the Mobile SDK identification flow by adding the required document type (enc_data: user_document_type), and we will validate that the required document type is used during document scanning.

It can be either:

ID card
Passport

If there is no match, the user will see an error message on the screen, and new result code is returned: unsuccess_reason: 108 – Document Type not match with input.