Skip to main content

Payments - v1.44.93

v1.44.93​

Release Dates

  • Sandbox: 30.03.2026

Improvements​

Updated pacs.009 scheduler timing configuration for production environment​

Updated the pacs.009 scheduler timing configuration for the outgoing-financial-institution-credit-transfer-ISO20022 scheduler in production. The scheduler now operates from 4:00 to 14:45 UTC starting March 27, 2026 EOB, modified from the previous 5:00 to 15:45 UTC timeframe.

Updated pacs.009 scheduler timing configuration with dual timeframe support​

Updated the pacs.009 scheduler timing configuration for the outgoing-financial-institution-credit-transfer-ISO20022 scheduler in production to support dual operational timeframes. The scheduler operates from 5:00 to 15:45 UTC starting Monday October 27, and from 4:00 to 14:45 UTC prior to Sunday October 26, with automatic transitions on October 23rd and October 26th.

Fixed GET instruction API error for incoming camt.027 messages​

Resolved a SERVICE_INVALID error occurring when calling GET /api/v1/instructions?direction=I&messageId= for incoming camt.027 messages. The fix addresses the NoSuchMethodException for ClaimNonReceiptV06.getClmNonRct() by correcting the FIELDPATH handling in the Camt027MessageBuilder for incoming messages, which previously saved paths with /ClmNonRct/ prefix while outgoing messages did not.

Scaled up production environment resources​

Increased resource allocation and scaling configuration for the production environment to support enhanced performance and capacity requirements.

Completed impact assessment for payment batch booking process enhancement​

Delivered feasibility and impact assessment for implementing partial settlement functionality in payment batch processing. The assessment covers the technical effort and operational impact of allowing payment batches (R-messages) to proceed with partial booking when individual payments contain errors, particularly incorrect original message IDs, while marking faulty transactions and sending appropriate notifications.

Updated payment component library with postal address validation fix​

Updated the payment component library to resolve validation errors with hybrid postal address formatting. The fix addresses SEPA_EPC_INST002 validation failures that occurred when postal addresses contained both structured elements (PstCd, TwnNm, Ctry) and unstructured elements (AdrLine) in hybrid format configurations.

Replaced deprecated organization settings API with internal configuration​

Replaced the deprecated /api/settings/organization endpoint with internal tenant-specific configuration for setting value dates in backdated transactions. This change addresses API V1 access restrictions and ensures proper timezone handling through internal configuration mapping rather than external API calls.

Created timezone configuration mapping for multi-environment support​

Implemented TIME_ZONE_ID_MAP configuration mapping across all environments to support tenant-specific timezone settings. The configuration retrieves timezone values from the tenant.organization_view table and maps them per environment, enabling proper timezone handling for payment processing operations.

Updated payment component library with postal address validation improvements​

Applied the latest payment component library update that includes fixes for postal address validation issues. This update resolves hybrid postal address format validation errors where combinations of structured and unstructured address elements previously triggered SEPA_EPC_INST002 validation failures.

Replaced deprecated organization API with timezone configuration mapping​

Implemented internal timezone configuration mapping to replace calls to the deprecated /api/settings/organization endpoint. The new configuration uses tenant-specific timezone settings retrieved from the organization database, ensuring proper timezone handling for backdated transaction value date calculations without relying on deprecated API endpoints.

Updated payments component library to latest version​

Updated the payments component library to the most recent version, incorporating the latest fixes and improvements for payment processing functionality.

Enhanced ps-scheduler logging for improved operational visibility​

Added comprehensive logging to the ps-scheduler component to provide better operational visibility and troubleshooting capabilities for payment scheduling operations.

Bug fixes​

Fixed null pointer exception in camt.027 message processing when transaction list is empty​

Resolved a critical error that occurred when processing camt.027 messages with empty transaction lists. The instruction endpoint now properly handles cases where no transaction details are available, preventing system failures during message processing.

Fixed instruction endpoint error for pacs.004 bulk message processing​

Corrected a 500 error in the instruction endpoint when processing pacs.004 bulk messages. The fix addresses message type routing issues that occurred after the 2025 regulatory changes, where pacs.003.001.08 messages were incorrectly processed as pacs.008 format, and resolves the missing getAmdmntInd() method exception.

Fixed outgoing instant payment rejection logic for insufficient funds scenarios​

Corrected the payment flow for outgoing instant credit transfers when positive pacs.002 confirmations arrive after the 10-second timeout and insufficient funds exist in both debtor and default accounts. Payments now remain in pending_settlement status instead of being incorrectly rejected, with proper notification mechanisms for fund shortage situations.

Fixed settlement date assignment for pacs.009 payments processed after cut-off time​

Resolved an issue where outgoing pacs.009 FI-to-FI payments processed outside scheduled hours were assigned incorrect settlement dates. The system now properly manages cut-off time enforcement to prevent processing of pacs.009 transfers beyond scheduler boundaries.

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

Last updated on