Improved processing and reprocessing of Datachecker verifications

For identification and verification processes, MSR uses Datachecker, for example via Secure ID Link and IDVerify. In the previous situation, the result of a verification was processed immediately without being stored persistently. If something went wrong during processing, reprocessing was not possible and there was a risk of data loss.

With this improvement, the processing of Datachecker verifications is more robust, more transparent and can be re-executed in case of errors.

Who is this feature relevant for?

• Application administrators responsible for integrations with Datachecker

• Organizations using Secure ID Link or IDVerify

• Combi customers where documents and verifications are an important part of the process

Feature explanation

To improve the processing of Datachecker results, a new object has been introduced: Datachecker Transaction. This object stores transactions and results separately from documents, ensuring they are always available for reprocessing.

Main components:

• A separate Datachecker Transaction is created for each Secure ID Link or IDVerify

• Transaction ID and Result ID are stored and tracked separately

• Each transaction has a clear status, such as Sent, To be processed, Processed or Expired

• Documents are explicitly linked to the corresponding Datachecker transaction

• In case of errors, the transaction remains available for reprocessing

Processing takes place in three steps:

Sending
When starting a Secure ID Link or IDVerify, a Datachecker transaction is created and linked to the contact and relevant documents.

Retrieving results
A scheduler configured by the customer periodically checks whether Datachecker has returned results. Received results are securely stored before further processing begins.

Processing results
Results are processed in a separate batch. On success, the transaction is completed. In case of errors, the transaction remains available for later reprocessing.

If Datachecker indicates that a result has expired, the transaction is automatically marked as Expired and will no longer be processed further.

Improved error handling

In case of processing errors, an interface log is now always created. Large Base64 document parts from the Datachecker response are filtered out, so that the full JSON structure remains available without truncation. The interface log can also be linked to the relevant person, making it easier to analyze issues.

Other features in the 2026-02 release 

🔗 Please find an overview of other features in this release here.