Return codes

When using EBICS Client, you may receive return codes and event messages.

Return codes for events

The tables here list the return code, the corresponding event message and a brief description of the return code.

Table 1. Return codes for events
Return Code Event Message Summary
EBICSCL2302 Order Data Compressed Indicates that the order data of the transaction is compressed. No action required.
EBICSCL2303 Order Data Encrypted Indicates that the order data of the transaction is encrypted. No action required.
EBICSCL2304 Order Data Encoded Indicates that the order data of the transaction is encoded. No action required.
EBICSCL2305 Order Data Signed Indicates that the order data of the transaction is signed. No action required.
EBICSCL2306 Order Data Decompressed Indicates that the order data of the transaction is decompressed. No action required.
EBICSCL2307 Order Data Decrypted Indicates that the order data of the transaction is decrypted. No action required.
EBICSCL2308 Order Data Decoded Indicates that the order data of the transaction is decoded. No action required.
EBICSCL2309 Signature Data Compressed Indicates that the signature data of the transaction is compressed. No action required.
EBICSCL2310 Signature Data Encrypted Indicates that the signature data of the transaction is encrypted. No action required.
EBICSCL2311 Signature Data Encoded Indicates that the signature data of the transaction is encoded. No action required.
EBICSCL2312 Signature Data Decompressed Indicates that the signature data of the transaction is decompressed. No action required.
EBICSCL2313 Signature Data Decrypted Indicates that the signature data of the transaction is decrypted. No action required.
EBICSCL2314 Signature Data Decoded Indicates that the signature data of the transaction is decoded. No action required.
EBICSCL2300 EBICS Packaging Passed Indicates that the packaging of the order data was successful. No action required.
EBICSCL2301 EBICS Packaging Failed Indicates that the packaging of the order data was not successful. A few of the reasons for the failure of packaging may be a result of failure when compressing order data, or encrypting order data, or erroneous keys used in signature or encryption. Review the list of events using Event Viewer from the EBICS Client dashboard interface.
EBICSCL2500 EBICS Unpackaging Passed Indicates that the unpackaging of the order data was successful. No action required.
EBICSCL2501 EBICS Unpackaging Failed Indicates that the unpackaging of the order data was not successful. A few of the reasons for the failure of unpackaging may be a result of failure when decompressing order data, or decrypting order data, or erroneous keys used in signature verification. Review the list of events using Event Viewer from the EBICS Client dashboard interface.
EBICSCL2318 Valid Response Received Indicates that you have received a valid response from the server when you submit an order type.
EBICSCL2319 Erroneous Response Received Indicates that the server returned an erroneous response for a particular order request. For more information about the response, view the list of events using Event Viewer from the EBICS Client dashboard interface for technical and business return codes.
EBICSCL2320 EBICS Initialisation Request Passed Indicates that the request has been initialized.
EBICSCL2321 EBICS Data Transfer Request Passed Indicates that the request for transfer of data has been accepted by the bank.
EBICSCL2322 No Submitter Authority Indicates that you do not have the user permission to submit an order. Configure the user permission for the role with authorization level set to T and permission type set to Submitter.
EBICSCL2323 Unpackaged data writing to Mailbox success Indicates that the data was unpackaged and stored in the user mailbox.
EBICSCL2324 Unpackaged data writing to Mailbox failure The failure to write unpackaged data to a mailbox may be a result of inadequate permission to access mailbox. For more information, see the ebicsClient.log file.
EBICSCL2325 Pending Tasks created for Authorizers Indicates that pending tasks are created for the user. View the list of pending tasks to be signed using the EBICS Client dashboard interface.
EBICSCL2326 Pending Tasks created for Submitter Indicates that pending tasks are created for the user who is authorized to submit orders. View the list of pending tasks to be submitted using the EBICS Client dashboard interface.
EBICSCL2327 Signature generation successful for Authorizer Indicates that the signature generation was successful when a signatory signed an order that was pending for signature.
EBICSCL2328 Signature generation failed for Authorizer Indicates that the signature generation was unsuccessful when a signatory signed an order that was pending for signature.
EBICSCL2329 OrderType is invalid Indicates that the order type specified is invalid. Specify a valid order type.
EBICSCL2330 HostID is invalid Indicates that the host ID or the bank ID specified is invalid. Specify a valid host ID.
EBICSCL2331 PartnerID and UserID combination is invalid Indicates that the user ID and the associated partner ID combination is invalid. Specify a valid combination of user ID and associated partner ID.
EBICSCL2332 SystemID is invalid Indicates that the system ID specified is invalid. Specify a valid system ID.
EBICSCL2333 Missing mandatory parameter in order metadata Indicates that a mandatory parameter in the order metadata is not included. Review the ordermetadata.xml for the missing parameter and specify a valid value for the parameter.
EBICSCL2334 Security Medium is invalid Indicates that the value specified for security medium is not valid. Enter a four-digit security number in the 0100 – 0499 range.
EBICSCL2335 Unable to parse Primary Document in Workflow Re-check configuration and initiate transaction.
EBICSCL2336 Encryption Public Key not found for Bank Upload a valid encryption key.
EBICSCL2337 Could not retrieve Key for usage When signing or encrypting order data, the key to the alias could not be retrieved.
EBICSCL2338 Segment Upload to Host The order data segment was successfully uploaded to the server.
EBICSCL2339 Segment Download from Host The order data segment was successfully downloaded from the server.
EBICSCL2340 Calculated Total Number of segments to be Uploaded EBICS Client calculates the total number of segments of an order data that is to be uploaded.
EBICSCL2341 Got Total Number of segments to be Downloaded EBICS Client receives the total number of segments of an order data that is to be downloaded.
EBICSCL2342 Auto Submit value is invalid Indicates that the value defined for autosubmit is not valid and therefore the order cannot be automatically submitted. Enter a valid value for the autosubmit parameter. Valid values are true and false.
EBICSCL2343 Country code value is invalid Indicates that the abbreviation for a country is not valid. Specify a valid format for country abbreviations.
EBICSCL2344 Host not yet Active Indicates that the server at the bank is not yet active. Download the bank keys using the HPB order type and validate the bank keys.
EBICSCL2345 User not yet Ready Indicates that the subscriber initialization for the user is not yet complete. Generate the INI and HIA letters for the user associated with the partner and send them to the bank for validation.
EBICSCL2346 Response data writing to Mailbox success Indicates that the response received from the bank was successfully stored in the mailbox.
EBICSCL2347 Response data writing to Mailbox failure The failure to write response data to a mailbox may be a result of inadequate permission to access mailbox. For more information, see the ebicsClient.log file.
EBICSCL2348 Error putting message into Mailbox Indicates that the message could not be uploaded to the mailbox.
EBICSCL2349 No Response from Server Indicates that the server did not respond when a request was sent to the server.
EBICSCL2350 Invalid response from Server Indicates that the server returned an invalid response when a request was sent to the server.
EBICSCL2392 Mandatory Parameter for HttpClient missing Indicates that the name of the configured http client adapter is null, or adapter properties are missing, or if the host or port is not configured properly. If SSL is enabled, CA certificate is not configured.
EBICSCL2393 HttpClient Instance Not Found Indicates that the http client adapter instance is missing.
EBICSCL2394 Error in Ending HTTP Session with Server Indicates that an error occurred when ending the HTTP session with the server, which may be a result of not finding a valid session.
EBICSCL2395 Host Not Found Indicates that the host or port is not configured properly.
EBICSCL2396 Handshake Failure When connecting to the server using SSL. the connection may be unsuccessful, for example, because of invalid certificates.
EBICSCL2398 Could not complete connection to specified host Indicates that the client was unable to connect to a host even when the session was successfully started.
EBICSCL2351 Invalid key length for signature Indicates that the length of the bank-technical keys is invalid for signature. Ensure that the key length is equal to or greater than 1536 bit and equal to or lesser than 4096 bit.

For information about defining EBICS-specific key lengths for electronic signature, encryption, and authentication, see EBICS Specification, version 2.4.2.
EBICSCL2352 Invalid key length for authentication Indicates that the length of the bank-technical keys is invalid for identification and authentication. Ensure that the key length is equal to or greater than 1024 bit and equal to or lesser than 16384 bit.

For information about defining EBICS-specific key lengths for electronic signature, encryption, and authentication, see EBICS Specification, version 2.4.2.
EBICSCL2353 Invalid key length for encryption Indicates that the length of the bank-technical keys is invalid for encryption. Ensure that the key length is equal to or greater than 1024 bit and equal to or lesser than 16384 bit.

For information about defining EBICS-specific key lengths for electronic signature, encryption, and authentication, see EBICS Specification, version 2.4.2.
EBICSCL2354 Error in starting HTTP Session with Server Indicates that an error occurred when starting an HTTP session with the server.
EBICSCL2355 Error in parsing OrderMetadata Document with Message ID Check whether the XML is well-formed or not.
EBICSCL2356 Technical Subscriber does not have permissions to be a delegate of the User specified Configure technical user and associate the technical user with an existing user.
EBICSCL2357 Error while trying to retrieve message from Mailbox Indicates that an error occurred when retrieving a message from the mailbox.
EBICSCL2358 Error in parsing OrderMetadata Document Check whether the XML is well-formed.
EBICSCL2359 Signature Application Rejected Signature application rejected because the signature requirements were already met for the order.
EBICSCL2360 Submission Application Rejected Submission application rejected because the order has already been submitted to the bank.
EBICSCL2361 Ordermetadata file is not a zip file or no files present inside the zip Ensure that the ordermetadata file is in a compressed format and that the zip file has valid content.
EBICSCL2362 Incorrect number of files present in Ordermetadata zip Indicates that the number of files present in the ordermetadata.zip file is incorrect. For example, when submitting an FUL order type from back-end, if the zip file does not contain either the payload data or the ordermetadata.xml or both.
EBICSCL2363 Missing file with name ordermetadata.xml in Ordermetadata zip Ensure that the zip file contains a file with the name ordermetadata.xml.
EBICSCL2364 Missing Payload file in Ordermetadata zip for OrderType FUL Ensure that the zip file contains the payload order data for order type FUL.
EBICSCL2365 Error while trying to retrieve Transport URL or other mandatory transport parameters Indicates that the host URL is malformed or the client is unable to retrieve HTTP configuration details from the database.
EBICSCL2366 Error while decrypting the data An error occurred when decrypting the data. The error may be a result of, for example, encrypting the data with the wrong certificate or if the data is not complete.
EBICSCL2367 Error while encrypting the data Indicates that the key was not found.
EBICSCL2368 Error while creating XML authentication The error may be a result of , for example, certificate not configured or unable to retrieve the certificate.
EBICSCL2369 Error while verifying XML authentication The error may be a result of , for example, certificate not configured or unable to retrieve the certificate.
EBICSCL2370 Unexpected Return code from Server The server returned an error not defined in the client database.
EBICSCL2371 EBICS Client Internal Error An internal error occurred when processing an EBICS request.

Return codes for HPB

Table 2. Return codes for HPB
Return Code Event Message Summary
EBICSCL1701 EBICS HPB Request Creation Failed An error occurred when creating an HPB request.
EBICSCL1702 EBICS HPB Request Creation Passed The HPB order request was created successfully.
EBICSCL1703 EBICS HPB Response Parsing Failed An error occurred when parsing an HPB response.
EBICSCL1704 EBICS HPB Response Parsing Passed The HPB response was parsed successfully.
EBICSCL1705 EBICS HPB Response Un-Packing Passed The HPB response was unpacked successfully.
EBICSCL1706 EBICS HPB Response Un-Packing Failed An error occurred when unpacking an HPB response.
EBICSCL1707 EBICS HPB Bank Certs Save Failed An error occurred when saving the bank keys.
EBICSCL1708 EBICS HPB Bank Certs Save Pass The HPB bank keys were saved successfully.

Return codes for keys

Table 3. Return codes for keys
Return Code Event Message Summary
EBICSCL2372 to EBICSCL2381 Could not retrieve Private Key for usage The following is a list of possible reasons for failure to retrieve private keys:
  • SystemCertificate not found in Database
  • Certificate is Expired
  • Certificate Not Yet Valid
  • Certificate is Held
  • Certificate is Revoked
  • Invalid Issuer Signature for a certificate in the chain
  • CertPathValidation failed
  • Error in Certificate
  • Error in fetching Certificate
  • Error in fetching key from RSA KeyStore
EBICSCL2382 to EBICSCL2391 Could not retrieve Public Key for usage The following is a list of possible reasons for failure to retrieve public keys:
  • Key not found in Database
  • Certificate is Expired
  • Certificate Not Yet Valid
  • Certificate is Held
  • Certificate is Revoked
  • Invalid Issuer Signature for a certificate in the chain
  • CertPathValidation failed
  • Error in Certificate
  • Error in fetching Certificate
  • Error in fetching key from RSA KeyStore

Return codes for generating order IDs

Table 4. Return codes for generating order IDs
Return Code Event Message Summary
EBICSCL2399 OrderID generation re-initialized Indicates that the last three alphanumeric values in the order ID, which can range from 000 to zzz, was re-initialized to 000.
EBICSCL2400 Order logging failed in the EBICS client system The order ID already exists in the system for partner ID. Contact administrator for further action.
EBICSCL2401 OrderID generation failed In a multi-node scenario, when one of the nodes fails to refresh the order ID cache and consequently fails to generate an Order ID for a particular order.
EBICSCL2402 OrderID Cache configuration error Check the configuration for order ID cache under System Properties.

Technical return codes

Table 5. Technical return codes
Return Code Event Message Summary
ESRVT011000 [t011000] EBICS_DOWNLOAD_POSTPROCESS_DONE The positive acknowledgment of the EBICS response that is sent to the client from the server.
ESRVT011001 [t011001] EBICS_DOWNLOAD_POSTPROCESS_SKIPPED The negative acknowledgment of the EBICS response that is sent to the client from the server.
ESRVT011101 [t011101] EBICS_TX_SEGMENT_NUMBER_UNDERRUN The server terminates the transaction if the client, in an upload transaction, has specified a very high (when compared to the number specified in the initialization phase) number of segments that are to be transmitted to the server.
ESRVT031001 [t031001] EBICS_ORDER_PARAMS_IGNORED The supplied order parameters that are not supported by the bank are ignored.
ESRVT061001 [t061001] EBICS_AUTHENTICATION_FAILED The bank is unable to verify the identification and authentication signature of an EBICS request.
ESRVT061002 [t061002] EBICS_INVALID_REQUEST The received EBICS XML message does not conform to the EBICS specifications.
ESRVT061099 [t061099] EBICS_INTERNAL_ERROR An internal error occurred when processing an EBICS request.
ESRVT061101 [t061101] EBICS_TX_RECOVERY_SYNC If the bank supports transaction recovery, the bank verifies whether an upload transaction can be recovered. The server synchronizes with the client to recover the transaction.
ESRVT091002 [t091002] EBICS_INVALID_USER_OR_USER_STATE Error that results from an invalid combination of user ID or an invalid subscriber state.
ESRVT091003 [t091003] EBICS_USER_UNKNOWN The identification and authentication signature of the technical user is successfully verified but the non-technical subscriber is not known to the bank.
ESRVT091004 [t091004] EBICS_INVALID_USER_STATE The identification and authentication signature of the technical user is successfully verified and the non-technical subscriber is known to the bank, but the user is not in a ’Ready’ state.
ESRVT091005 [t091005] EBICS_INVALID_ORDER_TYPE Upon verification, the bank finds that the order type specified in invalid.
ESRVT091006 [t091006] EBICS_UNSUPPORTED_ORDER_TYPE Upon verification, the bank finds that the order type specified in valid but not supported by the bank.
ESRVT091007 (H003 protocol)
[t091007] EBICS_USER_AUTHENTICATION_REQUIRED

(H004 protocol)
[t091007] EBICS_DISTRIBUTED_SIGNATURE_AUTHORISATION_FAILED

 Subscriber possesses no authorization of signature for the referenced order in the VEU administration.
ESRVT091008 [t091008] EBICS_BANK_PUBKEY_UPDATE_REQUIRED The bank verifies the hash value sent by the user. If the hash value does not match the current public keys, the bank terminates the transaction initialization.
ESRVT091009 [t091009] EBICS_SEGMENT_SIZE_EXCEEDED If the size of the transmitted order data segment exceeds 1 MB, the transaction is terminated.
ESRVT091010 [t091010] EBICS_INVALID_XML The XML schema does not conform to the EBICS specifications.
ESRVT091011 [t091011] EBICS_INVALID_HOST_ID The transmitted host ID is not known to the bank.
ESRVT091101 [t091101] EBICS_TX_UNKNOWN_TXID The supplied transaction ID is invalid.
ESRVT091102 [t091102] EBICS_TX_ABORT If the bank supports transaction recovery, the bank verifies whether an upload transaction can be recovered. If the transaction cannot be recovered, the bank terminates the transaction.
ESRVT091103 [t091103] EBICS_TX_MESSAGE_REPLAY To avoid replay, the bank compares the received Nonce with the list of nonce values that were received previously and stored locally. If the nonce received is greater than the tolerance period specified by the bank, the response EBICS_TX_MESSAGE_REPLAY is returned.
ESRVT091104 [t091104] EBICS_TX_SEGMENT_NUMBER_EXCEEDED The serial number of the transmitted order data segment must be less than or equal to the total number of data segments that are to be transmitted. The transaction is terminated if the number of transmitted order data segments exceeds the total number of data segments.
ESRVT091112 [t091112] EBICS_INVALID_ORDER_PARAMS This error can have different causes.

For example, in an HVT request, the subscriber specifies the order for which they want to retrieve the VEU transaction details. You can define an offset position in the original order file in the customer system. The order details are returned after the offset position. If the value specified for offset is higher than the total number of order details, the error EBICS_INVALID_ORDER_PARAMS is returned.

The error EBICS_INVALID_ORDER_PARAMS may also be returned for FUL or FDL orders when the there is a mismatch between the order type and file format set up in the server configuration and the request from the client.
ESRVT091113 [t091113] EBICS_INVALID_REQUEST_CONTENT The EBICS request does not conform to the XML schema definition specified for individual requests.
ESRVT091117 [t091117] EBICS_MAX_ORDER_DATA_SIZE_EXCEEDED The bank does not support the requested order size.
ESRVT091118 [t091118] EBICS_MAX_SEGMENTS_EXCEEDED The submitted number of segments for upload is very high.
ESRVT091119 [t091119] EBICS_MAX_TRANSACTIONS_EXCEEDED The maximum number of parallel transactions per customer is exceeded.
ESRVT091120 [t091120] EBICS_PARTNER_ID_MISMATCH The partner ID of the electronic signature file differs from the partner ID of the submitter.
ESRVT091121 [t091121] EBICS_INCOMPATIBLE_ORDER_ATTRIBUTE The specified order attribute is not compatible with the order in the bank system. If the bank has a file with the attribute DZHNN or other electronic signature files (for example, with the attribute UZHNN) for the same order, then the use of the order attributes DZHNN is not allowed. Also, if the bank already has the same order and the order was transmitted with the order attributes DZHNN, then again the use of the order attributes DZHNN is not allowed.
(H004 protocol)
ESRVT091219		 [t091219] EBICS_CERTIFICATES_VALIDATION_ERROR The server is unable to match the certificate with the previously declared information automatically.
(H005 protocol)
ESRVT091005		 [t091005] EBICS_INVALID_ORDER_IDENTIFIER The administrative order type or the combination of BTF identifiers is unknown or not approved for use with EBICS.
(H005 protocol)
ESRVT091006		 [t091006] EBICS_UNSUPPORTED_ORDER_IDENTIFIER The selected administrative order type or the combination of BTF identifiers is optional with EBICS and is not supported by the financial institution.
(H005 protocol)
ESRVT091122		 [t091122] EBICS_ORDER_ALREADY_EXISTS EBICS order already exists.

Bank-technical return codes

Table 6. Bank-technical return codes
Return Code Event Message Summary
ESRVB011301 [b011301] EBICS_NO_ONLINE_CHECKS The bank does not principally support preliminary verification of orders but the EBICS request contains data for preliminary verification of the order.
ESRVB091001 [b091001] EBICS_DOWNLOAD_SIGNED_ONLY The bank system only supports bank-technically signed download order data for the order request. If the subscriber sets the order attributes to DZHNN and requests the download data without the electronic signature of the bank, the transaction initialization is terminated.
ESRVB091002 [b091002] EBICS_DOWNLOAD_UNSIGNED_ONLY The bank system only supports unsigned download order data for the order request. When it is agreed that the subscriber can download order data only without the electronic signature of the bank, if the subscriber sets the order attributes to OZHNN and requests the download data with the electronic signature of the bank, the transaction initialization is terminated.
ESRVB090003 [b090003] EBICS_AUTHORISATION_ORDER_TYPE_FAILED The subscriber is not entitled to submit orders of the selected order type. If the authorization is missing when the bank verifies whether the subscriber has a bank-technical authorization of signature for the order, the transaction is cancelled.
ESRVB090004 [b090004] EBICS_INVALID_ORDER_DATA_FORMAT The order data does not correspond with the designated format.
ESRVB090005 [b090005] EBICS_NO_DOWNLOAD_DATA_AVAILABLE If the requested download data is not available, the EBICS transaction is terminated.
ESRVB090006 [b090006] EBICS_UNSUPPORTED_REQUEST_FOR_ORDER_INSTANCE In the case of some business transactions, it is not possible to retrieve detailed information of the order data.
ESRVB091105 [b091105] EBICS_RECOVERY_NOT_SUPPORTED If the bank does not support transaction recovery, the upload transaction is terminated.
ESRVB091111 [b091111] EBICS_INVALID_SIGNATURE_FILE_FORMAT The submitted electronic signature file does not conform to the defined format.
ESRVB091114 [b091114] EBICS_ORDERID_UNKNOWN Upon verification, the bank finds that the order is not located in the VEU processing system.
ESRVB091115 [b091115] EBICS_ORDERID_ALREADY_EXISTS The submitted order number already exists.
ESRVB091116 [b091116] EBICS_PROCESSING_ERROR When processing an EBICS request, other business-related errors occurred.
ESRVB091201 [b091201] EBICS_KEYMGMT_UNSUPPORTED_VERSION_SIGNATURE When processing an INI request, the order data contains an inadmissible version of the bank-technical signature process.
ESRVB091202 [b091202] EBICS_KEYMGMT_UNSUPPORTED_VERSION_AUTHENTICATION When processing an HIA request, the order data contains an inadmissible version of the identification and authentication signature process.
ESRVB091203 [b091203] EBICS_KEYMGMT_UNSUPPORTED_VERSION_ENCRYPTION When processing an HIA request, the order data contains an inadmissible version of the encryption process.
ESRVB091204 [b091204] EBICS_KEYMGMT_KEYLENGTH_ERROR_SIGNATURE When processing an INI request, the order data contains an bank-technical key of inadmissible length.
ESRVB091205 [b091205] EBICS_KEYMGMT_KEYLENGTH_ERROR_AUTHENTICATION When processing an HIA request, the order data contains an identification and authentication key of inadmissible length.
ESRVB091206 [b091206] EBICS_KEYMGMT_KEYLENGTH_ERROR_ENCRYPTION When processing an HIA request, the order data contains an encryption key of inadmissible length.
ESRVB091207 [b091207] EBICS_KEYMGMT_NO_X509_SUPPORT A public key of type X509 is sent to the bank but the bank supports only public key value type.
ESRVB091208 [b091208] EBICS_X509_CERTIFICATE_EXPIRED The certificate is not valid because it has expired.
ESRVB091209 [b091209] EBICS_X509_CERTIFICATE_NOT_VALID_YET The certificate is not valid because it is not yet in effect.
ESRVB091210 [b091210] EBICS_X509_WRONG_KEY_USAGE When verifying the certificate key usage, the bank detects that the certificate is not issued for current use.
ESRVB091211 [b091211] EBICS_X509_WRONG_ALGORITHM When verifying the certificate algorithm, the bank detects that the certificate is not issued for current use.
ESRVB091212 [b091212] EBICS_X509_INVALID_THUMBPRINT The thumb print does not correspond to the certificate.
ESRVB091213 [b091213] EBICS_X509_CTL_INVALID When verifying the certificate, the bank detects that the certificate trust list (CTL) is not valid.
ESRVB091214 [b091214] EBICS_X509_UNKNOWN_CERTIFICATE_AUTHORITY The chain cannot be verified because of an unknown certificate authority (CA).
ESRVB091215 [b091215] EBICS_X509_INVALID_POLICY The certificate has invalid policy when determining certificate verification.
ESRVB091216 [b091216] EBICS_X509_INVALID_BASIC_CONSTRAINTS The basic constraints are not valid when determining certificate verification.
ESRVB091217 [b091217] EBICS_ONLY_X509_SUPPORT The bank supports evaluation of X.509 data only.
ESRVB091218 [b091218] EBICS_KEYMGMT_DUPLICATE_KEY The key sent for authentication or encryption is the same as the signature key.
ESRVB091301 [b091301] EBICS_SIGNATURE_VERIFICATION_FAILED Verification of the electronic signature has failed.
ESRVB091302 [b091302] EBICS_ACCOUNT_AUTHORISATION_FAILED Preliminary verification of the account authorization has failed.
ESRVB091303 [b091303] EBICS_AMOUNT_CHECK_FAILED Preliminary verification of the account amount limit has failed.
ESRVB091304 [b091304] EBICS_SIGNER_UNKNOWN The signatory of the order is not a valid subscriber.
ESRVB091305 [b091305] EBICS_INVALID_SIGNER_STATE The state of the signatory is not admissible.
ESRVB091306 [b091306] EBICS_DUPLICATE_SIGNATURE The signatory has already signed the order.
(H005 protocol)
ESRVB090003		 [b090003] EBICS_AUTHORISATION_ORDER_IDENTIFIER_FAILED The subscriber is not entitled to submit orders of the selected administrative order type or the combination of BTF identifiers.
(H005 protocol)
ESRVB091115		 [b091115] EBICS_ORDERID_ALREADY_FINAL

The order number submitted using HVE or HVS cannot be matched.

Return codes for VEU

Table 7. Return codes for VEU
Return Code Event Message Summary
EBICSCL1050 Error while Unmarshalling the ResponseOrderData and persisting into DB Indicates that the response order data is not well-formed.

Return codes for console events

Table 8. Return codes for console events
Return Code Event Message Summary
EBICSCL9000 User created successfully The user profile was created successfully.
EBICSCL9001 User updated successfully The user profile was updated successfully.
EBICSCL9002 User deleted successfully The user profile was deleted successfully.
EBICSCL9003 User creation failed Creating of a user profile failed. This error may be the result of, for example, the user profile already exists or if the parameters in the user configuration have invalid values.
EBICSCL9004 User update failed Verify that the parameters for user configuration have valid values or if the connection to the database is down.
EBICSCL9005 User deletion failed Verify that the parameters for user configuration have valid values or if the connection to the database is down.

Return codes for login

Table 9. Return codes for login
Return Code Event Message Summary
EBICSCL9020 User Login was successful The user was successfully logged onto the system.
EBICSCL9021 and EBICSCL9022 User Login failed An attempt to log on to the hub was unsuccessful because of invalid user name or password or insufficient privileges.
EBICSCL9023 User does not have privilege to access the URI Verify that you have the correct permission and role to access the URI.
EBICSCL9024 The following features must be licensed as EBICS Client Obtain the license from IBM Support.

Return codes for file format

Table 10. Return codes for file format
Return Code Event Message Summary
EBICSCL9050 File format created successfully The file format was created successfully.
EBICSCL9051 File format updated successfully The file format was updated successfully.
EBICSCL9052 File format creation failed Verify that the parameters for file format configuration have valid values or if the connection to the database is down.
EBICSCL9053 File format update failed Verify that the parameters for file format configuration have valid values or if the connection to the database is down.
EBICSCL9054 File format deleted successfully The file format was deleted successfully.
EBICSCL9055 File format deletion failed Verify that the connection to the database is up or if the order type is associated with the appropriate file format.

Return codes for bank

Table 11. Return codes for bank
Return Code Event Message Summary
EBICSCL9070 Bank created successfully The bank profile was created successfully.
EBICSCL9071 Bank updated successfully The bank profile was updated successfully.
EBICSCL9072 Bank creation failed Verify that the parameters for bank configuration have valid values or if the connection to the database is down.
EBICSCL9073 Bank update failed Verify that the parameters for bank configuration have valid values or if the connection to the database is down.
EBICSCL9074 Bank deleted successfully The bank profile was deleted successfully.
EBICSCL9075 Bank deletion failed Verify that the connection to the database is up.
EBICSCL9076 Bank key validated successfully The bank key was validated successfully.
EBICSCL9077 Bank key validation failed The hash value received from the bank does not match the hash value stored in EBICS Client system.

Return codes for order submission

Table 12. Return codes for order submission
Return Code Event Message Summary
EBICSCL9090 Order submitted successfully The order was submitted successfully.
EBICSCL9095 Order submission failed A few of the reasons for the failure of order submission are, if the submitter does not have the required permission, if the certificates are not valid, if the validation of bank keys failed, and so on.

Return codes for offer

Table 13. Return codes for offer
Return Code Event Message Summary
EBICSCL9101 Offer created successfully The offer was created successfully.
EBICSCL9102 Offer creation failed Verify that the connection to the database is up.
EBICSCL9103 Offer updated successfully The offer was updated successfully.
EBICSCL9104 Offer update failed Verify that the connection to the database is up.
EBICSCL9105 Offer deleted successfully The offer was deleted successfully.
EBICSCL9106 Offer deletion failed Verify that the connection to the database is up.

Return codes for user permissions

Table 14. Return codes for user permissions
Return Code Event Message Summary
EBICSCL9120 User Permissions created successfully The user permission was created successfully.
EBICSCL9121 User Permissions creation failed Verify that the connection to the database is up.
EBICSCL9122 User Permissions updated successfully The user permission was updated successfully.
EBICSCL9123 User Permissions update failed Verify that the connection to the database is up.
EBICSCL9124 User Permissions deleted successfully The user permission was deleted successfully.
EBICSCL9125 User Permissions deletion failed Verify that the connection to the database is up.

Return codes for pending signature

Table 15. Return codes for pending signature
Return Code Event Message Summary
EBICSCL9141 Signature submitted The signature was submitted successfully.
EBICSCL9142 Signature submission failed Verify that the connection to the database is up or if the message was written successfully to the mailbox.
EBICSCL9143 Signature updated The signature was updated successfully.
EBICSCL9144 Signature update failed Verify that the connection to the database is up or if the message was written successfully to the mailbox.

Return codes for pending VEU signature

Table 16. Return codes for pending VEU signature
Return Code Event Message Summary
EBICSCL9151 VEU Signature submitted The VEU signature was submitted successfully.
EBICSCL9152 VEU Signature submission failed Verify that the connection to the database is up or if the message was written successfully to the mailbox.