Skip to main content
Skip table of contents

API Errorcodes

The API uses a structured error code system that allows for the clear identification of the error that has occurred. Each error code follows a standardized format that indicates both the category and the specific identifier of the error. This structure enables quick error assignment and efficient troubleshooting.

Structure of Error Codes

The error codes follow the following schema:
ERR-{Category}-{Number}

  • ERR – A fixed prefix currently used for all error codes. This prefix was introduced to potentially support other message types, such as warnings, in the future (currently not available). It serves to clearly identify error messages and makes it easier to distinguish them from other codes or status messages.

  • {Category} – The category of the error, which describes the affected functional area or type of error. Examples of categories include AUTH for authentication errors, VALIDATION for validation errors, or SERVER for internal server errors.

  • {Number} – A unique number within the respective category. Each number is specific to a particular error and does not repeat within the same category.

This structured list of error codes allows for quick identification and efficient resolution of errors that may occur when using the API.

List of All Error Codes and Error Messages with Explanations

ERR-01-XXXX – Category: Invalid String Parameter

  • ERR-01-0001 - RIdNotFound: No resource was found for the given RId.

  • ERR-01-0002 - MsgIdNotFound: No resource was found for the given message identification.

  • ERR-01-0003 - AmbiguousMsgId: The given message identification is not unique.

  • ERR-01-0004 - InvalidMinDate: The specified minimum date is not a valid date.

  • ERR-01-0005 - InvalidMaxDate: The specified maximum date is not a valid date.

  • ERR-01-0006 - InvalidPeriod: The specified period is invalid (start date and end date must be chronological).

  • ERR-01-0007 - InvalidDate: The specified date is not a valid date.

  • ERR-01-0008 - TransactionIdNotFound: No resource was found for the given transaction ID.

  • ERR-01-0009 - InvalidTransactionId: The specified transaction ID is invalid (empty or longer than 19 characters).

  • ERR-01-0010 - AmbiguousTransactionId: The specified transaction ID is not unique.

  • ERR-01-0011 - EMailAddressOrMerchantIdNotFound: No resource was found for the given email address or merchant ID.

  • ERR-01-0012 - MissingParameter: A required parameter was not specified.

  • ERR-01-0013 - BankNotFound: The specified bank was not found.

  • ERR-01-0014 - InvalidGateway: The specified gateway is not supported. Only "SRZ," "EBICS," or a valid rId are allowed.

  • ERR-01-0015 - UnsupportedApiVersion: The specified API version is not supported for the requested resource.

  • ERR-01-0016 - InvalidQueryStringValue: The query string parameter contains an invalid value.

ERR-02-XXXX – Category: Content Validation Failed

  • ERR-02-0000 - ContentValidationFailed: Content validation failed. More information about the exact cause can be found in the error details.

  • ERR-02-0001 - InvalidRId: The specified RId is invalid (empty or not 36 characters long).

  • ERR-02-0002 - InvalidXmlCharacter: The file contains invalid characters according to the DFÜ agreement.

  • ERR-02-0003 - MissingXmlNamespace: The XML document does not contain a valid XML namespace.

  • ERR-02-0004 - InvalidXmlNamespacePrefix: The XML namespace prefix is invalid.

  • ERR-02-0005 - PainVersionNotSupported: The specified PAIN version is not supported by konfipay.

  • ERR-02-0006 - PainVersionReleaseDateNotReached: The PAIN version specified in the XML document is not (yet) valid.

  • ERR-02-0007 - SchemaValidationError: Validation of the XML document against the XML schema failed.

  • ERR-02-0008 - InitPartyIbanChecksumValidationFailed: The IBAN checksum of the ordering party account is invalid.

  • ERR-02-0009 - OtherPartyIbanChecksumValidationFailed: The IBAN checksum of the beneficiary account is invalid.

  • ERR-02-0010 - InvalidIbanIsoCountryCode: The ISO country code contained in the IBAN is invalid or not supported.

  • ERR-02-0011 - TransactionLimitExceeded: The maximum number of transactions allowed per payment order was exceeded.

  • ERR-02-0012 - LocalInstrumentMashup: The document contains more than one payment method.

  • ERR-02-0013 - InvalidServiceLevel: The specified service level is invalid (urgent payments are not allowed).

  • ERR-02-0014 - InvalidExecutionDate: The execution date is too far in the future or past.

  • ERR-02-0015 - InvalidInitiatingPartyIban: The bank account is not assigned to the user account or is inactive.

  • ERR-02-0016 - IbanBicMismatch: The bank code of the IBAN does not match the BIC of the financial institution.

  • ERR-02-0017 - ControlSumMismatch: The checksum specified in the header or a payment does not match the content.

  • ERR-02-0018 - NumberOfTransactionsMismatch: The number of transactions specified in the header or a payment does not match the content.

  • ERR-02-0019 - InvalidOtherPartyCountry: The beneficiary account is not located in a SEPA-participating country.

  • ERR-02-0020 - InvalidBankAccountIban: The IBAN checksum of the bank account is invalid.

  • ERR-02-0021 - InvalidBankAccountAdditionalInformation: The content exceeds the maximum length of 500 characters.

  • ERR-02-0022 - InvalidCreditorId: The structure of the creditor ID is invalid.

  • ERR-02-0023 - MissingRefundIdentifier: No identifier was specified for the refund (transaction ID or RId).

  • ERR-02-0024 - InvalidRefundMemo: The note specified for the refund is invalid (max. 255 characters).

  • ERR-02-0025 - InvalidRefundType: The specified refund type is invalid. Possible types: "Full" or "Partial."

  • ERR-02-0026 - MissingRefundAmount: The refund amount was not specified. The amount is required if the refund type is "Partial."

  • ERR-02-0027 - InvalidRefundAmountValue: The specified refund amount is invalid.

  • ERR-02-0028 - InvalidRefundAmountCurrency: The currency of the refund amount is invalid.

  • ERR-02-0029 - DtazvValidationFailed: Validation of the DTAZV file failed.

  • ERR-02-0030 - IbanValidationFailed: Validation of the IBAN failed.

  • ERR-02-0031 - InvalidBlz: The specified bank code is invalid.

  • ERR-02-0032 - ContainerVersionNotSupported: The container version specified in the XML document is not supported.

  • ERR-02-0033 - CamtVersionNotSupported: The CAMT version specified in the XML document is not supported.

  • ERR-02-0034 - InvalidValue: A field in the transmitted JSON or XML document contains an invalid value.

  • ERR-02-0035 - OtherPartyAddressRequired: For payment orders outside the EU with an amount > €1,000, the address must be provided.

  • ERR-02-0036 - DeprecatedLocalInstrument: The file contains the unsupported direct debit type "COR1." Only "CORE" and "B2B" are supported. Automatic conversion from "COR1" to "CORE" can be enabled in the API settings.

  • ERR-02-0037 - InvalidLocalInstrument: The file contains an invalid value in the "LocalInstrument" field for this payment type.

  • ERR-02-0038 - PaymentMessageIsNotUnique: The Message ID of the payment file must be unique. This optional check can be disabled in the API settings.

ERR-03-XXXX – Category: Content Not Readable

  • ERR-03-0001 - NoContentReceived: No content was transferred.

  • ERR-03-0002 - InvalidContentType: The specified content type of the transferred content is invalid.

  • ERR-03-0003 - InvalidFileStructure: The structure of the transferred file is syntactically invalid.

  • ERR-03-0004 - InvalidXmlDocument: The transferred content does not correspond to a well-formed XML document.

  • ERR-03-0005 - InvalidLoginCredentials: The syntactic structure of the login information is invalid.

  • ERR-03-0006 - InvalidBankAccount: The syntactic structure of the bank account information is invalid.

  • ERR-03-0007 - InvalidRefund: The syntactic structure of the refund information is invalid.

  • ERR-03-0008 - ContentNotReadable: The transferred text, JSON, or XML file does not have the expected structure.

ERR-04-XXXX – Category: Prerequisites Not Met

  • ERR-04-0001 - MissingScope: The API key used for authentication does not have the necessary permissions to access the requested resource.

  • ERR-04-0002 - SrzMappingFailed: Determining the service data center for submitting the payment file failed.

  • ERR-04-0003 - EbicsContactMappingFailed: No fully initialized EBICS contact was found for transmitting the payment file.

  • ERR-04-0004 - MissingEbicsOrderType: The EBICS contact does not have the order type required for the payment type.

  • ERR-04-0005 - InvalidEbicsContact: The EBICS contact for transmitting the payment file is not fully initialized or not configured to send payments.

  • ERR-04-0006 - InvalidPaymentStatus: The payment status is already set to "executed." A new execution is only possible if the force parameter is set to "true."

  • ERR-04-0007 - BankAccountIbanAlreadyExists: A bank account with the specified IBAN and currency already exists.

  • ERR-04-0008 - InactiveBankAccount: The bank account is deactivated in konfipay.

  • ERR-04-0009 - UnknownBankAccount: No bank account was found for the given IBAN.

  • ERR-04-0010 - AmbiguousRefundIdentifier: The identifier for the refund transaction is not unique.

  • ERR-04-0011 - DuplicateFound: The file was identified as a duplicate.

  • ERR-04-0012 - IndividualRestriction: The payment file cannot be accepted due to an individual restriction of the financial institution.

  • ERR-04-0013 - ClientBlocked: The client application was blocked by konfipay. More information about the exact cause can be found in the error details.

  • ERR-04-0014 - InsufficientPermissions: The client is not authorized to perform the requested action. More information about the exact cause can be found in the error details.

ERR-05-XXXX – Category: Processing Error

  • ERR-05-0000 - ProcessingError: An error occurred while processing the request. More information about the exact cause can be found in the error details.

  • ERR-05-0001 - EbicsError: An error occurred while performing the EBICS action.

  • ERR-05-0002 - PayPalError: An error occurred while performing the PayPal action.

  • ERR-05-0003 - PayPalUnspecifiedError: An unspecified error occurred during the execution of the PayPal action.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close