Skip to main content

Payments - v1.44.85

v1.44.85​

Release Dates

  • Sandbox: 30.03.2026

Features​

Feature flag implementation for SEPA 2025 rulebook changes​

Feature flag added to control the rollout of SEPA 2025 rulebook compliance updates. The flag is initially disabled, allowing controlled activation of the new payment processing capabilities.

Enhanced camt.056 processing for SEPA 2025 naming conventions​

Incoming camt.056 payment cancellation messages now support shortened naming convention references. The system processes camt.056 messages where OrgnlMsgNmId references "pacs.008" instead of the full version format "pacs.008.001.0X", while maintaining backward compatibility with existing full version references.

Enhanced pacs.004 processing for SEPA 2025 naming conventions​

Incoming pacs.004 payment return messages now support shortened naming convention references. The system processes pacs.004 messages where OrgnlMsgNmId contains "pacs.008" instead of the full version format, enabling proper reconciliation with original payments while maintaining backward compatibility.

Enhanced pacs.002 processing for SEPA 2025 naming conventions​

Incoming pacs.002 payment status messages now support shortened naming convention references. The system processes pacs.002 messages where OrgnlMsgNmId contains "pacs.008" instead of the full version format "pacs.008.001.08" or "pacs.008.001.09", enabling correct linking to original payment instructions while maintaining backward compatibility.

Relaxed validation for incoming pacs.009 debtor account requirements​

Incoming pacs.009 FI-to-FI transfer messages no longer require debtor account ID validation. The system now processes incoming pacs.009 payments and books them in CBE even when the debtor account ID field is missing, while maintaining all other existing validations. Creditor account ID remains mandatory for successful processing.

Improvements​

Enhanced Kafka Event Handling for SEPA Credit Transfer Processing​

Implemented comprehensive logging and duplicate mitigation measures for SEPA CT outgoing payments (pacs.008) processing. Added detailed logging to InitiateSettlementHandler for complete event tracking and introduced unique indexing on (aggregate_id, type) in the event table to prevent duplicate Kafka event consumption that could result in duplicate XML messages to customers.

Default Configuration for Incoming Direct Debit Retry Processing​

Resolved NullPointerException in AML processing for incoming SEPA Direct Debit (SDD) transactions. The system now handles missing incomingDirectDebitRetryDays system property configuration by implementing appropriate default values or alerts, ensuring uninterrupted AML result processing flow.

Updated IBAN Plus Directory Integration​

Retrieved and integrated the latest IBAN Plus file from SWIFT network (swift.com) in XML format. This update ensures current IBAN validation data is available for payment processing and compliance verification.

Enhanced Exception Logging for Outgoing Direct Debit Scheduler​

Improved diagnostic capabilities for OutgoingDDScheduler by adding complete stack trace logging. This enhancement facilitates faster issue resolution and reduces alert noise by providing detailed context for exception handling.

Bug fixes​

Fixed SQL query error in SEPA block header retrieval​

The SQL query in SepaRepository for retrieving SEPA block headers has been corrected. The query now properly includes the missing parameter binding for INSTGAGT_GEN field, ensuring accurate retrieval of SEPA block header sequence numbers based on message ID, message name ID, input/output block type, and instructing agent generation parameters.

For more information on the release timeline, see Mambu Release Cycle.

Last updated on