This section contains several guides, such as:
- A technical guide for integration for Relying Parties.
- Best practises with user cases and examples.
- Rules for how our brand can be used.
The RP guideline - A complete guide for integrating BankID in your services.
Step-by-step guides and prototypes for the most common user flows.
How to format signature texts.
Follow our step-by-step guide to create your RP certificate.
How you may use our logotype and work mark.
We have no capacity to review and troubleshoot third party code. The general principles of integration and methods to be used are described in our guides.
We do provide some examples of code in our integration guide
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. Please use our guides.
You find the service status on the top right side of the webbsite. If you click that information field you will land on a page with more information, such as previous, ongoing and planned downtime.
You can also sign up for our technical newsletter to get tips and information about the service and changes made.
Here you find more information about the Enterprise version.
To communicate with BankID's service, you need to add our CA root certificate in your truststore to trust our server certificate. 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, read more here.
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.
This works only with the platform's embedded browser, i.e. Safari on iOS and Chrome on Android.
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. Here are some useful links:
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 by one of the following:
- The BankID app in the phone needs to be configured for testing. Note that you must uninstall and reinstall the app to configure it for testing. Read more here.
- There must be a test BankID on the phone. Read more here.
- 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.