Error codes description

Version 5.2
WS applied for: initSession

STATUS Code (V5.1) Error Code Description Code (V5.2) Current Message
ACCT OK OK OK SPS-SIGN Session has been created
RJCT AUTH_FAILED Authentication Error AUTH_FAILED Certificate does not match the one saved in SPS-SIGN
INTERNAL_ERROR INTERNAL_ERROR INTERNAL_ERROR An internal error occurred when creating or validating the session/ Unknown error
INSUFFICIENT_IDENTIFICATION INSUFFICIENT_IDENTIFICATION INSUFFICIENT_IDENTIFICATION Used for the authentification criteria for SIPS
CONFIG_ERROR CREDITOR_ERROR SIGN_ERR_001 No creditor Idenfitifer for [" + creditorId + "] was found.
Tx No." + creditorTxId + " already exists for creditor " + creditorConfig.getIdentifier()
No session archive found for (creditor:" + id + "/transactionId:" + transactionId + ")
Mandate update option is not active for your creditor.
CONFIG_ERROR SIGN_ERR_002 Simple Address Exception has been thrown!
Merger has failed
Service Id pour OTU Configuration is null!
Invalid URL
Incomplete config
SIGNER_ERROR SIGN_ERR_003 SignerInfo cannot be null
SIGN_IDENTIFICATION_ERROR SIGN_ERR_004 Only one Identification must be entered (either SignerInfo or SubjectInfo tag)
One TAG identification is mandatory for OTU Signature Method (SignerInfo or SubjectInfo tag)
An error has been detected when validating the request. Please check the criteria block [" + e.getIdentificationBlockCriteria() + "
An error has been detected when validating when checking the authentication criteria
SCI_ERROR SIGN_ERR_005 Invalid SCI
Invalid SCI " + sci + " sci known: " + creditorConfig.getBaseConfig().getSci()
SCI is missing. SCI is required for this particular case, the Creditor has several SCI :
BANK_ACCOUNT_ERROR SIGN_ERR_006 Invalid IBAN
IBAN cannot be null
BIC cannot be null
BankAccount cannot be null
The BIC is not Provided
The IBAN is not Provided
The BIC retrieved for the IBAN [" + iban + "] is not Valid
The IBAN [" + iban + "] is not Valid
The Bic / IBAN for debtor are invalid.
The BIC retrieved from the IBAN [" + iban + "] is not Reachable
The IBAN [" + iban + "] is in Exclusion List of SWIFT
Invalid BBAN
The BBAN is not valid
Invalid Debtor Country Code
Invalid BBAN Country Code. Must be ISO Format
The BIC is not Provided
The IBAN is not Provided
The BIC retrieved for the IBAN is not Valid
The IBAN retrieved is not Valid
The Bic / IBAN for debtor are invalid.
The BIC retrieved from the IBAN is not Reachable
The IBAN retrieved is in Exclusion List of SWIFT
The BBAN is not Valid
The BBAN is not provided
The BBAN country code is not provided
SCHEDULE_ERROR SIGN_ERR_007 Invalid Config. Imposible to set variableSchedule and periodicSchedule at the same time. Please chose only one Schedule
Invalid Config. Imposible to use a schedule
PARAMETER_ERROR SIGN_ERR_008 The attachment configuration is not active for your organisation
SUBJECT_INFO_ERROR SIGN_ERR_009 Subject informations is required for criteria authentication
CONTRACT_INFO_ERROR SIGN_ERR_010 Max length of the contract Id must not exceed
Max length of the contract Description must not exceed
TRANSACTION_ERROR SIGN_ERR_011 Max length of the transaction Id must not exceed
PERSONAL_INFO_ERROR SIGN_ERR_012 The First Name and the Gender are mandatory for OTU Signature Method
Ultimate debtor name must be set if ultimate debtor id is set
FirstName cannot be null
FirstName cannot be null (it should be last name)
Phone cannot be null
Email cannot be null
Invalid Config. Language length must be 2. Must be ISO Format
Invalid Phone Number
The Phone Number [" + userPhone + "] was not considered as a valid Mobile Number
Invalid Email
Max length of the ultimate debtor name must not exceed
Max length of the ultimate debtor Id must not exceed
ADDRESS_ERROR SIGN_ERR_013 BldngNm cannot be null
StrtNm cannot be null
PstCd cannot be null
City cannot be null
Ctry cannot be null
PostalAddress cannot be null
Debtor Address is not complete
The Debtor Country Code is not valid. Must be ISO Format
COMPANY_ERROR SIGN_ERR_014 The company name is mandatory for a B2B Mandate
The company name is mandatory for a B2B Mandate
The corporate indicator must be set to true with a B2B Mandate
The company name is mandatory for Core Enterprise Mandate
AMOUNT_ERROR SIGN_ERR_015 Invalid Config. First payment amount must be set to 0 for a Payment agreement method with an Authorization CaptureMode
Invalid Config. First payment amount must not be null for a Payment agreement method
Invalid Config. First payment amount must be a positive value
MANDATE_ERROR SIGN_ERR_016 Mandate not found
Invalid UIR
Invalid UMR
Mandate is not editable (Revoked, Deleted)
ACCESS_ERROR SIGN_ERR_017 the logged in user does not have right access on mandate user
INCORRECT_ORG_ERROR SIGN_ERR_018 Organization mentioned in creditro does not exist
DOCUMENT_SIGN_ERROR SIGN_ERR_019 documentSignatureType, documentId, documentName and documentFile are required for sessionDocumentSignature
RJCT
DOCUMENT_RETRIEVE_ARCHIVE_ERROR SIGN_ERR_021 Unable to recuperate Archive Information
Unable to read data retreived from archiving
DOCUMENT_SIGN_ERROR SIGN_ERR_025 Incompatible Agreement Method
SIGN_ERR_026 Payment type not supported (20.2)
SIGN_ERR_027 SCI and UMR and UIR should not be null when reuse mandate
SIGN_ERR_028 Creditor-Cancelable state was excepted, got another state
SIGN_ERR_029 Creditor Bank Account is not found inside creditor Organization in SPS
STRONG_CUSTOMER_AUTHENTICATION ERROR SIGN_ERR_032 Creditor is not allowed to use SCA
With SCA option authorization, we cannot skip first page
RJCT WRONG_VALUE IN_ENUM_FIELD SIGN_ERR_033 Wrong value was put in at least an enum field (agreementScheme or mandateType for example)
RJCT DOCUMENT_RETRIEVE_ARCHIVE_ERROR SIGN_ERR_021 Unable to recuperate Archive Information
Unable to read data retreived from archiving
DOCUMENT_SIGN_ERROR SIGN_ERR_025 Incompatible Agreement Method
SIGN_ERR_026 Payment type not supported (20.2)
SIGN_ERR_027 SCI and UMR and UIR should not be null when reuse mandate
SIGN_ERR_028 Creditor-Cancelable state was excepted, got another state
SIGN_ERR_029 Creditor Bank Account is not found inside creditor Organization in SPS
STRONG_CUSTOMER_AUTHENTICATION ERROR SIGN_ERR_032 Creditor is not allowed to use SCA
With SCA option authorization, we cannot skip first page