Merge branch 'main' into SRU2024

CHANGELOG.md

@@ -1,6 +1,7 @@
 # Prowide Core - CHANGELOG
 
 #### 9.5.3 - SNAPSHOT
+  * (PW-2040) Updated the BBAN validation data file to the IBAN REGISTRY Jul 2024 release 
   * (PW-2006) Fixed `getMUR` and `setMUR` in `SwiftMessage` to prioritize field 108 in block 4 over block 3 for system messages (category 0)
   * Added new `MtSequenceEnum` with all the available inner sequences of specific MT schemas
   * Added `isSystemMessage()` to SwiftMessage to check if the message is a category 0 message (010. 011, etc...)

src/main/java/com/prowidesoftware/swift/model/IbanValidationResult.java

@@ -42,7 +42,7 @@ public enum IbanValidationResult {
     INVALID_CHARACTERS("Invalid character '${found}' found"),
     MISSING_CHECK_DIGITS("Missing check digits"),
     INVALID_CHECK_DIGITS_FORMAT("Expected 2 check digits and found ${found}"),
-    IVALID_CHECK_DIGITS("The expected computed check digit is ${expectedCheckDigit} and ${found} was found"),
+    INVALID_CHECK_DIGITS("The expected computed check digit is ${expectedCheckDigit} and ${found} was found"),
 
     MISSING_BBAN("Missing custom account number (BBAN)"),
     BBAN_MAX_LENGTH(

src/main/java/com/prowidesoftware/swift/model/IbanValidationUtils.java

@@ -214,7 +214,7 @@ static IbanValidationResult validateCheckDigit(final String iban) {
         if (calculateMod(iban) != 1) {
             final String checkDigit = IBAN.getCheckDigits(iban);
             final String expectedCheckDigit = calculateCheckDigit(iban);
-            IbanValidationResult result = IbanValidationResult.IVALID_CHECK_DIGITS;
+            IbanValidationResult result = IbanValidationResult.INVALID_CHECK_DIGITS;
             result.setExpectedCheckDigit(expectedCheckDigit);
             result.setFound(checkDigit);
             return result;