• Overview of current versions:

Release 24.0: Rollout of Release 24.0 is scheduled for January 21st, 2025.

• Overview of current versions:

Release 23.0:

Rollout of Release 23.0 is scheduled for November 12th, 2024.

• Overview of current versions:

Release 22.0: Rollout of Release 22.0 is scheduled for September 3, 2024.

• Support of the languages French, Italian, Portuguese and Turkish in the POSTIDENT frontend

  There is an extension of language support for the apps (iOS/Android) to include the languages French, Italian, Portuguese and Turkish. So far, the languages German, English, Polish and Spanish have already been supported. If the user has chosen the languages French, Italian, Portuguese or Turkish in the smartphone/tablet settings, the POSTIDENT app will adopt the chosen language. If the user has set a language which the POSTIDENT app does not support, the default language English will be used. The support of the new languages only refers to the identification process in the app. Emails and SMS will continue to be offered in German and English.

• Overview of current versions:

• POSTIDENT TestApp on Integration and Test Environment (ITU)

  The POSTIDENT TestApp available on the Integration and Test Environment (ITU) now offers the possibility to generate ident cases directly via the user interface of the TestApp. The alternative possibility to simulate identifications for existing cases previously generated via SCR / EasyConnect, as before, remains. By default, the TestApp is loaded in "Existierenden Vorgang suchen" mode. The search mask corresponds to the previous search mask. By clicking on "Neuen Vorgang erzeugen", you can now switch to another mask that allows you to create a new ident case. First, a specific billing number (ClientID) must be selected. The mask then shows which ident methods are configured in the respective billing number (ClientID) and can therefore be simulated with a ident case generated in it.

Release 21.0:

• Discontinuation of result format XML

  As previously announced, the XML result format will be finally discontinued with release 19.0, leaving the JSON and CSV result formats (we recommend using the JSON result format - among other things, due to a limited dataset with CSV). There are no active customer configurations for provision in XML format via sFTP already. After the rollout of this release, a download of the XML format via the POSTIDENT Information Portal is no longer possible.

• Increase in the minimum length of passwords for user accounts to 15 characters The minimum length of passwords for user accounts will be increased from currently 12 to 15 characters. The new password policy applies to all passwords that are newly assigned from release 19.0 onwards, i.e. existing passwords do not have to be changed immediately. Passwords for new accounts or changed passwords (e.g. due to expiry after 90 days) must, however, meet the new minimum length of 15 characters.

• Notification of imminent deactivation of a user and system account Since release 17.0, for security reasons, user accounts are deactivated after 120 days of inactivity and system accounts after 180 days of inactivity. New with release 19.0 is that such accounts are informed by email 21 days before deactivation and are requested to log in to the respective POSTIDENT system.

• Email notifications about new identification results in the POSTIDENT Information Portal Users of the POSTIDENT Information Portal can optionally receive email notifications with the number of completed identifications for their assigned billing numbers (ClientIDs). The feature allows the user to configure the email notifications themselves in the Information Portal. The corresponding configuration can be found under the menu item "Einstellungen", which can be reached by clicking on the username at the top right. By default, the feature is deactivated for all users, so no unwanted email notifications are sent. If the feature is activated by the user, they can configure a notification interval of n hours and then receive a notification email to their login email address every n hours (initially n hours after activation). The email contains a table in which the different POSTIDENT identification methods are listed in columns and the billing numbers assigned to the user are listed in rows. In the individual cells, the number of new identification results provided since the last notification for the combination of billing number and identification method are listed. The last row and column each show the totals over all billing numbers or identification methods respectively. Currently, this email is only available in German.

• Expansion of supported ID cards

  From release 19.0, the AutoID method also supports identification documents from the following 25 countries: Afghanistan, Andorra, Armenia, Azerbaijan, Australia, Cyprus, Georgia, Gibraltar, India, Indonesia, Iraq, Iran, Israel, Jordan, Lebanon, Liechtenstein, Malaysia, Malta, Monaco, New Zealand, Pakistan, Philippines, Singapore, Sri Lanka, Vatican (city state).
• The list of all currently supported ID identification documents can be found at www.postident.de/download in the "Manuals / Release Notes" section - this will be supplemented with the added identification documents for release 19.0.

• Raising the Minimum SDK Version

  In order to continue to provide the best possible support and security, we will raise the supported minimum SDK version from 1.0 to 2.0. This means that users of business customer apps, where an SDK version of version 1.6 (or smaller) is used, will receive a notice that identification is not possible and the POSTIDENT app must be downloaded from the AppStore/ PlayStore for this.

• Overview of current versions:

Release 20.0:

• Expansion of supported ID cards

  Additional ID cards have been added for the nationalities Belarus, China, Denmark, Estonia, Finland, Iceland, Ireland, Japan, Republic of Korea, Latvia, Lithuania, Moldova, Norway, Russian Federation, Sweden, Taiwan, Thailand, which will be supported in the AutoID process with release 18.0.

• New substatus reason for shipment-specific return addresses

  With Release 17.0, the option to define individual return addresses per shipment was introduced. This resulted in the following features:
  • For the provision of a request without return addresses - with appropriate configuration of shipment-specific return addresses - the new substatus reason 339 is introduced within the combination 309/25/339 (309 declined / 25 problem with digital provisioning (data quality) / 339 case declined due to insufficient return address data in digital provisioning by business customer).
  • The element <ReturnAddress> is only part of the response if a shipment-specific return address has been handed over in the request, i.e. if the element is empty (<ReturnAddress/>), it is hidden.

• End of operating system support

  With the new release, support for the following operating systems will be discontinued:
  • Android: 5, 6 and 7
  • iOS: 13 and 14

• Overview of current versions:

Release 19.0:

POSTIDENT System

• Easy Connect URLs

  As already announced in our communication to the affected customers on March 9th, 2023, the redirections of the Easy Connect interface to the old URLs (postident.deutschepost.de/identportal/wl?an={billing number} &rn={reference number} or postident.deutschepost.de/identportal/wl?an={billing number}) will be switched off, which means that these URLs will no longer work after the rollout of Release 17.0. If you are already using the new versions of the URLs for the Easy Connect interface that have been available since March 2021, there is no need for action on your part:
  • Call with reference number: postident.deutschepost.de/user/start/?an={billing number}&rn={reference number}

  • Call without reference number: postident.deutschepost.de/user/start/?an={billing number}

    If you are still using the old link, please switch to the new URL. As of November 14th, 2023, identifications can no longer be carried out using the old URLs.

• Hiding empty objects in SCR JSON result data

  According to our convention, only filled fields are delivered in the result JSON, while empty fields (e.g. not relevant for your regulatory class) are hidden. However, until now this rule has only been followed by individual fields, while objects remained as empty containers. With release 17.0, the behavior is standardized and empty objects are now also hidden.

POSTIDENT Information Portal

• Deactivation and deletion of user and system accounts

  For security reasons, user and system accounts will be deactivated after 120 days of inactivity. If access is still required after deactivation, please contact your user administrator or the Serviceteam POSTIDENT to have your access reactivated. The following applies to user accounts only: If access is not reactivated, your account will be deleted 60 days after deactivation.

POSTIDENT by AutoID

• Information update of POSTIDENT by AutoID

  The procedure POSTIDENT by AutoID is the automated identification process for quick and secure identification with ID cards. Your customers can be identified in a user-friendly manner around the clock via smartphone using machine learning techniques. You can find more information about POSTIDENT by AutoID at postident.de/autoid. You will also find a video tutorial illustrating the process. The AutoID process is part of the POSTIDENT portfolio for standard (including “non-GwG”) use cases and can be used in addition to POSTIDENT by video chat, POSTIDENT by post office and POSTIDENT by online ID function (eID). If you have any further questions, please contact the Serviceteam POSTIDENT.

• Expansion of supported ID cards

  Additional ID cards have been added for the nationalities Belgium, Canada, Spain, France, Great Britain, Luxembourg, Macedonia, Montenegro, Netherlands, Portugal, Serbia and the USA, which will be supported in the AutoID process with release 17.0.

POSTIDENT delivery

• Individual return addresses per shipment

  A return address is currently defined globally for all shipments that are sent with your billing number. Alternatively, it is now possible to define an individual return address for each shipment instead. In order to do this, the use of individual return addresses must be configured for your billing number (please contact the Serviceteam POSTIDENT). Detailed information on the transfer of individual return addresses when placing an order can be found in our documentation in the SFTP Delivery API Guide Start in Chapter 3, XML files as a new ReturnAddress element can be found under Structure of Delivery Request (will be updated for rollout).

POSTIDENT Apps and SDK

• Adjustments to POSTIDENT by online ID function

  Adjustment of individual text elements for POSTIDENT by online ID function process due to the rebranding of “AusweisApp2” to the new name “AusweisApp”

• Supporting the user at POSTIDENT through video chat

  In order to make it easier for the user to interact with the agent, a new page is integrated before the chat starts. This page contains tips for the user so that the agent can quickly and easily recognize the security features on the ID card.

• Overview of current versions:

Release 18.0:

POSTIDENT by video chat

• Introduction of a new sub-status in case of improper use of the procedure

  If POSTIDENT by videochat is misused by a private customer, the agent now has the option of rejecting the ident with substatus 15 abuse (421 declined/15 abuse). In this case, identification with the declined caseID is no longer possible across all methods.

POSTIDENT by online ID function (eID)

• Improvement of user understanding

  To explain the CAN (access number), the existing FAQ for the article "What is the CAN and what do I need it for?" will be added with Release 16.0. Specifically, the FAQ contains extended information on when to use the 6-digit access number on the front of the ID card.

POSTIDENT Apps and SDK

Support of the user languages Spanish and Polish

• If the user has set up the languages Spanish or Polish in the smartphone/tablet settings, the POSTIDENT app will adopt the selected language. If the user has not set up German, Spanish or Polish, the default language is English.

• The support of the new languages Spanish and Polish only refers to the ident process in the app. E-mails and SMS will continue to be offered in German and English.

• UX adjustments when using an iPad (iOS)
• Improved compatibility of older iPhones with a 720p front camera when using Fotoident

Overview of current versions:

Release 17.0:

Rollout of Release 17.0 is scheduled for November 14th, 2023.

• The user can display his camera in the waiting area.

• If the user moves the app to the background, a local notification is sent after 5 seconds that the video chat will automatically end after 15 seconds, if the user does not return to the Postident app. By clicking on the notification, the user returns to the waiting area.

Improvement of usability

Entering different customer data during the identification process is simplified, i.e. the end customer is offered a suitable keyboard layout for the data to be entered.

• Date of birth / date of issue: datepicker
• Mobile phone number: enter numeric data

Introduction of a new iOS SDK framework

With the iOS SDK version 1.3, which is expected to be released at the beginning of August, we are separating from the previous use of Cocoapods in order to integrate the SDK on iOS end devices of business customers. With the iOS SDK version 1.3, a new framework is used to significantly simplify the time required to integrate the SDK and the effort involved in the update process to a new iOS SDK version. Existing SDK customers will receive appropriate migration documentation for switching to the new SDK framework.

Postident Apps and SDK

• Overview of current versions

Release 9.0:

The rollout of Release 9.0 is planned for September 6th, 2022.

POSTIDENT by videochat

In terms of quality improvements place holders used for identification numbers of temporary German passports will no longer be filled with zeros. Unlike other passports the place holder can not be found at the end of the identification number, but rather on second position. Example: DEU_I6:

The identification number consists of one letter, followed by a place holder, followed by 7 digits. As of now the place holder will not be filled with a zero any longer, so that the identification number is captured without a place holder, as in this example: C0000000.

POSTIDENT delivery

For more transparency in regard to result data of our POSTIDENT delivery customers the new substatus reason 335 (identification check negative, other reason) is implemented. This new substatus reason will automatically be delivered via existing interfaces.

POSTIDENT SDK Support

Note:Please make sure to always use an updated version of the SDK app. In case of an outdated version the user will be redirected to the POSTIDENT app. The following table shows the versions that are currently supported as well as the end of the official support:

Note:In December 2021 a vulnerability within the Google Places library has become known. The Android SDK uses Google Places for displaying post offices on Google Maps for POSTIDENT by postoffice. The weak point has been evaluated and rated as not exploitable. In the new SDK 0.7.2 version the vulnarability has beend closed, therefore we recommend a contemporary update.

Release 7.1:

Rollout of release 7.1 is scheduled for March, 22nd, 2022.

POSTIDENT Portal

• Customers with active webhooks will from now on receive a webhook with every declined case. While there had been only certain exceptions until now (e.g. operation valid time frame exeeded), webhooks for ident customers will also be sent out when the substatus is 12 or 17.
• Customers who are set up for the user administration at the Auskunftsportal can benefit from different improvements regarding usability and security starting with the new release. The independent administration of users and system-accounts for the Postident system is therefore getting more easy and secure. In case you are not set up yet for the user administration, you are welcome to contact our serviceteam for an initial setup. You will find more information in the SST AG-Ergebnis Guide on our download sitehttps://www.deutschepost.de/de/p/postident/downloads.html.

POSTIDENT SDK Support

Note:Please make sure to always use an updated version of the SDK app. In case of an outdated version the user will be redirected to the POSTIDENT app. The following table shows the versions that are currently supported as well as the end of the official support:

With the rollout 6.9 on November 16th the support of version 0.5 will be discontinued.

POSTIDENT Portal

• The SCR-Signing and SCR-Ident interface support only secure webhook-URLs with HTTPS encryption. As we are not aware of any URLS without an HTTPS encryption at the moment, there is no need for action on your side.
• Customers who are set up for the user administration in the Auskunftsportal can benefit from new advantages starting release 6.8, as the administration of data passwords and publics keys is going to be much easier:
  1) When creating a data password it is now possible to specify the exact time at which the data password will be valid. This way there is no more need for coordination with POSTIDENT regarding the exact moment of data passwords changes.
  2) Every SFTP user can now create up to 3 public keys in order to make the administration easier when changes are necessary. These public keys can also be deleted again as long as at least one public keys stays valid.

If you are interested in an independent administration of users in the Auskunftsportal, please contact the Serviceteam Postident for an initial setup: serviceteam.postident@deutschepost.de

POSTIDENT E-Signing

• For users of the test- and integration environment (ITU) the Signing test app for an independent simulation of test cases is now also available inEnglish.

POSTIDENT SDK support

Note:Please make sure to always use an updated version of the SDK app. In case of an outdated version the user will be redirected to the POSTIDENT app. The following table shows the versions that are currently supported as well as the end of the official support:

POSTIDENT Portal

• Coloured highlighting of declined idents in the Auskunftsportal

  We now mark declined idents more clearly and highlight the status in the result-PDF in red. By doing so, we minimize the risk of high-risk idents being missed when manually processed.

• Request of basic-coupons through partners

  It is now also possible for your partners (e.g. comparison portals) to retrieve POSTIDENT coupons for identification at the post office and make them available to the customers.

• Delivery of a new test-app

  Providing that you have access to our test- and integration environment (ITU), a new test-app is now available. The test-app enables users to independently simulate identification cases. In case you don’t have access to the ITU yet, you can set up an integration project with the help of the Serviceteam POSTIDENT.

• Implementation of a user administration in the Auskunftsportal

  The user adminstration in the Auskunftsportal enables users to independently administer user and system-accounts for the Postident system. You will find more information on this subject in theSST AG-Ergebnis Guideon ourdownload site.

References

• Please note that the outdated result data format XML in the Auskunftsportal will be provided no longer than December 31st, 2021.

POSTIDENT Portal

• E-Signing: After completing the ident case the customer will immediately be sent a reminder e-mail including a re-entering link to the signing case. Before the release a reminder-email had been sent out only after 24 hours. With the earlier sending of the reminder e-mail from the new release onwards, private customers are supported in completing the signing process more quickly.

• We are working on AI-supported improvements to the identification procedure POSTIDENT by video chat in order to extend the options to identify fraudulent activities.

  In this context, we inform users in the data privacy information that biometric data can be used.

References:

• Please note that the outdated result data format XML in the Auskunftsportal will be provided no longer than December 31st, 2021.
• The following identification documents for video and photo ident have been activated since the last release: ALB_P4, AUS_RB12, AUS_RB26, BFA_P4, BGD_P7, BGD_P8, CHE_P6, COL_P7, CYP_I4, EGY_P4, EST_P11, GBR_RB10, GBR_RB11, GBR_RB12, GBR_RB13, GBR_RB20, GBR_RB21, GBR_RB30, GBR_RB31, GBR_RB32, GBR_RB33, GBR_RB38, GBR_RB39, GBR_RB58, GBR_RB59, GHA_RB3, MLT_I5, NOR_P7, PRT_P6, SLV_I2, UZB_RB1

The complete list of all supported documents can be found on our download website:https://www.deutschepost.de/de/p/postident/downloads.html

Content: Bug fixes and improvements

POSTIDENT Portal

• Omission of data field Salutation

  For starting an E-Signing case it is no longer mandatory to deliver the data field "salutation". It is an optional field. The result data via SCR-interface (SCR ident as well as SCR E-Signing) will be delivered without the data field "salutation". So far the delivery of this field had been optional.

• New substatus reasons for fraud suspicion for POSTIDENT by postoffice

  New substatus reasons for the status declined (fraud suspicion) will be displayed at POSTIDENT by post office. These comprise "multiple identity checks for single person", "multiple persons present" and "multiple identity checks for single person over a longer period".

  You can find the adjusted interface description in ourdownload portalon page 14.

• Changes regarding supported key exchange process (KEX):

  There will be adjustments regarding saftey-related configurations of our SFTP-Server (postident-transfer.deutschepost.de Port 22), of which Ident- and Signing results can be obtained. We do not expect the need of adjustment on your system. However, to make sure please check if your SFTP-Client can handle these adjustments:

  -The KEX-process "diffie-hellman-group-exchange-sha256" will only accept key lengths of at least 2048 Bit (until now 1024 Bit)

  -The following additional KEX-processes are supported: diffie-hellman-group14-sha256, diffie-hellman-group15-sha512, diffie-hellman-group16-sha512

• Modifications to supported host key types (server authentification):

  The SFTP-Server additionally offers an ed25519 key for server authentification. Fingerprints:

  -SHA256:JyPAAXn3I82oojXq0Tw0X+qRlbl4xAx0shHgf0K0O6U

  -MD5:cd:4f:c3:d4:44:81:01:28:7b:5b:1d:12:2d:f0:f6:b8

• Discontinuation of support of the Windows Internet Explorer

  The support of the Windows Internet Explorer for the ident portal will no longer be continued as the share of users has fallen below 1%. Following note is being displayed for the user:

POSTIDENT apps and websites

• POSTIDENT apps – change of language via system language

  A change of language in the apps will only be possible through the change of the system language via device settings.

POSTIDENT Portal

• Support of the Edge browser for Postident by video chat

  From release 6.3 the Microsoft Edge Browser will be supported for Postident by video chat. In exchange the support of the Internet Explorer will end with release 6.4 (10th February 2021) due to a decreasing number of users.

• System adaptions and improvements in the backend

  Additionally several system adjustments and improvements in the backend will be implemented in this release.

  Up to date those changes have no functional impact on the services you use.

POSTIDENT Portal

• New substatusreason social engineering for fraud suspicion in Postident by video chat

  The new substatusreason social engineering will be displayed for status declined with substatus fraud suspicion for Postident by video chat.

  This reason will be indicated when there is a suspicion that the person to be identified has become victim of a kind of fraud that is called social engineering.

  You can find this supplement in the interface description on our download page on page 10.

• New substatus and substatusreasons for status incomplete and declined for Postident by eID

  For Postident by eID many new substatus and substatusreasons will be displayed for status incomplete and status declined. This way you get more transparency over the identification process and it easier for you to understand the reasons for termination.

  You find the corresponding values and their short description in the interface description on our download page on page 11.

• Delivery of birth name for Postident by eID for class GwG

  For Postident by eID for class GwG (German Money Laundering Act) the birth name will be read out and delivered with the result data if available.

• Position of the header information in the result data pdf has changed

  The Information in the header of the result data pdf will be shown on the left side and not on the right side anymore.

  Accordingly the logo of Deutsche Post will be displayed on the right side and not on the left side. This makes it possible to display long values in the data field "Eigene Referenz 1".

Example for the new header

• Increasing the security of passwords

  In order to increase security for system accounts (e.g. SCR-Ident, SCR-Signing) and for data passwords of the zip file encryption (e.g. Auskunftsportal, SHAFT), the length of the passwords is increased from 12 to 24 characters. This rule applies for all system account passwords and data passwords generated after rollout of release 6.2.

  Passwords for personal accounts to the Auskunftsportal are not affected by this change.

POSTIDENT portal

• POSTIDENT by post office will be purely digital by 30th September 2020!

  At the latest on 30th September 2020 you will no longer receive paper forms with the POSTIDENT by post office result data.

  As of this date you will receive result data from post office identifications only digital.

  Please adjust your processes on time and contact us via our website: www.postident.de/digitalisation.

• Measures to enhance quality and stability

  With this release several system adjustments are made which improve the quality of identifications and the stability of the POSTIDENT system.

POSTIDENT portal

• POSTIDENT by post office will be purely digital by 30th September 2020!

  Benefit from the advantages of digitization early on. You won’t receive any paper forms for POSTIDENT by post office cases by 30th September 2020 at the latest. From this point of time you will receive identification data from the post office purely digital. Please adjust your processes on time. Further information and an option to contact our serviceteam can be found at www.postident.de/digitalisation.

• Deactivation of the SHA1DSA algorithm for signature verification on the release rollout date

  The SHA1DSA algorithm, with which we sign the result files of our identification and signing processes, as well as video recordings will be deprecated since it no longer meets the currend security requirements. We will carry out the deactivation on July 14th 2020. From this date on, no signature files will be delivered with the SHA1DSA procedure, but only signature files according to the RSA-PSS (RSAASS-PSSS) procedure. We already announced this change in April 2019 and in May 2020.

  The certificate for RSA-PSS can be found on our website under "Digitales Zertifikat (RSAPSS) zur Überprüfung der in einer Datendatei enthaltenen Dokumente (Gültig: 27.03.2019 bis 25.03.2024)" or via this download link.

  In case you check signature files, you can only continue when switching to the RSA-PSS procedure.

• Completion of the SMS text for the mTAN dispatch (video identifications)

  The SMS text of the video ident mTAN dispatch will be completed by the caseID as well as the name of the identifiying company.

  This enables easier orientation for the client and it improves security.

  SMS Sample text:

  "123456 ist die TAN für Ihre Identifizierung für Demobank im Vorgang JKE235789ZTR."

• Adjustment in the result data portal

  The possibility to retrieve result data from the result data portal in json format is now available for all business customers,

POSTIDENT apps und websites

• Improvement of usability for choice of identification method

  When clients repeatedly call up the portal that is used to select the identification method than the identification method that has been selected before will automatically unfold. This also applies when another device is being used for the identification. This way orientation is made easier for the client, the identification can be continued and completed more target-oriented.

  Example - Postident by post office unfolded:

POSTIDENT Portal

• POSTIDENT by post office will be purely digital by 30th September 2020!

  Benefit from the advantages of digitization early on. You won’t receive any paper forms for POSTIDENT by post office cases by 30th September 2020 at the latest. From this point of time you will receive identification data from the post office purely digital. Please adjust your processes on time. Further information and an option to contact our serviceteam can be found at

  http://www.postident.de/digitalisation

• Changes concerning result data for POSTIDENT by eID of the German national identity card

  - Result format JSON: Ident status „cancelled“ will be renamed to „declined“. As a result the wording is adapted to the wording that is used for other identification methods.

  - Result format CSV/XML: Result data are supplemented by the new status 205 for unsuccessful eID identifications.

  You find those changes in the interface descripitions on our download page:

  https://www.deutschepost.de/de/p/postident/downloads.html

POSTIDENT apps und websites

• Language selection English for your clients (not available for E-Signing and POSTIDENT by photo)

  In the POSTIDENT apps and on the web pages (desktop) the language on the user interfaces is switched automatically to the language (German or English) set on the smartphone or computer.

  Manual selection is also possible.

  Additionally the customer can choose the language of the video chat with the call center agent.

POSTIDENT Portal (general)

• POSTIDENT by post office will be purely digital by 30th September 2020!

  Benefit from the advantages of digitization early on. You won’t receive any paper forms for POSTIDENT by post office cases by 30th September 2020 at the latest. From this point of time you will receive identification data from the post office purely digital. Please adjust your processes on time. Further information and an option to contact our serviceteam can be found at http://www.postident.de/digitalisation

POSTIDENT Portal Interface extension (SCR - REST API)

• In the future the whole identification status (status, substatus, substatusreason) will be provided by POSTIDENT SCR interface in the case of an incomplete identification attempt (incomplete). As a result it will be easier to precisely understand, why a case is incomplete or has been interrupted.

• The identification status incomplete will now also be shown for the identification method eID of the German national identity card. This will happen when for example the customer interrupts the identification process. Like in the other identification methods the identification can be restarted using the same case.

• Extension to the result data: the data field nationality contains four further codes for refugees and stateless persons in addition to the supplement RKS.

  Codes according to ISO-3166 ALPHA-3 plus:

  - RKS for Kosovar

  - NEW: XXA for Stateless

  - NEW: XXB for Refugee (1951 Convention)

  - NEW: XXC for Refugee

  - NEW: XXX for Unspecified

  You will find all changes in detail in our interface description (guide 1 start and guide 2 result) at https://www.deutschepost.de/de/p/postident/downloads.html

POSTIDENT apps und websites

• POSTIDENT app for Apple smartphones/ iPhones includes identification by eID of the German national identity card: - From April 2020

  the identification by eID is now also possible on iOS devices.

  (Picture: starting website for this identification method on the POSTIDENT portal)

  - For further information please visitPOSTIDENT by eID

  - Information:if you already have a connection to the POSTIDENT portal and if you use digital methods for identification then the Identification by eID method can be added simply by being configurated by the serviceteam POSTIDENT.

  - Prerequisitesfor usage by your customers: iOS version 13.2 and higher, NFC functionality, POSTIDENT App

• Language selection English for your customers (not available for E-Signing and POSTIDENT by photo)

  - From middle of April 2020; CHANGE (Status as of 17th April 2020): Due to a delay this feature will be available in Release 5.9 (Rollout 19th May 2020).

  - In the POSTIDENT apps and on the web pages (desktop) the language on the user interfaces will be switched automatically to the language that is configured on the smartphone. (manual selection is also possible)

  - Additionally the customer can choose the language of the video chat with the call center agent.

• POSTIDENT by post office will be purely digital by 30th September 2020!

  Benefit from the advantages of digitization early on. You won't receive any paper forms for POSTIDENT by post office cases by 30th September 2020 at the latest. Further information and an option to contact our serviceteam can be found at http://www.postident.de/digitalisation

• New result data pdf

  A new result data pdf file for all Postident methods is introduced. The pdf contains two new subheadlines "Informationen zum Ergebnis" and "Informationen zum Identifikationsvorgang". Furthermore it has become a dynamic pdf, therefore the different data fields are not always shown in the same position. If a data field doesn't contain content it will not be shown on the result data pdf. The pdf is not suited for automatic data capture.

  Please forward the information concerning the new result data pdf to those speciality departments that use the pdf.

Example of the new result data pdf:

• Anouncement of the provision of additional result data for Postident by post office

  From second quarter 2020 on there will be two new data fields provided by the result data pdf as well as by SCR-interface that describe the adress of the post office. In case it is configured, a user signiture (usersignature) will be delivered. These adjustments can be found in the technical documentation "Standard Connect & Result Ident REST API Guide 2 Result" in the subchapters AdditionalDataBasic and RecordResult on our download page.

  Those additional result data will in part be provided already by end of February but at that time they will not be available for all post offices.

• Optimised Postident coupon via SCR

  The coupon of Postident by post office has been optimised and is now automatically available for customers connected via SCR.

• Entry of the PIN has been simplified for Postident by eID when android devices are used.

Announcement

• Changes of ident status information in release 5.8 (Rollout 24th March 2020)

  In the future the whole ident status (status, substatus, substatusreason) will be provided by SCR interface in case of status "incomplete". Thus it will be easier to precisely understand why an identification case is incomplete and has been interrupted.

  In case of fraud suspicion (status 11) the data field "remark" will be delivered in order zu enhance traceability of the reason for fraud suspicion.

POSTIDENT Portal

• Date of expiry of the identification document will provided for eID identifications class GwG

  For the identification method Postident by eID of the German national identity card the attribute date of expiry will be provided additionally for class GwG (German Money Laundering Act).

Announcement

• POSTIDENT by post office will be purely digital by 30th September 2020!

  Benefit from the advantages of digitization early on. You won’t receive any paper forms for POSTIDENT by post office cases by 30th September 2020 at the latest. Further information and an option to contact our serviceteam can be found at http://www.postident.de/Digitalisierung

POSTIDENT Portal

• Implementation of the new eID certificate to support the class TKG (telecommunication)

  For the eID identification method a new authorisation certificate has been provided. Identification via eID can therefore be used by telecommunication service providers.

POSTIDENT Apps

• Enhancing usability of the Postident app

  - Clients can now find the privacy terms within the Postident app.

  - When creating fotos during a video- or photo identification session the client will now be supported by a frame and by textual instructions.

Announcement

• POSTIDENT by post office will be purely digital by 30th September 2020!

  Benefit from the advantages of digitization early on. You won’t receive any paper forms for POSTIDENT by post office cases by 30th November 2020 at the latest. Further information and an option to contact our serviceteam can be found at www.postident.de/Digitalisierung

Information

• The service POSTID for privat customers will be discontinued

  Deutsche Post has decided to discontinue the service POSTID by end of november 2019.

  POSTID enabled customers to save their identification information which has been collected during a Postident identification.

  The customers were able to authorize Deutsche Post AG in subsequent identification situations to pass on identification data without going through another identification process.

  The service will be discontinued because the demand for the use of the POSTID fell short of expectations.

  The Postident services für business clients to identify private clients by serveral identification methods remain unaffected and are available as usual.

  Deutsche Post will further invest in a market-oriented development of identification solutions and in an expansion of the product portfolio, among other things in the digital signature using POSTIDENT E-Signing and in mobile identification using eID.

• The following data has been removed from the result data set of TKG (Telecommunication) identifications in order to meet the privacy protection requirement of data economy: birthName, birthPlace, nationality, placeOfIssue
• The landing page of postident by video chat has been adjusted visually. Identification with the use of the postident app is now shown more prominent than the possibility to identify via webbrowser since the user experience is better with the Postident app.
  An example is shown below:

• Postident by eID - Introduction of the possibility to change the transportation-PIN

  When receiving a new identity card a user also gets a PIN Mail with an initial transportation PIN (also called activation PIN). The user has to change the transportation PIN into a personally generated six digit PIN in order to use the eID for identification. In the new release this will be possible directly within the identification process.

  View of the screens when changing the PIN:

POSTIDENT Portal

• New status values for Money Laundering Act compliant video identifications:

  - If the video recording for a video case is missing, in the future this case will be delivered as status 421 "declined" with substatus 19 "Identifizierung mit nicht behebbarem Datenproblem in Videochat-Aufzeichnung" (Non-Recoverable Dataproblem with the Video-Recording). This new substatus will only be delivered for future identification cases.

  - Recommendation: If the video case shows this substatus a new identification of the customer has to be started. Initiate a new case for the affected customer through your existing connection to the POSTIDENT portal.

  -You can see the details in the adjusted interface description you find on our download portal at https://www.deutschepost.de/de/p/postident/downloads.html

• Change of the name for identification method by electronic identity card:

  - "nPA" is renamed as "eID"

  - Field name in the SCR result interface: In the identification result data file, which you receive for a Postident by nPA/eID case, the name of the field additionalDataNPaResult is renamed as additionalDataEidResult

  -The adjusted interface description you find in our download portal at https://www.deutschepost.de/de/p/postident/downloads.html.
• Business clients belonging to the category "TKG" or "Standard" won't receive any videochat portrait pictures of their clients anymore. The portrait pictures will not be recorded, because capturing and delivering of the pictures is in those cases not required by regulation.

POSTIDENT Frontends

• POSTIDENT by video chat:

  - Business clients subject to Money Laundering Act (category GwG):

  The person being identified takes temporary fotos of his identification document (front and back side) bevor the chat starts. Several pieces of information necessary for identification are automatically extracted from the taken pictures. The legitimacy of the identification document will be proofed. Afterwards the image data will be deleted. ID card pictures legally required for identification will still be taken by the call center agent during video identication.

  - Business clients not subject to Money Laundering Act (categories TKG or Standard):

  The person being identified takes fotos of his identification document (front and back side) bevor the chat starts. Several pieces of information necessary for identification are automatically extracted from the taken pictures. The legitimacy of the identification document will be proofed. In case the quality is sufficient the pictures of the identification document will be used in the result data set. If quality is insufficient, the pictures necessary for identification will by taken again by the call center agent during the video identification process. During the video identification session the agents make sure that the shown identification document matches the identification pictures made in advance.

POSTIDENT Portal

• Change of substatus values for Postident by post office

  - Change: Substatus reason "118 Ausweisbilder nicht empfangen" will not be delivered with substatus 12 anymore. Instead of substatus 12 the data will be delivered with substatus 17: "Identifizierung mit nicht behebbarem Datenproblem in Ausweisdaten"

  - New: Substatus "18 Identifizierung mit nicht behebbarem Datenproblem in Scandaten"

  - Both substatus will be provided by the interface formats SST JSON, CSV 2.0 und XML 2.0 (additionally to substatus 11, 12, 16 which are already provided by those interface formats). No substatus information is delivered in CSV 1.3 and XML 1.3 data formats.
• Relevant for users of the test environment: the domain postident-demo.deutschepost.de will be turned off in favour of the domain postident-itu.deutschepost.de
• The post office ID where an identification has taken place is now always included as additional information in the result pdf. Until now it was already present for TKG based Identifications as well as results with potential fraud.
• Announcement: New signature algorithm RSA-PSS for result data files of identification and e-signing cases. Replacement of the old algorithm SHA1DSA by RSA-PSS will be completed until may 2020. Meanwhile result data will be signed by the new as well as the old algorithm. Until May 2020 two signature files will be provided.

POSTIDENT Frontends

• POSTIDENT iOS App requires the operating system iOS 11 or newer (iOS 10 will not be supported anymore)
• POSTIDENT by video chat: Adjustment of supported browser: Chrome 71+, Firefox 64+ and Firefox 60 (support of Safari- und Opera is removed).

POSTIDENT Portal

• The starting website of Postident by video chat appears in a new design in order to optimize the conversion. The clarity of the website has been improved and the visibility of the FAQs has been enhanced.

• The technical requirements have been established for new types of identification documents in order to use travel documents for foreigners, refugees and stateless persons as well as ministerial and diplomatic passports for our services Postident by postoffice and in part Postident by video chat. Those new types of identification documents are allowed for Postident by video chat from 20th march 2019 and for Postident by post office in the second half of 2019.

  When processing your identification result data please consider that these new identification documents may appear (please see the updated interface description on the download website).

• Announcement: With Postident Release 5.2 (Rollout 7th may 2019) new substatus values will be introduced for our services Postident by postoffice and Postident by video chat. Details will be announced by separate communication.

• Announcement: At the beginning of May the certificate for signing identification result data as well as A/V recordings (also archived A/V recordings) will be changed.

  Details will be announced by separate communication.

E-Signing

• E-Signing is supplemented with the stamp position by means of a machine readable PDF field in those documents that have to be signed.
• A reminder e-mail for e-signing cases where Postident by video chat has not been completed (after 24 hours and 48 hours) will be sent. The e-mail will only be sent when the case is still valid for at least 2 hours.
• Announcement: At the beginning of May the certificate for signing the signing result data will be changed for SFTP transmission.

POSTIDENT Apps

• The android app has been supplemented by our service POSTIDENT by german national identity card. Money Laundering Act compliant identifications using the eID function of the german identity card can now be performed without using a separate card reader. The iOS App will follow as soon as the NFC interface is opened by Apple.
• APP stability on newer iOS hardware has been improved.