DÁP eIdentification
Our completed component receives the identification result and connects it to the service provider’s customer journey. Business checks and data delivery are adapted to the target system.
Contum/
SOLUTION · DÁP INTEGRATION
DÁP eIdentification and eSignature in your own business processes
Our ready-to-integrate DÁP eIdentification component connects to existing enterprise customer journeys. DÁP eSignature integration is in its final development phase.
Obtaining additional customer data
DÁP data may not cover the complete customer due-diligence dataset. We design separate processes for missing information such as an address. KKSZB/SASZ connectivity is subject to appropriate access rights and service conditions.
DÁP eSignature under development
The integration is being developed to transfer documents for signing, initiate the process, receive signed documents and link them to the business case.
Onboarding and authentication
Primary use cases include customer identification, onboarding and service-specific authentication. Strong customer authentication requirements are assessed for each process; a DÁP connection alone does not establish SCA compliance.
NEXT STEP