Error codes
Code | Description |
---|---|
1001 | Unable to resolve DNS name to IP address. |
1008 | An error occurred on the socket connection. |
1009 | An error occurred during shutdown of the socket descriptor. |
2001 | Unable to open the configuration file. Double check the full path to the configuration file parameter in the call to BID_OpenSession. |
2002 | Unable to parse key/value parameters in configuration file. Check that the configuration file consists only of lines with: <key>=<value> |
2003 | The configuration file consists of more than the supported number of configuration parameters. |
2004 | A property that was supposed to be does not exists. Be sure that all these parameters are set: webaddress, grantedpolicies and truststore |
2005 | A property parameter key is larger than the supported property parameter size. |
2006 | A property parameter value is larger than the supported property parameter size. |
2007 | Unable to open the key store file. Double check the full path to the keystore file in the configuration file or as supplied parameter to BID_OpenSession |
2008 | The maximum number of supported merchant sessions is reached. Shut down process and restart it. |
2009 | The supplied session context is out of bounds. This means that during an interface call, the session context parameter is invalid. |
2010 | The key store file is not valid. It does not contain a valid structure. |
2011 | Unable to retrieve password protected PKCS#7 from key store file. The supplied password is incorrect. |
2012 | Unable to retrieve password protected PKCS#8 from key store file. The supplied password is incorrect. |
2013 | Unable to retrieve PKCS#8 from key store file. The file is not a valid BankID key store file. |
2014 | The key store file consists of too many keys. The file is not a valid BankID key store file. |
2015 | The key store file consists of too many certificates. The file is not a valid BankID key store file. |
2016 | A certificate in the key store file was neither of type "signing" nor "authentication". The file is not a valid BankID key store file. |
2017 | The "authentication" certificate in the key store file is expired. |
2018 | The "signing" certificate in the key store file is expired. |
2020 | The info item set is larger than the supported info item key size. |
2021 | The info item set is larger than the supported info item value size. |
2022 | The info item is not set even though an interface call needs it. |
2023 | More than the supported number of info items is set for the session. Call BID_RemoveInfoItems to clean up. |
2024 | Unable to create an SSL context for the session. |
2025 | The "truststore" property parameter is not set. The merchant must set this in the property file or as input parameter to BID_OpenSession. The trust store points to a directory where trusted CA certificates for SSL connections are stored. |
2026 | An error occurred trying to trust the CA certificates in the directory where the property "truststore" points. The CA certificate files might be corrupt. |
2027 | The SSL context for the session was not found. Be sure that BID_OpenSession is called for the session handle used. |
2028 | An error occurred trying to close the property file after reading the properties. |
2029 | An error occurred trying to close the key store file |
2030 | An error occurred trying to scan the CA certificates in the key store file. |
2032 | More calling threads than what is supported are trying to use the system. Remember to call BID_RemoveInfoItems for all threads setting info items using BID_SetInfoItem. |
2033 | The key store file does not reflect a BankID environment that exists. It is neither for preproduction nor production. |
2034 | An error occurred trying to extract a public key from the BID file |
2035 | An error occurred in the digest engine update |
2036 | An error occurred in the digest engine final |
2037 | BID file is neither Soft Local nor HSM |
2038 | No HSM labels exist in the HSM BID file |
2039 | Signkey does not exist in BID file |
2040 | Authkey does not exist in BID file |
2041 | SignCert does not exist in BID file |
2042 | A verifier key does not exist in the BID file. |
2043 | AuthCert does not exist in BID file |
2044 | CA Certs do not exist in BID file |
2045 | Authkey label does not exist in BID file |
2046 | The supplied password for the BID file is incorrect |
2047 | Invalid soft-RA BID file |
3001 | An error occurred trying to create a critical section blocker. |
3002 | An error occurred waiting to enter a critical section of code. |
3003 | An error occurred trying to exit a critical section of code. |
3004 | A request to enter an unregistered section of critical code occurred. |
4001 | The certificate used to create a signature is neither for authentication nor signing. |
4002 | An error occurred initializing the digest operation |
4003 | An error occurred updating the digest operation. |
4004 | An error occurred finalizing the digest operation. |
4005 | An error occurred initializing the signing operation |
4006 | An error occurred updating the signing operation. |
4007 | An error occurred finalizing the signing operation. |
4008 | Unable to retrieve HSM session context |
4009 | Unable to sign with HSM keys |
4010 | Unable to create PKCS#7 structure |
4011 | Unable to create signature for PKCS#7 |
4012 | Unable to create sha1rsa structure |
4013 | Signature to large for internal buffer. |
4014 | Unable to derencode the signing certificate. |
5001 | The PKCS#7 is invalid |
5002 | The PKCS#7 is of a type that is not signed and can not be used in BankID |
5003 | The PKCS#7 does not contain the digest of the data to verify. |
5004 | The PKCS#7 does not contain signer information. |
5005 | The PKCS#7 does not contain any signers |
5006 | An error occurred trying to initialize the signing operation |
5007 | The PKCS#7 did not verify. |
5008 | Unable to create X509 store context |
5009 | Unable to create X509 store |
5010 | Unable to add trusted CA file path. |
6001 | The certificate type is not supported for the server. Check the "grantedpolicies" parameter for allowed certificate types. |
6002 | The key usage in the certificate does not allow for the current operation. For example using a signing certificate for an authentication operation. |
6003 | The server does not support the certificates key algorithm. |
6004 | The pid was not found in the certificate |
6005 | The originator was not found in the certificate |
6006 | The bank name was not found in the certificate |
6007 | The date of birth was not found in the certificate |
6008 | The policy oid was not found in the certificate |
6009 | The aia location was not found in the certificate |
6011 | The common name was not found in the certificate |
6012 | The key usage was not found in the certificate |
6013 | The email address was not found in the certificate |
6014 | No valid certificate policies were found in the parameter "grantedpolicies" |
6015 | Unable to parse data to ASCII |
6016 | The signer info structure is missing from the PKCS#7 |
6017 | The time of signing is missing from the PKCS#7 |
6018 | An error occurred trying to extract the "Not Before" date in the signing certificate |
6019 | An error occurred trying to extract the "Not After" date in the signing certificate |
6020 | Unable to parse the PKCS#7 structure. |
6021 | The PKCS#7 did not contain any signers |
6022 | The time of signing in the PKCS#7 is after the "Not After" date in the signing certificate |
6023 | The time of signing in the PKCS#7 is before the "Not Before" date in the signing certificate |
6024 | The merchant's signer certificate could not be found. |
6025 | The merchant's organization ID could not be found in the certificate. |
6026 | The merchant's name could not be found in the certificate. |
6027 | The phonenummer was not found in the certificate. |
7001 | The requested digest algorithm is not supported |
7002 | The certificate information item requested is not supported |
8001 | Unable to parse PKCS#7 |
8002 | No signer info in PKCS#7 |
8003 | No signer info certificate found in PKCS#7 |
8004 | The certificate information item requested is not supported |
10001 | The URL is malformed |
10002 | The server parameter in the URL is larger than supported size. |
10003 | The GET parameter in the URL is larger than supported size. |
10004 | The total URL request is larger than supported size. |
10005 | The URL encoding failed. |
11002 | The requested client type is not supported. Supported values are {'NC','SL} |
11003 | The requested java version is not supported. |
11004 | The requested browser type is not supported. |
11005 | The requested browser version is not supported. |
11006 | The requested os is not supported. |
11007 | Critical error. The current running BankID Server contains a serious security flaw. Upgrade to the current version immediately. |
11018 | The property httproxyport is invalid. Be sure it is set correct in the configuration file or as a parameter to BID_OpenSession |
11019 | The BID file does not belong to any BankID environment. |
11021 | Unsupported browser. |
11022 | Unsupported useragent. |
11025 | The BankID Server version is not valid. |
11026 | The browser type is invalid. |
11027 | The browser version is invalid. |
11028 | The user agent is invalid. |
11029 | Invalid OS. |
11030 | The specified configuration is invalid. |
12001 | A mandatory item in the PKCS#7 was not found and is invalid for use in BankID |
12002 | The PKCS#7 does not contain a message digest and is invalid for use in BankID |
12003 | The digest in the PKCS#7 does not match the digest of the data that was originally signed when the PKCS#7 was constructed. |
12004 | The PKCS#7 did not verify. |
12005 | The digest is larger than what is supported |
12006 | An error occurred trying to initialize digest engine |
12007 | An error occurred trying to update digest engine |
12008 | An error occurred trying to finalize digest engine |
12009 | Could not parse PKCS#7 structure. This is an invalid PKCS#7 structure |
12010 | The PKCS#7 does not contain signed attributes |
12011 | The PKCS#7 did not contain any signer info items |
12012 | A required signed attribute was not found in the PKCS#7 |
12013 | A required signed attribute was not of the right datatype |
12014 | A required signed attribute did not contain the expected value. |
12015 | Reserved for future use. |
12016 | Invalid hash algorithm. |
12017 | Unable to derencode signing certificate. |
12018 | Invalid hash. |
12019 | Error parsing signer info. |
13001 | An error occurred signing the OCSP request that should be sent to the VA. |
13002 | The aia location (the full url to the validation authority) is invalid in the certificate. |
13003 | The response from the VA contained an HTTP error response. |
13004 | The response from the VA contained an invalid HTTP header |
13005 | The HTTP response from the VA did not contain the content-length parameter |
13006 | The HTTP response from the VA did not contain a valid content-length parameter. |
13007 | Unable to retrieve a basic OCSP response from the OCSP response from the VA response |
13008 | Unable to retrieve the OCSP response from the VA response |
13009 | The nonce in the OCSP request does not match the nonce in the OCSP response. This indicates a replay attack. |
13010 | The certificate serial number in the OCSP request does not match the certificate serial number in the OCSP response. |
13011 | The OCSP response does not contain the VA's signing certificate. |
13012 | The certificate is revoked |
13013 | Error creating thread for VA communication |
13014 | The VA was unable to check the status of the certificate |
13015 | The OCSP response does not contain any sub responses |
13018 | The VA reports that the OCSP request was malformed |
13019 | The VA reports an internal error during processing of the OCSP request |
13020 | The VA could not process the OCSP request at the moment. Try again later. |
13021 | The VA demands a signed OCSP request. The OCSP request was not signed |
13022 | The signer of the OCSP request is not authorized to lookup the requested certificate |
13023 | The signature of the OCSP request did not verify |
13024 | The content-length value of the HTTP response from VA is invalid |
13026 | The port entry in the aia location is invalid. |
13027 | Unable to retrieve HSM context session |
13028 | The connection to the VA timed out |
13029 | The vatimeout property in the configuration file is invalid |
13030 | Unable to create X509 store context for OCSP verification |
13031 | The VA certificate in the OCSP response did not verify |
13032 | An error occurred trying to initialize the x509 trust store for OCSP verification |
14002 | An error occurred creating an SSL session with the VA. Be sure that the truststore parameter is set correct in the configuration file or as a parameter to BID_OpenSession |
14003 | An error occurred sending data to the VA. The connection might be terminated |
14004 | The VA did not send back a certificate during SSL handshake. |
14005 | The VA certificate does not contain the subject name |
14006 | The VA certificate does not contain the common name |
14007 | The common name of the VA certificate does not match the AIA location of the certificate in request. A hostname mismatch has occurred. |
14008 | An error occurred during SSL connect. Be sure that the truststore parameter is set correct in the configuration file or as a parameter to BID_OpenSession |
14009 | The VA responded with a message that is larger than what is supported |
14010 | An error occurred resolving the AIA location DNS name to ip-address. |
14011 | An error occurred creating a local socket. The process might have run out of file descriptors |
14012 | An error occurred inserting the local socket descriptor into the SSL session. |
14013 | Server SSL certificate did not verify |
14014 | An error occurred on the established socket. |
16001 | The configuration property webaddress was not found. Be sure that the webaddress parameter is set correct in the configuration file or as a parameter to BID_OpenSession |
16002 | The mobile server challenge does not contain name of merchant |
17001 | The requested digest algorithm is not supported. Currently supported digest methods are SHA1 (0), MD5 (1) and SHA256 (2) |
17002 | An error occurred initializing the digest operation |
17003 | An error occurred updating the digest operation |
17004 | An error occurred finalizing the digest operation |
18000 | Creating SDO with Mobile signatures is not supported. |
18001 | The SDO to be created is larger than what is currently supported |
18002 | The SDOList is not present in the SDO structure |
18003 | The SDO is not present in the SDO structure |
18004 | The SDO structure contains more than one SDO |
18005 | The SDO Datapart is not present in the SDO structure |
18006 | The SDO Seal is not present in the SDO structure |
18007 | The SDO version is not present in the SDO structure |
18008 | The first signature element is not present in the SDO structure |
18009 | The second signatureelement is not present in the SDO structure |
18010 | The CMS Signature is not present in the SDO structure |
18011 | The Hashed data is not present in the SDO structure |
18012 | The Digest method is not present in the SDO structure |
18013 | The Digest value is not present in the SDO structure |
18014 | The Signature policy identifier is not present in the SDO structure |
18015 | The Signature policy id is not present in the SDO structure |
18016 | The Sig policy id is not present in the SDO structure |
18017 | The Identifier is not present in the SDO structure |
18018 | The Signers document format is not present in the SDO structure |
18019 | The Mimetype is not present in the SDO structure |
18020 | The User certificate and revocation data is not present in the SDO structure |
18021 | The Revocation values are not present in the SDO structure |
18022 | The OCSP values are not present in the SDO structure |
18023 | The Encapsulated OCSP value is not present in the SDO structure |
18024 | The CMS signature is not present in the SDO structure |
18025 | The SDO profile is not present in the SDO structure |
18026 | The SDO signature is not present in the SDO structure |
18027 | The SDO seal CMS signature element is not present in the SDO structure |
18028 | The SDO seal hashed data is not present in the SDO structure |
18029 | The SDO seal digest method is not present in the SDO structure |
18030 | The SDO seal digest value is not present in the SDO structure |
18031 | The SDO seal signature policy identifier is not present in the SDO structure |
18032 | The SDO seal signature policy id is not present in the SDO structure |
18033 | The SDO seal sig policy id is not present in the SDO structure |
18034 | The SDO seal identifier is not present in the SDO structure |
18035 | The SDO seal signers document format is not present in the SDO structure |
18036 | The SDO seal mimetype is not present in the SDO structure |
18037 | The SDO seal user certificate and revocation data is not present in the SDO structure |
18038 | The SDO seal revocation values are not present in the SDO structure |
18039 | The SDO seal revocation values are not present in the SDO structure |
18040 | The SDO seal encapsulated OCSP value is not present in the SDO structure |
18041 | The SDO seal CMS signature is not present in the SDO structure |
18042 | The SDO seal SDO profile is not present in the SDO structure |
18043 | The SDO contains more than two signature elements. |
20001 | The SDO datapart contains a policy that is not supported |
20002 | The SDO list is not present in the SDO |
20003 | The SDO has more than one SDO element |
20004 | The SDO version is not present in the SDO structure |
20005 | The SDO datapart is not present in the SDO structure |
20006 | The SDO signature is not present in the SDO structure |
20007 | The SDO policy is not present in the SDO structure |
20008 | The hashed data is not present in the SDO structure |
20009 | The datatype is not present in the SDO structure |
20010 | Unable to parse the datapart signature |
20011 | Incorrect policy oid for datapart signer |
20012 | The data is not present in the sdo, but a request to to verify the data was requested |
20013 | Hashed data is not a digest of the data in the SDO |
20014 | The signaturelist is not present in the SDO |
20015 | DateTime format is not valid in the SDO |
20016 | A signatureelement lacks OCSP response data |
20017 | A signatureelement lacks OCSP response data length |
20018 | Unable to parse the signature elements OCSP response |
20019 | No responsedata in the OCSP response |
20020 | No producedat in the OCSP response |
20021 | Missing single response in OCSP response data |
20022 | The certificate status in the OCSP response was not good. |
20023 | Unable to parse PKCS#7 structure |
20024 | No certid in OCSP response |
20025 | The OCSP response in the signatureelement is not for the certificate in the PKCS#7. The serialnumbers are not equal |
20026 | The OCSP response in the signatureelement is not for the certificate in the PKCS#7. The issuernames are not equal |
20027 | The timegap between the OCSP's in the two signatureelements are too large |
20028 | No merchant has signed the SDO contract |
20029 | There are not two signatureelements in the SDO. |
20030 | The datapart signatureelement did not verify |
20033 | The datapart CMS signature is not done using SHA1 |
20034 | Mimetype not supported |
20035 | Signature policy not supported |
20036 | The SDO seal did not verify |
20037 | The two signatureelements are not signatures over the same data |
20039 | The Signed object is not present in the SDO while requesting a validation of the signed data. |
20040 | The SDO seal signature is not done by the merchant signature element. |
20041 | The signatures in the SDO is not done over the data in the SDO |
20042 | The number of signatures in the SDO does not match the required number of signatures |
20043 | The SDO is unsealed, but it was required that the SDO was sealed |
20044 | The SDO is sealed, but it was required that the SDO was unsealed |
20045 | Unable to verify the contract. The contract is not sent as a parameter and is not contained in the SDO. |
21001 | Failed to base64 encode data |
21002 | Failed to base64 decode data |
21003 | An error occurred in the base64 decode engine |
21004 | An error occurred in the base64 decode engine memory buffer |
21005 | An error occurred in the base64 encode engine |
21006 | An error occurred creating the base64 membuf |
22001 | Unable to open private key file |
22002 | Unable to parse PKCS8 structure. |
22003 | Unable to decrypt PKCS8. |
22004 | Unable to create private key from decrypted PKCS8. |
22005 | Unable to decrypt data with private key. |
22006 | Unable to retrieve hsm context. |
23001 | Unable to initialize decryption. |
23002 | Unable to update decryption. |
23003 | Unable to finish decryption. |
24001 | Unable to initialize encryption. |
24002 | Unable to update encryption. |
24003 | Unable to finish encryption. |
25001 | Unable to load the PKCS#11 driver. Check the path and file |
25002 | The PKCS#11 interface function C_INITIALIZE was not found in the supplied driver. |
25003 | An error occurred during the C_INITIALIZE call. |
25004 | The PKCS#11 interface function C_GETSLOTLIST was not found in the supplied driver. |
25005 | An error occurred during the C_ GETSLOTLIST call. |
25006 | The PKCS#11 interface function C_OPENSESSION was not found in the supplied driver. |
25007 | An error occurred during the C_ OPENSESSION call. |
25008 | The PKCS#11 interface function C_LOGIN was not found in the supplied driver. |
25009 | An error occurred during the C_ LOGIN call. |
25010 | The PKCS#11 interface function C_GENERATEKEYPAIR was not found in the supplied driver. |
25011 | An error occurred during the C_ GENERATEKEYPAIR call. |
25012 | The PKCS#11 interface function C_LOGOUT was not found in the supplied driver. |
25013 | An error occurred during the C_ LOGOUT call. |
25014 | The PKCS#11 interface function C_CLOSESESSION was not found in the supplied driver. |
25015 | An error occurred during the C_ CLOSESESSION call. |
25016 | The PKCS#11 interface function C_FINALIZE was not found in the supplied driver. |
25017 | An error occurred during the C_ FINALIZE call. |
25018 | The PKCS#11 interface function C_CREATEOBJECT was not found in the supplied driver. |
25019 | An error occurred during the C_ CREATEOBJECT call. |
25020 | The PKCS#11 interface function C_SIGNINIT was not found in the supplied driver. |
25021 | An error occurred during the C_ SIGNINIT call. |
25022 | The PKCS#11 interface function C_SIGN was not found in the supplied driver. |
25023 | An error occurred during the C_ SIGN call. |
25024 | The PKCS#11 interface function C_FINDOBJECTSINIT was not found in the supplied driver. |
25025 | An error occurred during the C_ FINDOBJECTSINIT call. |
25026 | The PKCS#11 interface function C_FINDOBJECTS was not found in the supplied driver. |
25027 | An error occurred during the C_ FINDOBJECTS call. |
25028 | The PKCS#11 interface function C_FINDOBJECTSFINAL was not found in the supplied driver. |
25029 | An error occurred during the C_ FINDOBJECTSFINAL call. |
25030 | Unable to find the requested private key. |
25031 | There are no HSM's (tokens) configured in any available slots. |
25032 | The label for the keys in the BID files does not exist in any of the configured HSM's |
25033 | The PKCS#11 implementation is not loaded yet. |
25034 | The PKCS#11 interface function C_DECRYPTINIT was not found in the supplied driver. |
25035 | The PKCS#11 interface function C_DECRYPT was not found in the supplied driver. |
25036 | An error occurred during the C_DECRYPTINIT function call |
25037 | An error occurred during the C_DECRYPT function call |
26001 | The SDO is not valid as it does not contain any SDO elements. |
27001 | The input to lowercase was NULL |
28001 | Mandatory configuration parameter is empty |
28002 | Mandatory configuration parameter is invalid. |
28003 | Web address parameter is "localhost". |
28004 | Web address parameter is not a valid hostname |
29001 | An error occurred initializing the digest engine |
29002 | An error occurred updating the digest engine |
29003 | An error occurred finalizing the digest engine |
29004 | An error occurred retrieving the HSM context |
29005 | An error occurred initializing the signing engine |
29006 | An error occurred updating the signing engine |
29007 | The signing certificate is neither SIGNING nor AUTHENTICATION |
29008 | An error occurred finalizing the signing engine |
29009 | Signature does not match in the static allocated buffer |
30001 | CreateXMLDSIG can only be used by banks that hold a valid RA signer certificate. |
31001 | Unable to verify contract. The contract was not sent as a parameter and is not contained int the SDO. |
32001 | The BankID C Server is not running under a valid BankID environment. Check the BID-file. |
32002 | No channel parameters were set. CreateSecureChannel only gives meaning in conjunction with setting parameters using BID_SetInfoItem() |
32004 | The size of the parameters set for the channel exceeds the allowed size. |
33001 | Out of memory. |
33002 | A required parameter was NULL or not within required values |
33003 | A pointer was invalid. The process did not have read access (or/and write access) to the virtual memory address contained in the pointer. |
33004 | A string truncation occurred. |
34001 | The SDO is not valid XML |
34002 | The SDO is valid XML but does not contain SDO |
34003 | Old format not supported. |
35000 | The HTTP communicator returned OK. |
35001 | The HTTP communicator function was initialized with the wrong arguments |
35002 | The HTTP communicator could not connect to the proxy server |
35003 | The HTTP communicator did not got a response from the proxy server |
35004 | The HTTP communicator got an error response from the proxy server |
35005 | The HTTP communicator could not connect to the server |
35006 | The HTTP communicator encountered errors during SSL handshake |
35007 | The HTTP communicator could not retrieve the SSL peer certificate |
35008 | The HTTP communicator could not retrieve the SSL peer certificate subject name |
35009 | The HTTP communicator could not retrieve the SSL peer certificate common name |
35010 | There is a mismatch in the SSL certificate's common name and the server hostname |
35011 | The HTTP communicator encountered a connection error |
35012 | The proxy credentials used by the HTTP communicator is not valid |
35013 | The HTTP communicator encountered an internal error |
35014 | The HTTP communicator timed out |
35015 | The HTTP communicator failed during initialization |
35016 | The HTTP communicator failed during finalization |
36001 | The BankID C Server is not running under a valid BankID environment. |
36002 | Unable to create thread for MGMFE communication |
36003 | The connection with BankID Mobile Gateway timed out. |
36004 | The response from BankID Mobile Gateway was not OK |
36005 | The response from BankID Mobile Gateway was empty |
36006 | The response from BankID Mobile Gateway did not contain a status code |
36007 | The status code from BankID Mobile Gateway was not OK |
37001 | The response from BankID Mobile Gateway did not contain expected transaction reference |
37002 | The response from BankID Mobile Gateway did not contain expected transaction status. |
38001 | Could not generate random for merchant reference |
38002 | Unable to download dictionary |
38003 | Validation of downloaded dictionary failed. |
39001 | Mandatory infoitem missing |
39002 | The "operation" parameter missing in the encrypted InitTransaction request |
39003 | The "clientChallenge" parameter missing in the encrypted InitTransaction request |
39004 | The "clientIp" parameter missing in the encrypted InitTransaction request |
39005 | The specified MIME type is not supported. |
39006 | The "operation" parameter specifiedin the InitTransaction request is not supported |
39007 | Error during create / encrypt of response. |
39008 | The received TID doesn't match the TID infoitem. |
40001 | The "operation" parameter was missing in the encrypted VerifyTransaction request |
40002 | The "pkcs7" parameter was missing in the encrypted VerifyTransaction request |
40003 | The "ocsp" parameter was missing in the encrypted VerifyTransaction request |
40004 | The "errorCode" parameter was missing in the encrypted VerifyTransaction request |
40005 | The "operation" parameter in the VerifyTransaction request is not supported |
40006 | The received TID doesn't match the TID infoitem. |
40007 | The "pkcs7s" parameter was missing in the encrypted VerifyTransaction request |
40008 | Error while parsing rtReport |
40009 | The number of documents set is not equal to the number of signatures received |
40010 | Signed data is missing |
40050 | Invalid MAC length. |
40051 | Computed MAC does not match received MAC. |
41000 | A key was not found in the map. |
42000 | Incorrect response from Services (TransactionInfo) |
42001 | Invalid Nonce in response (TransactionInfo) |
43000 | Unknown BankID environment (InitSession) |
43001 | Unknown response from SDM (InitSession) |
43002 | Incorrect response from SDM (InitSession) |
43003 | Error received from SDM (InitSession) |
43004 | No nonce in response from SDM (InitSession) |
43005 | The received nonce doesn't match the expected value (InitSession) |
43006 | No Helper URI in response from SDM (InitSession) |
43007 | No TID in response from SDM (InitSession) |
43008 | No ClientID (aka CID, KID, GUID) in response from SDM (InitSession) |
44000 | Unable to determine which key to use to encrypt request to SDM |
44001 | Error encrypting basekey in the SDM request. |
45000 | The country was not found in the certificate |
45001 | The organization was not found in the certificate |
Serial signing errors | |
46000 | PAdES error, byterange to insert merchant signature into has insufficient space to hold the signature, preferred size as of PDFBox is 0x4A00 (i.e. signature 0x2500 bytes) |
46001 | Merchant input error, mix of parallel and serial signed documents, either all or no documents must have parallel signing mode |
46002 | Merchant error, sealbuilder function supplied by merchant did not return any data |
46003 | Merchant error, sealbuilder function supplied by merchant returned a byterange with data, but the byterange did not fit the given document |
46004 | Merchant error, at least one document has an invalid serial signing kind |
46005 | Clientproxy protocol error, missing or invalid parameter in request |
46006 | Merchant error: Mix of self-assembler (PAdES-only) flow and non-PAdES documents (text, XML or PDF that should be signed in parallel) |
46007 | Merchant's seal or validation data builder function failed (i.e. non-zero return value). Check the implementation of the builder function. |
46008 | Illegal configuration requested: The "noGraphic" infoitem was set to "Y" while self-assembling seals. |
46009 | A function that only makes sense for a document being signed serially, was called for a document being signed in parallel. |
46010 | A function that only makes sense for a document being signed in parallel, was called for a document being signed serially. |
46011 | Serial signing was requested, but documents configured for parallel signing were added. |
46012 | Serial signing was not requested, but documents configured for serial signing were added. |