Skip to main content

Payments - v1.44.86

v1.44.86​

Release Dates

  • Sandbox: 30.03.2026

Features​

Enhanced pacs.007 Message Processing with SEPA 2025 Shortened Naming Convention​

MPG now processes incoming pacs.007 return messages that reference original pacs.003 transactions using the shortened naming convention "pacs.003" in the OrgnlMsgNmId field. This update ensures compliance with SEPA 2025 rulebook requirements while maintaining backward compatibility with full version naming (pacs.003.001.0X). The system correctly reconciles returns with original SEPA Credit Transfer transactions and handles unlinked returns through established procedures.

Enhanced pacs.004 Message Processing with SEPA 2025 Shortened Naming Convention​

MPG now processes incoming pacs.004 return messages that reference original pacs.003 transactions using the shortened naming convention "pacs.003" in the OrgnlMsgNmId field. This enhancement supports SEPA 2025 compliance for SEPA Direct Debit returns while preserving backward compatibility with existing full version references. The system maintains proper reconciliation with original transactions and applies standard handling for unlinked returns.

Enhanced pacs.002 Status Report Processing with SEPA 2025 Shortened Naming Convention​

MPG now processes incoming pacs.002 status report messages that reference original pacs.003 transactions using the shortened naming convention "pacs.003" in the OrgnlMsgNmId field. This update enables proper linking of status reports to original SEPA Direct Debit instructions in accordance with SEPA 2025 rulebook requirements. The system maintains backward compatibility with full version naming and implements appropriate error handling for invalid references.

MPG now captures and stores Legal Entity Identifier (LEI) codes from the Ultimate Debtor field (CdtTrfTxInf/UltmtDbtr/Id/OrgId/LEI) in incoming pacs.008 messages. Stored LEI data is accessible through the Payment Details API and included in Instructions API responses, enhancing transaction transparency and supporting regulatory compliance requirements for ultimate fund originator identification.

Enhanced camt.087 Payment Modification Processing with SEPA 2025 Shortened Naming Convention​

MPG now processes incoming camt.087 payment modification request messages that reference original pacs.008 transactions using the shortened naming convention "pacs.008" in the OrgnlMsgNmId field. This enhancement ensures compliance with SEPA 2025 rulebook requirements while maintaining backward compatibility with full version references (pacs.008.001.0X). Payment modification requests are handled according to established business rules.

Enhanced camt.029 Resolution Processing with SEPA 2025 Shortened Naming Convention​

MPG now processes incoming camt.029 resolution messages that reference original pacs.008 transactions using the shortened naming convention "pacs.008" in the OrgnlMsgNmId field. This update supports SEPA 2025 compliance for payment cancellation request resolutions while maintaining backward compatibility with full version naming. The system properly evaluates and actions cancellation requests according to business rules.

Enhanced pacs.028 Status Inquiry Processing with SEPA 2025 Shortened Naming Convention​

MPG now processes incoming pacs.028 status inquiry messages that reference original messages using shortened naming conventions (e.g., "camt.056") in the OrgnlMsgNmId field. This enhancement ensures proper validation and linking of status inquiries under SEPA 2025 rules while maintaining backward compatibility with full version references (camt.056.001.0X). Status requests are processed efficiently with appropriate validation and linking capabilities.

Improvements​

Enhanced Payment Data Sanitization for Pacs.003 Messages​

Payment details validation now includes comprehensive sanitization before database storage. The system validates and removes illegal characters from incoming payment data, particularly in /DrctDbtTxInf/RmtInf fields, and generates alerts when non-compliant characters are detected. This ensures compliance with SEPA extended character set requirements.

Improved Rejection Code Accuracy for Closed Account Payments​

Incoming payments failing due to closed accounts now return the correct AC04 rejection code instead of the generic AC06 code. The system performs additional account state validation via GET /api/deposits/{accountId} and adds an optional errorSource field to ApiError events (CreditTransactionFailed, FailPaymentOrder, PaymentOrderFailed) to distinguish between closed and blocked account states without altering customer-facing information.

Updated IBAN Plus Directory Integration​

IBAN Plus file retrieval process has been updated to access the latest monthly flat files from SWIFT's download area. The system now retrieves XML format files from the most recent available date through the SWIFTRef portal.

Payment Data Sanitization for Pacs.003 Processing​

Incoming payment processing now includes validation and sanitization of payment details before database storage. The parseAndValidate method in IncomingScheduler.processPacs003 removes illegal character sequences and creates alerts for non-compliant data, ensuring adherence to SEPA character set standards.

IBAN Plus File Retrieval Process Enhancement​

Monthly IBAN Plus file download process has been streamlined for accessing flat files through SWIFT's MySwift portal. The system now supports automated retrieval of XML format files from the SWIFTRef download area with improved file selection for the most current monthly datasets.

Accurate Rejection Codes for Failed Account Transactions​

Payment rejection handling now uses appropriate reason codes based on actual account states. The system distinguishes between closed (AC04) and blocked (AC06) accounts by performing additional validation calls and enriching transaction events with account state information, improving payment processing accuracy while maintaining backward compatibility.

Bug fixes​

Fixed transaction identification in incoming pacs.028 messages to prevent incorrect recalls​

Resolved issue where incoming pacs.028 transactions were identified only by txId and msgNmId, which could result in incorrect transaction recalls. Transaction identification now uses the complete key set: MSGNMID, TXID, DBTRAGT, STTLDT, INOUTTRN to ensure unique identification across multiple originator banks.

Resolved NullPointerException in AML processing when Debtor Account is missing in Pacs 009​

Fixed AcceptCustomerProfile handler error that occurred when processing Pacs 009 messages without Debtor Account information. The system now properly handles missing debtor account data during AML result processing without throwing NullPointerException.

Enhanced transaction identification for incoming pacs.028 messages in external gateway​

Improved transaction identification logic for incoming scheduler pacs.028 messages by expanding identification parameters beyond txId and msgNmId. Transactions are now identified using MSGNMID, TXID, DBTRAGT, STTLDT, INOUTTRN to prevent duplicate key conflicts between originator banks and ensure accurate transaction recall operations.

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

Last updated on