POSTIDENT by post office
Reading the eID chip in post offices
As announced, starting in July 2026 the chip of identity documents with German eIDs will be read in the post office, and a blocking list check will be performed (see the announcement of the new sub-status reason "Identification document blocked by authorities" in the release notes for Release 29.0).
With Release 32.0, we are now additionally providing the DKK (service- and card-specific identifier) in the result PDF and in the additionalDataBasic object of the result JSON (additionalDataBasic.dkk). The presence of the DKK in the result data indicates that a successful chip reading has taken place for the identification method:
DKK is filled - no blocking list note - | DKK is not filled - blocking list note - | DKK is not filled - no blocking list check possible - |
|---|---|---|
|
|
|
POSTIDENT Delivery
Restoration of restricted access rights to the archive endpoint of the ident product
Up to Release 31.0, it was incorrectly possible to archive cases of the POSTIDENT Delivery product via the archive endpoint of the POSTIDENT Ident product (GET .../{clientId}/cases/archive) instead of using the archive endpoint intended for the POSTIDENT Delivery product (GET .../{clientId}/cases/delivery/archive). As some POSTIDENT Delivery customers were using this incorrect endpoint, we temporarily allowed its use during a transition period. With Release 32.0, this transition period will now come to an end. Please use exclusively the following endpoints to archive cases via SCR:
POSTIDENT Ident POSTIDENT Zustellung PATCH .../{clientId}/cases/archive PATCH .../{clientId}/cases/delivery/archive
POSTIDENT Apps and SDK
Android App
Stability improvements
Resolution of multiple defects and crashes to ensure more reliable use of the app.
Modernized app design
The Android app has been technically and visually modernized and now complies with current platform standards. This applies to the methods "POSTIDENT by Online Identification Function" and "POSTIDENT by post office".
| Screenshots | ![]() | ![]() | ![]() | ![]() | ![]() |
|---|---|---|---|---|---|
| Meaning | Method description "Online Identification Function" | "Online Identification Function" User Consent (new) | PIN selection option (new) | Entry of 6-Digit PIN | NFC-Scan |
| Screenshots | ![]() | ![]() | ![]() |
|---|---|---|---|
| Meaning | Method description "Post office" | Display of coupon codes | Coupon code details |
POSTIDENT iOS App
Support for iOS versions
Compatibility with iOS 26
The POSTIDENT app is fully compatible with iOS 26.
Improved support for older iOS Versions
Optimizations for older iOS versions (e.g. iOS 17.x) ensure more stable usage.
General Improvements
Optimized Design and Improved Stability
Revised app interfaces and improvements in app behavior in the event of interruptions across various usage scenarios.
POSTIDENT via Online ID Function
Improved support for PIN selection
Users receive helpful guidance directly within the app on selecting the correct PIN (5 or 6 digit, or PIN unknown).
Clearer display of ID data to be read
The requested data from the ID document is presented in a more clearly structured and easier-to-understand format.

POSTIDENT by post office
Improved display with large font sizes:
The post office matrix code and identification data are reliably displayed even when larger font sizes are used.
Further UX optimizations
Enhancements to enable easier and more accessible use of the post office method.
Overview of current versions:
| SDK | Version | Date of release | End of official support | New Features |
|---|---|---|---|---|
| iOS | 2.17.1 | exp. CW 18 2026 | POSTIDENT by post office
POSTIDENT by eID function
POSTIDENT by AutoID
| |
| iOS | 2.18 | exp. CW 22 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 Online ID 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 March 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 March 2027. | |
| Android | 2.17 | 01.04.2026 | 01.10.2026 | Android 16 Support "Edge-to-Edge"
POSTIDENT by AutoID Minor improvement of user understanding during face verification by replacing the illustration graphic. SDK Dependency Version Compatibility The POSTIDENT SDK relies on a set of well-established third-party libraries. While these dependencies are declared internally, they are resolved together with the consuming application's dependency graph at build time. To ensure correct behavior, applications integrating this SDK must use compatible versions of the required libraries. Gradle will automatically select the highest compatible version present in the dependency graph. Using significantly older versions than those listed below may lead to build-time resolution failures or unexpected runtime behavior. The SDK is regularly tested against the versions specified below. ![]() |
| Android | 2.18 | exp. CW 22 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 March 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 March 2027. |
Release 33.0:
Rollout of Release 33.0 is scheduled for 07.07.2026.









