Error codes#
On this page
This page contains an overview of possible error codes that may be displayed to end-users during usage of the BankID OpenID Connect provider. The document is intended for the development and support organizations of banks and merchants helping to deal with customer incidents.
OIDC errors#
| Code | Category | Description | Action/solution |
|---|---|---|---|
| 4096 | Generic error | Unexpected script error | Contact BankID support. |
| 4100 | Generic error | Method selected, but the IDP argument is missing | Contact BankID support. |
| 4101 | Generic error | Failed to get session when handling error from IDP during initialization | Contact BankID support. |
| 1200 | Generic error | BID helper did not load | Problem loading BankID client. Contact BankID support. |
| 1201 | Generic error | BID callback gave error | Problem with BankID client. Contact BankID support. |
| 1202 | Generic error | BID callback missing result | Problem with BankID client. Contact BankID support. |
| 1203 | Generic error | BID callback status error | Problem with BankID client. Contact BankID support. |
| 1204 | Generic error | BID helper did not load within a reasonable time | Problem with BankID client. Contact BankID support. |
| 1205 | Generic error | BID helper url missing | Problem with BankID client. Contact BankID support. |
| 14003 | API error | Composite-idp could not communicate with SDM server | Problem with BankID client. Contact BankID support. |
| 4096 | Cookie error | Generic error | Contact BankID support. |
| 4097 | Cookie error | Could not open set cookie window from iframe | Contact BankID support. |
| 4098 | Cookie error | Could not set cookie in set cookie window | Contact BankID support. |
| 4099 | Cookie error | Sending event log took to long (never sent to server) | Contact BankID support. |
| 4100 | Cookie error | User exists client without finishing session | Contact BankID support. |
| 4101 | Cookie error | Set Cookie Window is opened and it's not in correct state | Contact BankID support. |
| Code | Category | Description | Action/solution |
|---|---|---|---|
| D010 | Generic error | Likely communication error | Contact BankID support. |
| D011 | Generic error | Likely communication error | Problem connecting to identity provider. Try another authentication method or contact BankID support. |
| D108 | Generic error | Likely communication error | Contact BankID support. |
| D112 | Generic error | Generic IDP request returned error | Problem connecting to identity provider. Try another authentication method or contact BankID support. |
| D103 | API error | Likely communication error | Problem with user session. Contact BankID support. |
| D105 | API error | Likely communication error | Problem with BankID. Contact BankID support. |
| D107 | API error | Likely communication error | Problem with BankID. Contact BankID support. |
| D002 | Communication error | Likely communication error | Network error. Try again later or contact BankID support if the problem persists. |
| D007 | Communication error | Likely communication error | Network error. Try again later or contact BankID support if the problem persists. |
| D008 | Communication error | Likely communication error | Network error. Try again later or contact BankID support if the problem persists. |
| D009 | Communication error | Likely communication error | Network error. Try again later or contact BankID support if the problem persists. |
| D000 | Unrecoverable error | No legal action provided. | Contact BankID support. |
| D001 | Unrecoverable error (skip) | Session could not be found. | Problem with authentication session. Session aborted. |
| D300 | Unrecoverable error (skip) | No sid provided. | Session not found. |
BankID errors#
| Code | Category | Description | Action/solution |
|---|---|---|---|
| BID-1001 | Generic error | Invalid tag parameter. | Verify the contents of the Applet Tag. |
| BID-1002 | Generic error | Error with unidentified source or cause. | Try again. Contact BankID support in case of repeating errors. |
| BID-1003 | Generic error | Incorrect Action in Applet Tag. | Verify the contents of the Applet Tag. |
| BID-1007 | Generic error | Could not fetch crypto library. | Error in client. Contact BankID support. |
| BID-1009 | Generic error | Error in communication with Archive. | Verify the URL of the user's archive service. |
| BID-101A | Generic error | MimeType is incorrect. | Incorrect data format sent to the client (MimeType). Error in the merchant implementation. |
| BID-101B | Generic error | Invalid URL. | MerchantURL in TAG is not a valid URL. |
| BID-1016 | Generic error | Could not perform DNS-lookup of merchant URL from the end-user's device. | Ask the user to test her BankID from the device in question at BankID's website: https://bankid.no/hjelp/testverktoey (opens in a new tab) If this test succeeds, investigate the merchant implementation. If this test fails, it is an indication that the end-user's device or network are not set up correctly in order to perform DNS-lookup. Report any continuous errors to BankID support. |
| BID-1017 | Generic error | The merchant's IP-address does not match the provided IP-address. | Ask the user to test her BankID from the device in question at BankID's website: https://bankid.no/hjelp/testverktoey (opens in a new tab) If this test succeeds, investigate the merchant implementation. If this test fails, consider further investigation according to the error message. Report any continuous errors to BankID support. |
| BID-1018 | Generic error | The hostname of the merchant URL (URL in Applet Tag) does not match with the web address from the BankID Server configuration. | Investigate the merchant implementation. |
| BID-1019 | Generic error | ServerURL received by client does not match any of the approved URLs. | Contact BankID support. |
| BID-1020 | Generic error | The carrier field in the Applet Tag is incorrect. | Investigate the merchant implementation. |
| BID-1021 | Generic error | Validation of the SDO failed. The merchant generates an invalid SDO (missing or incorrect data). | Merchant needs to investigate and resolve the error situation. |
| BID-1022 | Generic error | The version of BankID Server is obsolete. | The BankID Server version that was used is older than the required minimum version. The minimum version is 3.1.0.0. |
| BID-1031 | Generic error | Generic communication error between client and Merchant/COI. | Try again, if the error persists, contact the bank/Merchant. |
| BID-1032 | Generic error | Error in PDF received from Merchant (not BankID 2.1). | Contact Merchant in order to validate the PDF document. |
| BID-1101 | BankID Client Error | The client is missing data in order to process the request (serverURL in Applet Tag missing). | Verify that the script that calls the client is sending the correct parameters (Applet Tag has to contain serverURL). |
| BID-1109 | BankID Client Error | The client could not find the Merchant certificate. | Verify that the correct certificate is sent to the client and that the certificate has not been revoked and has not expired. |
| BID-1118 | BankID Client Error | Communication problem towards COI. | Contact BankID support. For a single user: Ask user to try another internet connection with better capacity or try to shorten the distance to Wi-Fi router. |
| BID-1119 | BankID Client Error | Expected response from COI timed out. | Close all browsers and try again in 10 minutes. |
| BID-1204 | BankID Client Error | COI did not receive any valid parameters. | Contact BankID support. |
| BID-1216 | BankID Client Error | Invalid client version. | Update the BankID client to the latest version. |
| BID-1297 | BankID Client Error | BankID protocol violation: Received client request is missing mandatory parameters. | Should not happen with valid client. Ask the end-user to try again. |
| BID-1299 | BankID Client Error | An incorrect client version is being used. | For net centric BankID: Delete cache (temporary files) on the device. Start the web browser again. If error still present, contact the local system administrator. For locally stored BankID: Update to the latest release. |
| BID-1308 | BankID Client Error | The new password has to be different from the old one. | Ask user to choose a new password different from current password. |
| BID-138E | BankID Client Error | Banklagret COI reports internal timeout. | Try again, if the error persists, contact BankID support. |
| BID-1313 | BankID Client Error | The certificate has expired. | A new BankID has to be ordered as the BankID can no longer be renewed. |
| BID-1321 | BankID Client Error | The Merchant has used the signing certificate for authorization or vice versa. | Investigate the merchant implementation. |
| BID-1334 | BankID Client Error | The merchant certificate is invalid. It could have expired. | The bank needs to check the order date of the certificate. |
| BID-1350 | BankID Client Error | Validation of SDO failed. Merchant has generated an invalid SDO. | Error could be due to incorrect or missing data. Investigate the merchant implementation. |
| BID-1356 | BankID Client Error | Timeout towards VA. | Contact BankID support. |
| BID-136C | BankID Client Error | The certificate status has been revoked. | The certificate has been revoked, please contact the bank that issued the BankID to have a new certificate issued. |
| BID-1402 | BankID Client Error | Banklagret COI reports internal error. | Try again, if the error persists, contact BankID support. |
| BID-1403 | BankID Client Error | The usage of your security element has failed too many times. The security element has been blocked. | Please contact the bank that issued the BankID. |
| BID-1406 | BankID Client Error | Incorrect data entered. | Please try again. |
| BID-1407 | BankID Client Error | An error has occurred with the bank's OTP-service. | Check the status of the bank's own OTP-service. |
| BID-1409 | BankID Client Error | The time it took to complete the transaction was too long. | Complete the transaction without any delays. |
| BID-1412 | BankID Client Error | Internal error – requires investigation by BankID support. | Contact BankID support. |
| BID-1439 | BankID Client Error | BankID has been blocked. | This can happen if end-user has entered the wrong one-time code too many times. Users need to contact the bank to have their BankID opened again. |
| BID-14B1 | BankID Client Error | The identification has expired. | Try again and look for a notification from BankID on your phone, or open the app to confirm the request. Alternatively, you can try logging in with a one-time code device. |
| BID-14C0 | BankID Client Error | Cannot connect with BankID app | Try again, or try logging in with a one-time code device. If the error persists, contact BankID support. |
| BID-14D1 | BankID Client Error | User session not found. | Try again. If the error persists, contact BankID support. |
| BID-2002 | BankID Client Error | An unexpected error occurred. | Try again, if the error persists, contact BankID support. |
| BID-2002 | BankID Client error | An unexpected error occurred. | Try again, if the error persists, contact BankID support. |
| BID-2008 | BankID Client error | The URL does not use HTTPS. | Merchant must use URLs with HTTPS. |
| BID-2011 | BankID Client error | Error in initAuth() response from Merchant. | Merchant needs to investigate. |
| BID-2012 | BankID Client error | Error in initSign() response from Merchant. | Merchant needs to investigate. |
| BID-2013 | BankID Client error | Error in verifyAuth() response from Merchant. | Merchant needs to investigate. |
| BID-2014 | BankID Client error | Error in verifySign() response from Merchant. | Merchant needs to investigate. |
| BID-2015 | BankID Client error | Error in handleError() response from Merchant. | Merchant needs to investigate. |
| BID-2016 | BankID Client error | Error during decoding of data. | Make sure the end-user uses the correct encoding. |
| BID-2017 | BankID Client error | extPDFDomain and domain in extPDFURL do not match, or extPDFURL does not use HTTPS. | Merchant needs to investigate. |
| BID-2018 | BankID Client error | Error during initialization of Web-client. | Could be due to slow network connection, slow device, or incorrect configuration of Merchant site. |
| BID-2030 | BankID Client error | Communication error towards Merchant or COI. | Try again, if the error persists, contact BankID support. |
| BID-2031 | BankID Client error | Communication error towards Merchant or COI. | Try again, if the error persists, contact BankID support. |
| BID-2032 | BankID Client error | Communication error towards Merchant or COI. | Try again, if the error persists, contact BankID support. |
| BID-2033 | BankID Client error | Communication error towards Merchant or COI. | Try again, if the error persists, contact BankID support. |
| BID-2034 | BankID Client error | Communication timed out. | Try again, if the error persists, contact BankID support. (BankID 2.0) |
| BID-2035 | BankID Client error | Communication was aborted. | Try again. If the error persists, contact BankID support. (BankID 2.0) |
| BID-2056 | BankID Client error | Communication error. | Try again, if the error persists, contact BankID support. |
| BID-20A1 | Communication error | Communication timeout towards Merchant. (BankID 2.1) | Try again, if the error persists, verify the merchantURL or contact BankID support. |
| BID-20A2 | Communication error | Communication towards Merchant was aborted. (BankID 2.1) | Try again, if the error persists, verify the merchantURL or contact BankID support. |
| BID-20B0 | Communication error | Communication error towards COI. (BankID 2.1) | Try again, if the error persists, contact BankID support. |
| BID-20B1 | Communication error | Communication timeout towards COI. (BankID 2.1) | Try again, if the error persists, contact BankID support. |
| BID-20B2 | Communication error | Communication towards COI was aborted. (BankID 2.1) | Try again, if the error persists, contact BankID support. |
| BID-20C0 | Communication error | Error received from Client proxy. (BankID 2.1) | Try again, if the error persists, verify the clientProxyURL or contact BankID support. |
| BID-20C1 | Communication error | Communication error towards Client proxy. (BankID 2.1) | Try again, if the error persists, verify the clientProxyURL or contact BankID support. Make sure that the client is able to resolve the clientProxyURL. |
| BID-20C2 | Communication error | Client proxy detected error(s) in document to be signed. (BankID 2.1) | Try again, if the error persists, contact BankID support or the party hosting the Client proxy URL being used. |
| BID-20C4 | Communication error | Communication timeout towards Client proxy. (BankID 2.1) | Try again, if the error persists, verify the clientProxyURL or contact BankID support. |
| BID-20C5 | Communication error | Communication towards Client proxy was aborted. (BankID 2.1) | Try again, if the error persists, contact BankID support or the party hosting the Client proxy URL being used. |
| BID-2901 | BankID Helper error | Missing config parameter. | Error in Helper configuration. |
| BID-2902 | BankID Helper error | Missing client container. | Error in Helper setup. |
| BID-2903 | BankID Helper error | Unknown frame mode. | Error in Helper configuration. |
| BID-2904 | BankID Helper error | Browser not supported. | Upgrade browser. |
| BID-2905 | BankID Helper error | Helper could not connect to Client after some time. | Try again, if the error persists, contact BankID support. |
| BID-2906 | BankID Helper error | Bootloader error. | Try again, if the error persists, contact BankID support. |
| BID-2907 | BankID Helper error | XDM origin error. | Error in Helper configuration. |
| BID-2908 | BankID Helper error | Unexpected error. | Try again, if the error persists, contact BankID support. |
| BID-5000 | Communication error | Communication error towards Merchant. | Possible causes: - Web-client not able to connect to Merchant. - Hostname verification fails. |
| BID-5001 | Communication error | Client communication towards Merchant timed out. Occurs if it takes too long before the client receives a response from Merchant. | Try again. If the error persists, contact Merchant. |
| BID-5002 | Communication error | Merchant connection established, unknown error. | The Applet isn't able to interpret the response from Merchant. |
| BID-5003 | Communication error | Incorrect format of parameters, or missing/unexpected parameters have been transferred between client and Merchant. The two parties are not in sync. | Error at Merchant. Verify that the data protocol for direct communication is followed. |
| BID-5004 | Communication error | Internal error. requires investigation by BankID support. | Contact BankID support. |
| BID-5005 | Communication error | BSS Channel error. | Contact BankID support. |
| BID-5006 | Communication error | BIDXML Transformation error. | Contact BankID support. |
| BID-5007 | Communication error | The client has received an error code from Merchant. | Contact Merchant to check the Merchant error logs for the real error code. The error may have a cause which is not desirable to reveal to an end-user. |
| BID-5008 | Communication error | The URL does not use HTTPS. | The URL which the net centric client uses to contact Merchant must use SSL (https://...). |
| BID-500A | Communication error | The client has received an invalid response from Merchant. | Investigate Merchant implementation. |
| BID-500D | Communication error | Hostname verification fails. The hostname in the SSL certificate does not match the hostname of the host machine the net centric client tried to connect to. | Contact bank or Merchant and refer to error code: BID-500D. This error usually occurs in conjunction with SSL certificate updates. |
| BID-5010 | Communication error | Not possible to navigate to NextURL. | Verify the nextURL in Tag/response to Applet. |
| BID-5011 | Communication error | Invalid initAuth() response. | The Applet is not able to interpret the initAuth() response from Merchant. |
| BID-5012 | Communication error | Invalid initSign() response. | The Applet is not able to interpret the initSign() response from Merchant. |
| BID-5013 | Communication error | Invalid verifyAuth() response. | The Applet is not able to interpret the verifyAuth() response from Merchant. |
| BID-5014 | Communication error | Invalid verifySign() response. | The Applet is not able to interpret the verifySign() response from Merchant. |
| BID-9001 | Transaction error | The user chose to abort the identification/signing transaction by clicking Cancel in the client dialog. | Inform that the abortion was due to a user action and that there are no errors with the system. The user may start over again. |
| BID-9314 | Transaction error | The certificate is suspended. The password has been incorrectly entered too many times (5). | Please contact the Issuer of the BankID. |
| BID-9403 | Transaction error | The OTP is suspended. The security code/one-time-password has been incorrectly entered too many times (5). | Please contact the Issuer of the BankID. |
| BID-9407 | Transaction error | The bank's OTP service aborted the process. An error message has been shown to the user. | Possible causes may be listed in the bank's internal documentation, alternatively in the documentation provided by the OTP service vendor. Ask questions about the error message. Validate against the relevant error message lists. |
| BID-9409 | Transaction error | The client session timed out. | Ask the user to start over again. |
| BID-9419 | Transaction error | Signing aborted due to changes in contents. | Could be that the client has manipulated the end-user web browser. |
| BID-9439 | Transaction error | The end-user has entered an incorrect one-time-password from an unknown device too many times. | The end-user has to try again from a device previously known by the BankID environment or contact the bank to have the block lifted. |
| BID-9458 | Transaction error | The end-user does not have the certificate type (PersonalBankID or EmployeeBankID) which is required by the Merchant. | The end-user must obtain the correct BankID in order to use the service. |
BankID signing errors#
| Code | Category | Description | Action/solution |
|---|---|---|---|
| S100 | Signing Error | Cannot start signing, order not found | Cannot find signing order. Make sure that documents are uploaded and signing order is embedded with the authentication request. |
| BID-186A0 | Signing Error | Unspecified error from Client proxy. | Try again. If the error persists, contact BankID support and refer to error code: BID-186A0 |
| BID-18768 | Signing Error | OK (will only be returned to Merchant, not shown to user). | N/A |
| BID-187CC | Signing Error | Redirection. | Try again. If the error persists, contact BankID support and refer to error code: BID-187CC |
| BID-18830 | Signing Error | Bad Request. | Verify Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-18830 |
| BID-18833 | Signing Error | Forbidden. | Try again. If the error persists, contact BankID support and refer to error code: BID-18833 |
| BID-18834 | Signing Error | Not found. | Try again. If the error persists, contact BankID support and refer to error code: BID-18834 |
| BID-18894 | Signing Error | Internal server error. | Try again. If the error persists, contact BankID support and refer to error code: BID-18894 |
| BID-188F8 | Signing Error | Bad input. | Verify Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-188F8 |
| BID-188F9 | Signing Error | The encAuth received from client does not match the calculated one. | Verify Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-188F9 |
| BID-188FA | Signing Error | Invalid trace id. | Verify Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-188FA |
| BID-188FB | Signing Error | No documents to be signed. | Verify Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-188FB |
| BID-188FC | Signing Error | Error communicating with merchant. | Try again. If the error persists, contact BankID support and refer to error code: BID-188FC |
| BID-188FD | Signing Error | TraceID not specified. | Verify Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-188FD |
| BID-188FE | Signing Error | TraceID already exists. | Verify Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-188FE |
| BID-188FF | Signing Error | Operation not supported. | Verify Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-188FF |
| BID-18900 | Signing Error | Empty merchant key. | Verify Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-18900 |
| BID-18901 | Signing Error | Empty merchant URL. | Verify Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-18901 |
| BID-18902 | Signing Error | Empty session ID. | Verify Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-18902 |
| BID-18905 | Signing Error | Document id not specified. | Try again. If the error persists, contact BankID support and refer to error code: BID-18905 |
| BID-18906 | Signing Error | Document page id not specified. | Try again. If the error persists, contact BankID support and refer to error code: BID-18906 |
| BID-18907 | Signing Error | Document parser error. Document validation message (will only be returned to Merchant, not shown to user). | Merchant should investigate. |
| BID-18908 | Signing Error | MimeType not supported. | Verify Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-18908 |
| BID-18909 | Signing Error | MimeType does not match document type. | Verify Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-18909 |
| BID-1890A | Signing Error | Document is not downloadable. | Try again. If the error persists, contact BankID support and refer to error code: BID-1890A |
| BID-1890B | Signing Error | Unsupported encoding. Document validation message. | Merchant should investigate. |
| BID-1890C | Signing Error | Missing argument (e.g. operation, merchantKey, merchantURL etc.). | Verify Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-1890C |
| BID-1890D | Signing Error | Error building client response. | Verify Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-1890D |
| BID-1890E | Signing Error | Generic encryption/decryption error. | Try again. If the error persists, contact BankID support and refer to error code: BID-1890E |
| BID-1890F | Signing Error | Decryption of request failed. | Try again. If the error persists, contact BankID support and refer to error code: BID-1890F |
| BID-18910 | Signing Error | Received empty response from merchant. | Verify Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-18910 |
| BID-1895C | Signing Error | Could not convert PDF to BufferedImage. | Try again. If the error persists, contact BankID support and refer to error code: BID-1895C |
| BID-1895D | Signing Error | Could not convert BufferedImage to PNG. | Try again. If the error persists, contact BankID support and refer to error code: BID-1895D |
| BID-1895E | Signing Error | Could not decode HTML to Latin1. | Try again. If the error persists, contact BankID support and refer to error code: BID-1895E |
| BID-1895F | Signing Error | Could not decode BIDXML to Latin1. | Try again. If the error persists, contact BankID support and refer to error code: BID-1895F |
| BID-18960 | Signing Error | Could not split BIDXML to XML/XSLT. | Try again. If the error persists, contact BankID support and refer to error code: BID-18960 |
| BID-18961 | Signing Error | Could not decode txt document to Latin1. | Try again. If the error persists, contact BankID support and refer to error code: BID-18961 |
| BID-18962 | Signing Error | Could not convert PDF. | Try again. If the error persists, contact BankID support and refer to error code: BID-18962 |
| BID-18963 | Signing Error | PDF-Validator could not read document | Try again. If the error persists, contact BankID support and refer to error code: BID-18963 |
| BID-18964 | Signing Error | Document is password protected | Try again. If the error persists, contact BankID support and refer to error code: BID-18964 |
| BID-18965 | Signing Error | Document is corrupt | Try again. If the error persists, contact BankID support and refer to error code: BID-18965 |
| BID-18966 | Signing Error | Error converting signed page. The specified PDF page is out of bounds | Try again. If the error persists, contact BankID support and refer to error code: BID-18966 |
| BID-189C0 | Signing Error | PE_BIMG_TO_PNG. | Logged performance event when converting a document. Available to merchant in cpReport, will not be displayed in the Web-client. |
| BID-189C1 | Signing Error | PE_PDF_TO_BIMG. | Logged performance event when converting a document. Available to merchant in cpReport, will not be displayed in the Web-client. |
| BID-189C2 | Signing Error | PE_PDF_VALIDATOR. | Logged performance event when converting a document. Available to merchant in cpReport, will not be displayed in the Web-client. |
| BID-189C3 | Signing Error | PE_HTML_WASHER. | Logged performance event when converting a document. Available to merchant in cpReport, will not be displayed in the Web-client. |
| BID-189C4 | Signing Error | PE_TXT_WASHER. | Logged performance event when converting a document. Available to merchant in cpReport, will not be displayed in the Web-client. |
| BID-189C5 | Signing Error | PE_XML_CONVERTER. | Logged performance event when converting a document. Available to merchant in cpReport, will not be displayed in the Web-client. |
| BID-189C6 | Signing Error | PE_REQUEST_DECRYPT. | Logged performance event when converting a document. Available to merchant in cpReport, will not be displayed in the Web-client. |
| BID-189C7 | Signing Error | PE_MERCHANT_REQUEST. | Logged performance event when converting a document. Available to merchant in cpReport, will not be displayed in the Web-client. |
| BID-189C8 | Signing Error | PE_DOCUMENT_PREPARATION. | Logged performance event when converting a document. Available to merchant in cpReport, will not be displayed in the Web-client. |
| BID-189C9 | Signing Error | PE_DOCUMENT_RESPONSE_CREATION. | Logged performance event when converting a document. Available to merchant in cpReport, will not be displayed in the Web-client. |
| BID-189CA | Signing Error | PE_INIT_SIGN_TOTAL. | Logged performance event when converting a document. Available to merchant in cpReport, will not be displayed in the Web-client. |
| BID-18A24 | Signing Error | Document validation message (will only be returned to Merchant, not shown to user). | N/A |
| BID-18A25 | Signing Error | Document validation message (will only be returned to Merchant, not shown to user). | N/A |
| BID-18A26 | Signing Error | Document validation message (will only be returned to Merchant, not shown to user). | N/A |
| BID-18A27 | Signing Error | Document validation message (will only be returned to Merchant, not shown to user). | N/A |
| BID-18A28 | Signing Error | PDF document is invalid. Document validation message (will only be returned to Merchant, not shown to user). | Merchant should investigate its PDF document generation. |
| BID-18A29 | Signing Error | The PDF Validator license is invalid. | Contact BankID support or the party hosting the Client proxy URL being used and refer to error code: BID-18A29. |
| BID-18A2A | Signing Error | Could not read PDF document. | Try again. Merchant should investigate its PDF document generation. If the error persists, contact BankID support and refer to error code: BID-18A2A. |
| BID-18A2B | Signing Error | TXT with illegal elements detected. Document validation message (will only be returned to Merchant, not shown to user). | Merchant should investigate its TXT document generation. |
| BID-18A2C | Signing Error | HTML with illegal elements detected. Document validation message (will only be returned to Merchant, not shown to user). | Merchant should investigate its XML/HTML document generation. |
| BID-18A2D | Signing Error | HTML with illegal attributes detected. Document validation message (will only be returned to Merchant, not shown to user). | Merchant should investigate its XML/HTML document generation. |
| BID-18A2E | Signing Error | Unsupported encoding. | Try again. Investigate Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-18A2E. |
| BID-18A2F | Signing Error | Invalid XML/BIDXML. | Try again. If the error persists, contact BankID support and refer to error code: BID-18A2F. |
| BID-18A8E | Signing Error | Could not update document. | Try again. If the error persists, contact BankID support and refer to error code: BID-18A8E. |
| BID-18A90 | Signing Error | Database connection error. | Try again. If the error persists, contact BankID support and refer to error code: BID-18A90. |
| BID-18AA5 | Signing Error | Could not find document page. | Try again. If the error persists, contact BankID support and refer to error code: BID-18AA5. |
| BID-18AA6 | Signing Error | Document TTL not found. | Try again. If the error persists, contact BankID support and refer to error code: BID-18AA6. |
| BID-18AA7 | Signing Error | Database cleanup error. | Try again. If the error persists, contact BankID support and refer to error code: BID-18AA7. |
| BID-18AA8 | Signing Error | Database update not applied. | Try again. If the error persists, contact BankID support and refer to error code: BID-18AA8. |
| BID-18A8F | Signing Error | Error connecting to merchant. | Try again. If the error persists, contact BankID support and refer to error code: BID-18A8F. |
| BID-18A91 | Signing Error | XSLT requested file access. | Try again. If the error persists, contact BankID support and refer to error code: BID-18A91. |
| BID-18A92 | Signing Error | Failed to configure XML/XSL Transformer. | Try again. If the error persists, contact BankID support and refer to error code: BID-18A92. |
| BID-18A93 | Signing Error | Attempted accessing system property. | Try again. If the error persists, contact BankID support and refer to error code: BID-18A93. |
| BID-18A94 | Signing Error | A href contained JavaScript. | Try again. Investigate Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-18A94. |
| BID-18A95 | Signing Error | The CSS contained an URL. | Try again. Investigate Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-18A95. |
| BID-18A96 | Signing Error | HTML contained meta refresh. | Try again. Investigate Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-18A96. |
| BID-18A97 | Signing Error | HTML contained image with non-dataURI source. | Try again. Investigate Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-18A97. |
| BID-18A98 | Signing Error | Found tag(s) in document description. | Try again. Investigate Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-18A98. |
| BID-18A99 | Signing Error | Base64 decoding error. | Try again. Investigate Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-18A99. |
| BID-18A9A | Signing Error | Base64 encoding error. | Try again. Investigate Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-18A9A. |
| BID-18A9B | Signing Error | Failed to add security provider. | Try again. If the error persists, contact BankID support and refer to error code: BID-18A9B. |
| BID-18A9C | Signing Error | Could not find requested security provider. | Try again. If the error persists, contact BankID support and refer to error code: BID-18A9C. |
| BID-18A9D | Signing Error | Missing merchant seal param. | Try again. Investigate Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-18A9D. |
| BID-18A9E | Signing Error | Missing end user seal param. | Try again. Investigate Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-18A9E. |
| BID-18A9F | Signing Error | Missing document byte range. | Try again. Investigate Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-18A9F. |
| BID-18AA0 | Signing Error | Missing merchant cert in client req. | Try again. Investigate Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-18AA0. |
| BID-18C01 | Signing Error | Error adding seal to document. | Try again. If the error persists, contact BankID support and refer to error code: BID-18C01. |
| BID-18C02 | Signing Error | Error adding signature to document. | Try again. If the error persists, contact BankID support and refer to error code: BID-18C02. |
| BID-18C03 | Signing Error | Error adding signature extension to document. | Try again. If the error persists, contact BankID support and refer to error code: BID-18C03. |
| BID-18C04 | Signing Error | Error loading document. | Try again. If the error persists, contact BankID support and refer to error code: BID-18C04. |
| BID-18C05 | Signing Error | Error updating document source. | Try again. If the error persists, contact BankID support and refer to error code: BID-18C05. |
| BID-18C06 | Signing Error | Error adding document security store. | Try again. If the error persists, contact BankID support and refer to error code: BID-18C06. |
| BID-18C07 | Signing Error | Error saving document security store. | Try again. If the error persists, contact BankID support and refer to error code: BID-18C07. |
| BID-18C08 | Signing Error | Error updating document security store source. | Try again. If the error persists, contact BankID support and refer to error code: BID-18C08. |
| BID-18B00 | Signing Error | Error parsing PAdES validation data JSON. | Try again. Investigate Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-18B00. |
| BID-18B01 | Signing Error | PAdES validation data is empty. | Try again. Investigate Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-18B01. |
| BID-18B02 | Signing Error | PAdES validation data missing for document. | Try again. Investigate Merchant implementation. If the error persists, contact BankID support and refer to error code: BID-18B02. |