Skip to main content

Payments - v1.44.89

v1.44.89​

Release Dates

  • Sandbox: 30.03.2026

Features​

Internal Processing SLA for Outgoing Instant Payments​

MPG now enforces a strict 5-second internal processing window for outgoing SEPA Instant Payments. When you initiate a payment via API, MPG monitors the complete internal flow (message creation, AML checks, fund reservation) and automatically cancels the payment if processing exceeds 5 seconds. The system uses payment message timestamps as reference and removes any created reservations during cancellation. You will receive immediate notification if a payment is cancelled due to timeout, with the payment status updated to "cancelled".

Timeout Handling for Outgoing Instant Payments​

MPG automatically releases fund reservations for outgoing SEPA Instant Payments if no pacs.002 confirmation is received within 10 seconds. The payment remains in "pending-settlement" status. If a late pacs.002 arrives after the 10-second window, MPG processes it immediately: rejections follow standard behavior, while acceptances trigger direct account debiting without reservation. If insufficient funds are available, MPG debits your pre-configured process account. Event notifications are sent at the 12-second mark and upon final payment resolution.

Configuration of Instant Payment SLA Timer​

MPG now enforces a 5-second processing timer for incoming SEPA Instant Payments to ensure scheme SLA compliance. The system validates timestamps from incoming pacs.008 messages and must complete all processing within 5 seconds. Successful processing within the window creates account bookings and sends positive pacs.002 (ACCP) responses. If the 5-second window is exceeded, MPG prevents booking creation and immediately sends a pacs.002 reject message with appropriate timeout reason codes.

Regulatory Change: LEI Code Addition to Processing Logic​

MPG now captures and stores Legal Entity Identifier (LEI) codes from the Ultimate Debtor field in incoming pacs.003 messages. The system parses LEI data from the CdtTrfTxInf/UltmtDbtr/Id/OrgId/LEI path in pacs.003.001.08 messages and associates it with the specific payment transaction. Stored Ultimate Debtor LEI information is accessible through the Payment Details API and included in Instructions API responses, enhancing transparency for regulatory and analytical requirements.

Improvements​

Enhanced validation and performance improvements for /api/v1/instructions endpoint​

Implemented comprehensive validation layer and performance optimizations for the /api/v1/instructions endpoint. Added validation for non-existent filters with 400 error responses, mandatory filter combinations requiring both dateFrom and dateTo parameters to be either filled or empty, and requirement that dateFrom/dateTo must include one of messageId, messageType, or paymentsId. Enhanced query performance with pre-counting mechanism for large result sets and appropriate response handling.

Optimized SEPA Instant settlement processing flow​

Removed timeout validation in the internal transaction credit settlement handler for SEPA Instant payments. The system now processes settlement requests without timeout checks after sending positive ACCP pacs.002 responses, streamlining the settlement flow for AML-approved instant credit transfers and improving processing efficiency for asynchronous settlement operations.

Updated IBAN Plus directory integration​

Retrieved and integrated the latest IBAN Plus file from SWIFT network in XML format. Updated directory references to ensure accurate IBAN validation and routing for international payment processing, maintaining compliance with current SWIFT standards and improving payment instruction accuracy.

Validation framework implementation for /api/v1/instructions endpoint​

Deployed enhanced validation framework for the /api/v1/instructions endpoint with feature toggle controls. Implemented filter validation layer, mandatory parameter combinations for dateFrom/dateTo fields, and query performance improvements. Feature toggle enabled in sandbox environment with planned production deployment following customer testing period to ensure backward compatibility.

Bug fixes​

Instruction endpoint now correctly processes camt.029.001.08 and camt.027.001.06 bulk transactions​

Fixed issue where the instruction endpoint was ignoring specific CAMT message types (camt.029.001.08 and camt.027.001.06) during bulk transaction processing. This was causing incomplete batch returns where expected record counts did not match actual returned records, leading to premature batch termination in downstream processing jobs.

Authorization hold settlement now correctly handles insufficient funds after pacs.002 timeout​

Resolved BALANCE_BELOW_ZERO error that occurred when pacs.002 messages arrived after timeout expiration and the debited account had insufficient funds. The system now properly settles transactions by debiting the suspense account instead of failing with "Authorization Hold Settlement Failed" status.

AML response timeout handling improved for outgoing instant payments​

Fixed timing issue in outgoing instant payment flow where authorization holds were incorrectly released when AML results arrived after the 5-second internal processing timeout. The system now properly manages fund release timing based on the actual timeout threshold rather than AML response arrival time.

Event tenant assignment corrected in external gateway​

Resolved issue where incoming events were persisted with incorrect tenant information, causing events to be stored in one schema while generated events were published to a different tenant's topic. Tenant ID determination and persistence now maintain consistency throughout the event processing pipeline.

Gateway visibility restored for pacs.028 messages with short originalMessageNameId​

Fixed issue preventing pacs.028 messages with abbreviated originalMessageNameId values from appearing in the gateway interface.

Incoming instant pacs.002 error handling standardized for invalid originalMessageNameId​

Corrected inconsistent behavior when processing incoming instant pacs.002 messages with invalid originalMessageNameId values (e.g., "pacs.123"). The system now properly saves notifications with appropriate failure causes instead of triggering unhandled alerts, aligning with standard pacs.002 processing behavior.

Bulk transaction instruction endpoint processing enhanced for CAMT message types​

Addressed missing transaction records in bulk processing where camt.029.001.08 and camt.027.001.06 messages were not being mapped to final API response objects. This ensures complete batch processing and accurate record counts for downstream systems.

Alert messaging improved for pacs.002 invalid original message ID errors​

Enhanced error message clarity when pacs.002 messages contain invalid or shortened original message name IDs. Alert messages now properly display the actual originalMessageNameId value instead of showing "null" references, improving troubleshooting capabilities.

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

Last updated on