FAQ


Find the answers to the most commonly asked questions.

To communicate with BankID’s service, you need to add our CA root certificate in your truststore to trust our server certificate. This certificate is available in “BankID Relying Party Guidelines” on this page. How you do this differs slightly depending on your environment. If this is not done you typically get various SSL/TLS errors.

For authentication to the BankID service, certificate authentication is used and your application need to use a client certificate stored in your keystore. If this is not done you typically get various SSL/TLS errors. This is issued by the same bank you purchased the service from. You don’t need to install additional CA certificates to use the client certificate.

For testing, use the client certificate found on this page.

To use BankID in your service, you need an agreement with one of the banks that sells the BankID service. In addition, you need to make the technical integration of BankID in your service. There is also a test environment that you can use without first signing an agreement.

See the document “How to get a test BankID” on this page.

Testing can not be automated. Passwords/Security codes have to be manually entered in the BankID clients. We recommend building a so-called test stub that simulates the BankID service web service. It can also be used to perform load tests on your services.

If you try to log in or sign in the test environment, but no sign-in or signing dialog appears in the BankID app, it’s probably caused on one of the following:

  • In order for it to work, the BankID app in the phone needs to be configured for testing. See the document “How to get a test BankID” on this page. Note that you must uninstall and reinstall the app to configure it for testing.
  • There must be a test BankID on the phone. See the document “How to get a test BankID” on this page.
  • The call from your service must be made to the https://appapi2.test.bankid.com test environment. If you make a call to the production environment, then the login will never appear in an app configured for testing.
  • The correct certificates to reach the test environment must be installed in your truststore and keystore. Note that there are different certificates for the test and production environments. See also about server certificates above.
  • A useful tip is to test at https://demo.bankid.com and select “Log in with a Test BankID”. If that works your client is correctly configured for test and you have a working test BankID. In this case the problem is likely to be found in your implementation.

We do not provide sample code. We want you to fully understand and take responsibility for the implementation of BankID integration and do not want you to cut and paste code. We have however noted that there is some help and examples to be inspired by on different developer sites.

To make the integration of BankID, you need knowledge and experience on how to secure communication with TLS and how to call web services. In addition, you need general software development knowledge and understand the overall flow, and the various user cases that can be obtained with BankID. See “BankID Relying Party Guidelines” on this page.

We have no capacity to review and troubleshoot third party code. The general principles of integration and methods to be used are described in the “BankID Relying Party Guidelines” on this page.

We have no phone support. To use BankID in your service, you need an agreement with one of the banks that sells the BankID service. In addition, you need to make the technical integration of BankID in your service. There also is a test environment that you can use without first signing an agreement.

Automatic app switching works only with the platform’s embedded browser, i.e. Safari on iOS and Chrome on Android.

On https://www.bankid.com/status, you find information about the status of the services. We also inform about future planned changes that may mean downtime and previous disturbances, on this page. There is also the opportunity to register for a technical newsletter in which we publish important information about the service and future changes.

See the document “Installing BankID Security Application in corporate environments” on https://www.bankid.com/bankid-sakerhetsprogram . Some issues that are covered by this publication are:

  • BankID Security Application in terminal server environments (Citrix, VMWare Horizon).
  • Does BankID for Windows support “Roaming Profiles”?
  • Why do I see error messages about “Communication Error” or “Proxy Error” when I try to use BankID in a corporate environment?
  • Is it possible to turn off automatic update for the BankID application?
  • How should we configure our firewall for the BankID application?

BankID Technical Newsletter


If you have an e-service that uses BankID or will use BankID in the future, you can subscribe to our technical newsletter to keep up to date with the latest news and changes!