# Demo service
Signicat provides a service called demo
. This is intended for demo and testing purposes while you await your own customer-specific service. Once you have signed a contract with Signicat, you and your company will get your own service that you should use for all testing purposes.
Details for Signicat's demo service are as follows:
- Servicename:
demo
- WS Password:
Bond007
- Test users: See separate pages for each ID method.
This page lists details on methods for authentication and signing that are available in Signicat's demo service. For more help and guidelines, please visit Getting started with authentication and Getting started with Signicat Sign to learn more about how services are utilized.
Page contents
# OIDC considerations
We have set up a demo-preprod
client to be used when OpenID Connect is utilized as the authentication protocol. For this client, the scope profile
is available for all ID methods. Other scopes may be available depending on the ID method used.
When calling the OIDC endpoint, you will need to submit the client secret for the demo-preprod
client. Here are the details for Signicat's two pre-production environments (Nordics and Europe):
Market | Base URL | Environment | Service | Client ID | Client secret |
---|---|---|---|---|---|
Nordics | https://preprod.signicat.com/ | preproduction | demo | demo-preprod | Download demo JSON web key (demo-preprod-jwk.zip) |
Europe | https://eu01.preprod.signicat.com/ | preproduction | demo | demo-preprod-basic | Download demo JSON web key (demo-preprod-basic-jwk.zip) |
The OIDC server will redirect the user to a redirect URI once the user has finished authenticating and authorizing the access for your client. The following redirect URIs are pre-configured and may be used:
https://localhost:8080/redirect
https://localhost:5000/redirect
https://localhost/redirect
http://localhost/redirect
Contact Signicat at support@signicat.com to set up an additional redirect URI for use.
# List of scope and claims available if supported by the ID method in question
Scope | Claims |
---|---|
profile | website zoneinfo birthdate gender profile preferred_username given_name middle_name locale picture updated_at name nickname family_name |
signicat.national_id | signicat.national_id |
address | address |
email | email_verified , email |
phone | phone_number_verified , phone_number |
signicat.certificate | signicat.certificate signicat.certificate_bank signicat.certificate_not_after signicat.certificate_issuer_dn signicat.certificate_not_before signicat.certificate_dn |
signicat.paper | paper.issuedate paper.expirydate paper.document_number paper.nationality paper.document_type |
# Authentication methods
Country | ID name | Method names |
---|---|---|
Global | Facebook, Google, Live or LinkedIn | social |
Global | SMS OTP | scid-sms scid-sms-form |
Global | Email OTP | scid-email |
Global | Paper Verify | scid-passport-otp scid-proofid-2selfiesplusidcard scid-proofid-2selfiespluspassport scid-proofid-3ptyID-trapets scid-proofid-dl-mitek scid-proofid-idpapers scid-proofid-idpapers-test scid-proofid-passport scid-proofid-passport-mitek scid-proofid-passport-seal scid-proofid-selfiepluspassport-seal signicat-paper |
Baltics | Smart-ID | smartid |
Belgium | itsme Register | itsme-register |
Belgium | itsme Login | itsme-login |
Belgium | .beID | beid-authentication |
Denmark | NemID key card (bank stored certificate, employee and person signature) | nemid |
Denmark | NemID key card (bank stored certificate, employee signature only) | nemid-moces |
Denmark | NemID key card (bank stored certificate for business owners) | nemid-erhverv |
Denmark | NemID code file (locally stored employee certificate) | nemid-codefile |
Estonia | EstEID | esteid |
Estonia | EstEID Mobile | esteid-mobil |
Finland | FTN | ftn |
Finland | Mobiilivarmenne | mobiilivarmenne |
Germany | Personalausweis (nPA) | npa-login npa-ident |
Germany | Verimi | verimi |
Germany | Video Assurance (coming soon) | |
Germany | yes® | yes |
Netherlands | iDIN | idin idin-ident idin-login idin-age |
Norway | Norwegian BankID | nbid |
Norway | Norwegian BankID on mobile | nbid-mobil |
Norway | Norwegian BankID with Bisnode lookup | nbid-bisnode |
Norway | Norwegian BankID on mobile with Bisnode lookup | nbid-mobil-bisnode |
Norway | Norwegian BankID without national identity number | nbid-nossn |
Norway | Norwegian BankID on mobile without national identity number | nbid-mobil-nossn |
Norway | Buypass | buypass |
Norway | Commfides | commfides |
Netherlands | iDIN | idin |
Spain | DNI electrónico | dnie |
Sweden | Swedish BankID | sbid |
Sweden | Swedish BankID with QR code scan | sbid-qr |
Sweden | Telia e-leg | telia |
Global | Freja eID Basic | freja-basic |
Sweden | Freja eID+ | freja-plus |
Sweden, Norway, Denmark, UK | Freja eID Extended | freja-extended-email freja-extended-phone freja-extended-se freja-extended-no freja-extended-dk |
# Authentication-based signing methods
Refer to our electronic signing documentation for more information on authentication-based signing.
Country | ID name | Method name | Result output format | Text | PAdES | |
---|---|---|---|---|---|---|
Global | Facebook, Google, Live or LinkedIn | social | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ |
Global | SMS | scid-sms scid-sms-form | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ |
Global | scid-email | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ | |
Global | Handwritten | N/A | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ |
Belgium | itsme | itsme-approval | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ |
Denmark | NemID keycard | nemid | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ |
Denmark | NemID on file | nemid-codefile | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ |
Estonia | EstEID | esteid | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ |
Estonia | EstEID Mobile | esteid-mobil | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ |
Finland | FTN | ftn-sign | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ |
Finland | Mobiilivarmenne | mobiilivarmenne | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ |
Germany | Personalausweis (nPA) | npa-login npa-ident | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ |
Germany | Verimi | verimi | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ |
Germany | Yes® | Yes | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ |
Netherlands | iDIN | idin | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ |
Norway | Norwegian BankID | nbid | LTV-SDO | No ❌ | No ❌ | No ❌ |
Norway | Norwegian BankID on mobile | nbid-mobil | LTV-SDO | No ❌ | No ❌ | No ❌ |
Norway | Buypass | buypass | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ |
Norway | Commfides | commfides | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ |
Spain | DNI electrónico | dnie | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ |
Sweden | Swedish BankID | sbid | LTV-SDO | No ❌ | No ❌ | No ❌ |
Sweden | Swedish BankID with QR code scan | sbid-qr | LTV-SDO | No ❌ | No ❌ | No ❌ |
Note
- PAdES (PDF Advanced Electronic Signatures) requires Signicat's PackagingService API (packaging method
pades
andltvsdo-validator
as validation method). PAdES does not support text. - LTV-SDO stands for long-term validation signed data object. For more information, see our documentation on long-term validation of documents or view an LTV-SDO XML example file.
- Refer to our overview of ID methods for more information on the individual methods for authentication and signing.
# Third-party (native) signing methods
Refer to our electronic signing documentation for more information on third-party (native) signing.
Country | ID name | Method name | Result output format | Text | PAdES | Other | |
---|---|---|---|---|---|---|---|
Global | Swisscom AIS | swisscom swisscom-pades | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ | |
Belgium | .beID | beid-signature | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ | |
Denmark | NemID keycard | nemid-sign | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ | |
Denmark | NemID on file | nemid-codefile-sign | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ | |
Estonia | EstEID | esteid-sign | bDoc | No ❌ | Yes ✔️ | No ❌ | |
Norway | Norwegian BankID | nbid-sign | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ | |
Norway | Norwegian BankID mobile | nbid-mobil-sign | SEID-SDO (text/plain) LTV-SDO (pdf) | Yes ✔️ | Yes ✔️ | Yes ✔️ | PDF and PAdES require Signed Statement. |
Norway | Buypass | buypass-sign | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ | |
Norway | Commfides | commfides-sign | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ | |
Sweden | Swedish BankID | sbid-sign | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ | |
Sweden | Swedish BankID with QR code scan | sbid-qr-sign | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ | |
Global | Freja eID Basic | freja-email-sign freja-phone-sign | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ | |
Sweden | Freja eID+ | freja-plus-se-sign | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ | |
Sweden, Norway, Denmark, UK | Freja eID Extended | freja-extended-no-sign freja-extended-se-sign freja-extended-dk-sign freja-extended-email-sign freja-extended-phone-sign | LTV-SDO | Yes ✔️ | Yes ✔️ | Yes ✔️ |
Note
- PAdES (PDF Advanced Electronic Signatures) requires Signicat's PackagingService API (packaging method
pades
andltvsdo-validator
as validation method). PAdES does not support text. - LTV-SDO stands for long-term validation signed data object. For more information, see our documentation on long-term validation of documents or view an LTV-SDO XML example file.
- Refer to our overview of ID methods for more information on the individual methods for authentication and signing.
# Assure
Credentials:
- Client ID:
assure-api-test-client
- Secret:
jfKBjVz-hclajTP9sBlO2sg4XZO1lwiQzxu6WcGUxr8
- Endpoint:
https://preprod.signicat.com/
Important
Since this is a non-production environment, you should not use real ID documents when testing. This is a shared service, so other people can look into any dossier or process using these credentials.
Refer to our Identity verification documentation for details on identity verification with Signicat Assure.
# Sign API
Credentials:
- Client ID:
demo-preprod
- Secret:
mqZ-_75-f2wNsiQTONb7On4aAZ7zc218mrRVk1oufa8
- Scope:
client.signature
- Endpoint:
https://preprod.signicat.com/
Refer to our documentation on how to use our Sign API, which is a RESTful web service that serves as Signicat's single integration point for electronic signatures and all underlying methods.
# Portals
Signicat's ID portal might be used when the user has to choose between two or more methods.
Name | Description |
---|---|
auth-portal | Lists all authentication methods |
# Graphical profiles
Profile | Description |
---|---|
demo | Default layout |
background | Default layout with background |
iframe | Minimal styling |
# Packaging methods
Method name | Supported signatures |
---|---|
pades | Infinite, includes a signature page at the end |
pades-multi | Infinite |
# Supported URL parameters
Using URL parameters might ease a process or disable one step for the end-user.
Important
Different ID methods may handle the prefilling of national identification numbers differently.
ID method | Parameter | Input | Example*** |
---|---|---|---|
Norwegian BankID | prefilled.subject | national identification number | &prefilled.subject=05054512345 |
Norwegian BankID on mobile | prefilled.subject | Mobile number:date of birth | &prefilled.subject=11223344:050545 |
Norwegian BankID on mobile (BankID version 2.0)* | prefilled.subject prefilled.phone | national identification number Mobile number | &prefilled.subject=05054512345 &prefilled.phone=11223344 |
Swedish BankID | prefilled.subject | national identification number | &prefilled.subject=194505051234 |
Freja eID Basic | prefilled.subject | &prefilled.subject=carl@example.com | |
Freja eID+ | prefilled.subject | national identification number | &prefilled.subject=194505051234 |
NemID | prefilled.subject prefilled.mode | national identification number Client mode: Standard or limited | &prefilled.subject=0505451234 &prefilled.mode=limited &prefilled.mode=standard |
SMS OTP | prefilled.authType prefilled.deviceId | SMS Mobile number | &prefilled.authType=sms &prefilled.deviceId=+4711223344 |
Email OTP | prefilled.authType **prefilled.deviceId | email email address | &prefilled.authType=email &prefilled.deviceId=test@test.com |
*) Also accepts the legacy format (mobile:date of birth
) for backwards compatibility.
**) This parameter is mandatory if prefilled.deviceId
is used.
***) Value needs to be URL-encoded.
Note
Contact Signicat at support@signicat.com to find out which tags apply to your service.