POSTIDENT System
Auskunftsportal: New export function for your account overview
User accounts with the "User Administration" role can now export an overview of all user and system accounts for your company from the POSTIDENT Information Portal as an Excel file. To do so, select the "Export account list" button in the upper-right corner of the "User Administration" section. The file contains a separate row for each combination of account and assigned role.
POSTIDENT by video chat
New substatus reason for identification documents not accepted due to regulatory requirements
As announced in our communication of 27 August 2026, we are adding a new substatus reason to the result information. This is set if an identification document that is generally supported by the respective identification method does not meet the applicable regulatory requirements.
Status Substatus Substatus reason Change incomplete 50 Problem with identification document 501 Identification document not accepted by regulation NEW: Substatus reason
POSTIDENT Apps and SDK
Android App
AutoID
Modernised app design: POSTIDENT by AutoID has been technically and visually modernised and adapted to current Android standards..
Online ID function (eID)
The "Submit" button has been visually highlighted, making it easier to identify.
If the connection between the smartphone and the identification document is interrupted, the NFC scan can be restarted without having to restart the entire identification process.
General app improvements
Navigation structure: The navigation has been made clearer. Users can now more easily see where they are in the identification process and which steps are still to come.
iOS App
AutoID
Modernised app design: POSTIDENT via AutoID has been technically and visually modernised and adapted to current iOS standards.
Online ID function (eID)
The "Submit" button has been visually highlighted, making it easier to identify.
General app improvements
Optimised display on iOS 26
The display of the POSTIDENT App has been optimised for the "Liquid Glass" design introduced with iOS 26.
iPhone 18 Pro - camera support
Camera functionality within the POSTIDENT App has been optimised for the iPhone 18 Pro to continue to ensure reliable image capture quality.
Overview of current versions:
| SDK | Version | Date of release | End of official support | New features |
|---|---|---|---|---|
| iOS | 2.18 | 10.06.2026 | 10.12.2026 | SDKUIConfigBuilder Class Re enabled We have re enabled the SDKUIConfigBuilder class, allowing you to individually configure the animation behavior during SDK startup and adapt it to your app's requirements. Support for iOS Versions
General Improvements
POSTIDENT via eID Function
POSTIDENT by post office
Notice Regarding SSL/TLS Security in the POSTIDENT SDK: We are providing updated certificate and hash value information for the existing SSL/TLS pinning method for the last time. This is due to a planned certificate change in the autumn. From 2027 onwards, we will significantly simplify security: Regular updates of certificate hash values will no longer be required, substantially reducing your maintenance effort. Current adjustments (transition phase) For the POSTIDENT SDK, we are providing updated hash values for the previously used SSL/TLS pinning method for the last time. This adjustment is necessary because the POSTIDENT certificates will be renewed in the autumn.
Future migration to CA certificate pinning From April 2027, the previously used SSL/TLS pinning will be completely replaced by CA certificate pinning at DPDHL level. Your benefits from this change:
To continue using POSTIDENT SDKs, it is necessary to switch to the respective current SDK version no later than April 2027. |
| iOS | 2.19 | 26.08.2026 | 26.02.2027 | Initialization of the Host App in Light or Dark Mode When initializing the SDK, it will now be possible to enforce either Light Mode or Dark Mode via a flag. This can be particularly useful in scenarios where the host app uses a Dark Mode-like design by default. POSTIDENT E-Signing For regulatory reasons, it is not permitted that, in cases with multiple signatories, at least two signatories use the same device (smartphone or tablet). Previously, this invalid configuration was only detected at the end of the process. To improve the user experience, a validation is now performed at the beginning of the identification process. If another signatory in the same signing case has already used the same device for identification, the user will receive a clear and informative error message at an early stage. |
| iOS | 2.20 | 21.10.2026 | 21.04.2027 | Navigation Structure The navigation structure within the POSTIDENT SDK has been simplified and made more intuitive. This provides users with clearer guidance throughout the identification process and a better understanding of their current step as well as the remaining steps. POSTIDENT by AutoID The user interfaces within the AutoID process have been further optimized and standardized. In addition to revising the method and process descriptions, the screens used for capturing ID documents and video selfies have been modernized to guide users more effectively through the identification process. |
| iOS | 2.21 | exp. cw 48 2026 | POSTIDENT by AutoID The method has been technically and visually modernised and adapted to current iOS standards. POSTIDENT by Online ID function The "Submit" button has been visually highlighted, making it easier to identify. General improvements
| |
| Android | 2.18 | 12.06.2026 | 12.12.2026 | Stability improvements
Modernized app design
Notice Regarding SSL/TLS Security in the POSTIDENT SDK: We are providing updated certificate and hash value information for the existing SSL/TLS pinning method for the last time. This is due to a planned certificate change in the autumn. From 2027 onwards, we will significantly simplify security: Regular updates of certificate hash values will no longer be required, substantially reducing your maintenance effort. Current adjustments (transition phase) For the POSTIDENT SDK, we are providing updated hash values for the previously used SSL/TLS pinning method for the last time. This adjustment is necessary because the POSTIDENT certificates will be renewed in the autumn.
Future migration to CA certificate pinning From April 2027, the previously used SSL/TLS pinning will be completely replaced by CA certificate pinning at DPDHL level. Your benefits from this change:
To continue using POSTIDENT SDKs, it is necessary to switch to the respective current SDK version no later than April 2027. |
| Android | 2.19 | 21.09.2026 | 21.03.2027 | UX Improvements Standardization of navigation and usability for the "Accessibility Statement" and FAQs. POSTIDENT E-Signing For regulatory reasons, it is not permitted that, in cases with multiple signatories, at least two signatories use the same device (smartphone or tablet). Previously, this invalid configuration was only detected at the end of the process. To improve the user experience, a validation is now performed at the beginning of the identification process. If another signatory in the same signing case has already used the same device for identification, the user will receive a clear and informative error message at an early stage. Dependency Version Compatibility OKHttp 4.x The POSTIDENT SDK still uses OkHttp internally, but the SDK now publishes a shaded implementation of OkHttp and Okio so that consuming applications do not need to align their own OkHttp versions with the SDK. This is intentionally done to support customer applications that already use a different OkHttp version or need to upgrade OkHttp on their own schedule. In other words: you can use the OkHttp version that best fits your application without having to force the SDK to the same version. The shaded HTTP client is packaged inside the SDK artifacts, relocated away from the standard okhttp3 / okio package names, and is not exposed as a regular transitive dependency anymore. Integrators should continue to depend only on the published SDK artifacts and should not reference shaded OkHttp classes directly. |
| Android | 2.20 | 16.10.2026 | 16.04.2027 | Android 16 Additional security mechanisms have been integrated for Android 16 to further protect sensitive customer data against unauthorized access during the identification process. POSTIDENT by AutoID The user interfaces within the AutoID process have been further optimized and standardized. In addition to revising the method and process descriptions, the screens used for capturing ID documents and video selfies have been modernized to guide users more effectively through the identification process. |
| Android | 2.21 | exp. cw 48 2026 | New Google Play quality requirements New technical quality requirements from Google for Android apps will apply from February 2027. The POSTIDENT Android SDK has been updated accordingly as of version 2.21. We recommend that business customers who have integrated the POSTIDENT Android SDK into their app update to version 2.21 or later. In addition, please review Google's requirements for your own app. POSTIDENT by AutoID The method has been technically and visually modernised and adapted to current Android standards. POSTIDENT by Online ID function
General improvements Navigation structure: The navigation has been made clearer. Users can now more easily see where they are in the identification process and which steps are still to come. |
Release 36.0:
Rollout of Release 36.0 is scheduled for 19.01.2027.


