The development phase includes technical as well as graphical integration with Signicat’s services.
Graphical profiles are used to customize the user experience of a customer’s application. A graphical profile consists of a collection of files which will be a part of the customer-specific configuration on id.signicat.
A customer may have several brands or applications. In this case it is convenient to establish a different graphical profile for each brand, application or website using id.signicat. It is also possible to have several profiles for the same website, and even share the same profile between several websites.
You can find more information on graphical profiles in our documentation on Graphical adjustments and customization.
Signicat provides authentication capability with a wide range of public and private eIDs in the Nordic region. The service is easily integrated into any website and web application to enable secure login with strong authentication.
For more information on authentication, see our documentation on Getting started with authentication.
Signicat’s signature services are designed for use in web applications covering almost any B2C, B2B and B2E scenario. You may integrate with the signature services using our Sign API, a RESTful web service that can be used to obtain electronic signatures from customers, as well as with our legacy DocumentService SOAP API.
For more information on signing, see our documentation on Getting started with signing.
Customers will normally need test users during the development and test phase. Please see the pages for each ID method for test user information.
During the development phase it is recommended that customers use Signicat test certificates and the public test environment “demo”. Please see our Demo Service page for information on which authentication and signing methods are available in Signicat’s demo service.