Skip to main content

Payments - v1.44.88

v1.44.88​

Release Dates

  • Sandbox: 30.03.2026

Features​

Enforced Single Outgoing Recall Request for SEPA Instant Payments​

MPG now enforces compliance with SEPA scheme rules by allowing only one recall request (camt.056) per original SEPA Instant Payment (pacs.008). When attempting to initiate a second recall for the same transaction, the system will reject the request with a clear error message: "A recall request has already been sent for this payment." The API will return a 400 Conflict response for duplicate recall attempts, while successful first-time recalls receive standard success responses. This enforcement operates on a per-transaction basis, allowing separate recalls for different payments while maintaining scheme compliance.

Updated Timestamp Handling for Outgoing SEPA Instant Payments (pacs.008)​

Outgoing pacs.008 Instant messages now capture timestamps at the moment MPG receives the payment creation API call, rather than when the message leaves the payment engine. This change ensures compliance with SEPA 2025 rulebook requirements for the 10-second processing window. The AccptncDtTm field now uses millisecond precision with the format pattern: [0-9]4(-[0-9]2)2T[0-9]2(:[0-9]2)2 (\.[0-9]2[1-9])?(Z|([-+][0-9]2(:[0-9]2)?)). Example format: 2025-08-11T15:43:05.789+02:00.

Enhanced Processing for Incoming pacs.028 Messages with Shortened Naming Convention​

MPG now processes incoming pacs.028 status inquiry messages that reference original payment instructions using shortened naming conventions in the OrgnlMsgNmId field (e.g., "camt.056" instead of "Camt.056.001.0X"). This update ensures compatibility with SEPA 2025 rules while maintaining backward compatibility with existing full naming convention formats. The system successfully validates and links these messages for efficient status inquiry handling.

Enhanced Processing for Incoming camt.029 Messages with Shortened Naming Convention​

MPG now correctly processes incoming camt.029 payment cancellation resolution messages that reference pacs.008 Instant payments using shortened naming conventions in the OrgnlMsgNmId field (e.g., "pacs.008" instead of "pacs.008.001.0X"). This enhancement ensures compliance with SEPA 2025 rulebook requirements for handling cancellation request resolutions while maintaining full backward compatibility with existing naming convention formats.

Bug fixes​

Fixed null pointer exception in camt.056 additional information processing​

Resolved a critical issue where empty additional information fields in incoming camt.056 cancellation requests caused null pointer exceptions during camt.029 response generation. The fix ensures proper handling of transactions when additional info is not populated, preventing system crashes in the authorize/deny workflow through the /authorize/deny endpoint.

Corrected inbound message validation for camt.056 OrgnlMsgNmId field​

Fixed validation logic for the OrgnlMsgNmId field in inbound camt.056 messages to properly handle invalid short message name identifiers. This resolves scenario 6.3 validation failures and ensures compliant processing of cancellation request messages.

Enhanced camt.056 to camt.029 transaction flow error handling​

Improved error handling in the OutgoingScheduler for instant payment cancellation rejections when processing camt.056 messages with missing additional information. The fix prevents null pointer exceptions in both InstantCamt029V3Translator and Camt029V3Translator when generating outgoing camt.029 responses for transactions in TO_BE_REJECTED state.

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

Last updated on