Configuration
To get and use BankID for test you need to configure the BankID client software for test. Typical errors when this configuration is not done is “Invalid Credentials”, “BankID is missing” or error 10026 when trying to issue a BankID.

Type |
---|
Android/Huawei |
The BankID app is thus configured for the test environment. Please note that the app must be uninstalled/reinstalled to be restored for the production environment. Notes:
|
iOS |
Uninstall any existing version of BankID Security App and then reinstall it from App Store. In Settings → BankID → Developer → Server, enter cavainternal.test.bankid.com. BankID Security App will now connect to the test server. Please note that the app must be uninstalled/reinstalled to be restored for the production environment. |
PCs (Windows and Mac OS X) |
To use the client for test you must configure it for test. If you change configuration your existing BankIDs will be blocked. Follow the backup-restore procedure to avoid that. Start by backing up the production environment
Create a set up for test
Note: Existing production BankIDs will be blocked in the test environment as soon as you start the BankID Application again, so you can just remove them from the BankID Application GUI. Once you restore the production environment, your production BankIDs will be available again. Backup the test environment
Switch between production and test later on
Location of BankID folder
Note that the BankID folder is created the fist time the BankID Application is started, so if you can't find it, please try to start and exit the BankID Application. The Config folder is a subfolder of the BankID folder. IMPORTANT: A BankID enrolled for production can only be used or administered in BankID Application configured for production and a BankID enrolled for test (kundtest) can only be used or administered in BankID Application configured for test. Trying to use or administer a BankID in the BankID Application configured wrong will block the BankID. |
Type
- Uninstall any existing version of the BankID app and then install it again from Google Play Store (Android) or AppGallery (Huawei).
NOTE This step must be performed regardless of which version of the app is installed. - Put the phone in airplane mode.
- Launch the BankID app. Dismiss any network failure warning or similar.
- Go to Settings in the BankID app and select About BankID.
- Make a "long press" (i.e. press and hold) on the heading Error information.
- Enter kundtest in the box that appears and press OK (if no box appears, check again that your device is in airplane mode).
- Without leaving About Bankid, check that it says CUST by version number. This verifies that you entered correctly.
- Exit the BankID app.
- Exit the airplane mode.
- Force quit the BankID app. (It is not enough to put the BankID app in the background. The app must be completely quit in memory. There are several ways to do this depending on the device and operating system.)
The BankID app is thus configured for the test environment. Please note that the app must be uninstalled/reinstalled to be restored for the production environment.
Notes:
- The BankID app cannot be run in emulated environments.
- Apps that create a local (VPN server runs on the phone and the phone connects to it) always turned on VPN connection, have been shown to be able to interfere with the BankID test environment, even in airplane mode.
Uninstall any existing version of BankID Security App and then reinstall it from App Store.
In Settings → BankID → Developer → Server, enter cavainternal.test.bankid.com.
BankID Security App will now connect to the test server. Please note that the app must be uninstalled/reinstalled to be restored for the production environment.
To use the client for test you must configure it for test. If you change configuration your existing BankIDs will be blocked. Follow the backup-restore procedure to avoid that.
Start by backing up the production environment
- Exit the BankID application.
- Open the BankID folder (see below).
- Copy the entire content to a separate location to be able to restore the production configuration later on.
Create a set up for test
- Exit the BankID Application.
- Open the BankID\Config folder, see below.
- Create a plain text file named ”CavaServerSelector.txt”, containing the text ”kundtest”. The content must be plain text and lower case. The file may be created using a text editor, e.g. Notepad (Windows) or Pico in a Terminal window (OS X).
Note: Existing production BankIDs will be blocked in the test environment as soon as you start the BankID Application again, so you can just remove them from the BankID Application GUI. Once you restore the production environment, your production BankIDs will be available again.
Backup the test environment
- Exit the BankID Security Application.
- Open the BankID folder (see below).
- Copy the entire content to a separate location to be able to restore the test configuration later on.
Switch between production and test later on
- Exit the BankID Application.
- Replace the existing BankID folder with the backup copy for the desired environment.
Location of BankID folder
- Windows: %appdata%
- OS X: ~/Library/Application Support
Note that the BankID folder is created the fist time the BankID Application is started, so if you can't find it, please try to start and exit the BankID Application.
The Config folder is a subfolder of the BankID folder.
IMPORTANT: A BankID enrolled for production can only be used or administered in BankID Application configured for production and a BankID enrolled for test (kundtest) can only be used or administered in BankID Application configured for test.
Trying to use or administer a BankID in the BankID Application configured wrong will block the BankID.