Hello Everyone,
I’m currently working on integrating Signicat services into our system and have encountered a few challenges that I’m hoping someone here might be able to assist with.
Our primary goal is to streamline digital identity verification for our users, but we’re facing some roadblocks during implementation. Here’s an overview of what we’re trying to achieve and the issues we’ve run into:
- Integration Process: We’re using Signicat’s API for identity verification. While the documentation is helpful, I’m unclear on how to properly set up and test multiple ID verification methods (e.g., eID and document scanning). Are there best practices for configuring these methods to ensure seamless operation?
- Error Handling: During API calls, we occasionally receive generic error responses without sufficient detail (e.g., HTTP 500). Has anyone encountered this issue, and how did you troubleshoot it?
- Customization: We’d like to customize the UI for the authentication flow to match our brand guidelines. However, I’m unsure how far we can go with Signicat’s customization options. Is there a way to use custom CSS or themes within their SDK?
- Compliance: Since we’re operating in multiple countries, understanding local compliance requirements is critical. Does Signicat offer resources or guidance for ensuring compliance with various regulations (e.g., GDPR, AMLD)?
https://community.signicat.com/t/mitid-can-you-log-in-to-your-netbank-with-nemid-after-migration/msbi
If anyone has experience addressing similar challenges or has tips to share, I’d greatly appreciate your insights. Additionally, if there are specific support channels or community resources I should explore, please let me know.
Thank you in advance for your time and help.
Hi Harry,
- To best test Signicat products we would like to refeere to our dashboard (dashboard.signicat.com). You can create an organization with different production and sandbox accounts to test most of our product. You can further create an API account with the Assure API permissions to test out our different eID and document scanning providers. These processes would best be tested using postman and using the dashboard would be the best way of setting up towards Signicat to get the access you need.
- We do have some troubleshooting info for the HTTP 400 range in our API reference. But for HTTP 500, Internal Server Error is a general error message indicating that the server encountered an unexpected condition that prevented it from fulfilling a request. It does not specify the exact problem, which can be caused by various issues on the server side.
- We offer some customization via our theming function in the dashboard and we are expanding on this going into 2025, we have some cool stuff down the line to keep branding intact for our customers. We also have parts that we are unable to provide any kind of branding to, such as the third party suppliers and eIDs.
- Signicat is operating on an international level and is compliant with GDPR and other directives from the EU. We have some information about compliance here: Security & Compliance - Signicat and we are also handling other directives such as Digital Operational Resilience Act (DORA).
For additional resources or if you have a specific flow or use-case you are interested in, you could reach out to our sales-team. We have an excellent pre-sales team who can understand and uncover both technical and commercial needs. It can be quite a lot of information to take in and if you are unfamiliar with the solutions already out there, a chat might be the best way of spearheading your efforts.
(I somewhat assume they are on holiday, so not sure when they are available to reach out)