Core - Changes & Fixes

This page details everything required to get going on IPF Release 2025.4.0

New

Payment Warehouse Datasource

Payment Warehouse can be used as a source of Payment data for the Payment Entries Processor (Payment Releaser). When this is the case, besides the existing BasePaymentWarehouseDataSource (now renamed to AggregateEntriesWarehouseDataSource) Datasource implementation, a new implementation is also available - LatestEntryWarehouseDataSource. (PAY-15784)

LatestEntryPaymentDatasource will fetch only the latest Payment Entry related to the required Payment Initiation/Instruction/Transaction. It should be used when a Payment Warehouse Entry representing the adjusted Payment Message contains the full message payload, including the original message and all the changes made up to now applied to it.

Mapping Framework

New configuration property added to allow for disabling Orika Auto Mapping Behaviour (default is true, as per previous release) (PAY-14687)

ipf.orika.transformations.use-auto-mapping = true

IPF Processing Data

Two headers have been added to the Egress Payload and are supported by the Ingress modules. (PAY-15757)

Header Value Notes

ipf_schema_name

DataEnvelope

ipf_schema_Version

1 or 2

Derived from the value configured for ipf.processing-data.egress.schema-version.
If not configured, defaults to 2
The payload will also contain the now deprecated header schema-version.
The final IPF release that will support this header is 2026.4, it will not be supported in IPF release 2027.1.
While supported, the payload will include both ipf_schema_version and schema-version headers, and they will have the same value.
If using a custom implementation to consume IPF Processing Data, you will need to update to the latest headers before support is withdrawn. See the consuming IPF Processing Data documentation for more information.

Changed

Connectors

  • The jms.default-consumer.max-pending-acks Jms Receive Transport config param now has value 0 by default. This is required for JmsAckReceiveConnectorTransport to be able to achieve at-least-once message delivery guarantees. For more details, see: JMS Quickstart

Payment Warehouse Datasource

  • BasePaymentWarehouseDataSource Datasource implementation renamed to AggregateEntriesWarehouseDataSource