CSM Reachability - Changes & Fixes
This page covers the changes and fixes provided to CSM Reachability IPF Release 2025.1.0
New
-
Added new Domain API endpoint for determining the processing entity responsible for the payment messages they handle.
-
/v2/determine-processing-entity
-
-
Added new configuration parameter for connector configuration
-
ipf.csm-reachability-api.connector.determine-processing-entity
-
Changed
-
Changed implementation so country code is made optional for identifierType = NCC for the following endpoints (before it was conditionally mandatory when identifierType = NCC )
-
/v2/party-entities
-
/v2/settlement-agents
-
/v2/select-csm-agents
-
/v2/validate-csm-reachability
-
/v2/validate-intra-entity-reachability
-
-
Search by and match by
BICidentifier is now changed to also match head office BICs and 8 character BICs.-
Head office BIC for an entity is usually an 8 character BIC followed by "XXX". It is possible that sometimes the payments or industry data may have this BIC presented as an 8 character BIC only while the data is held with "XXX" at the end (and vice versa). The BIC matching on reachability implementations now supports these scenarios.
-
This change affects:
-
Endpoints
/determine-processing-entity,/settlement-agents,/validate-csm-reachabilityand/validate-intra-entity-reachability. -
Search for
AgentSettings,Processing Entity,Intra Entity PartiesandCSM Participantsettings.
-
-
Data Ingestion
New
-
Added option to process DELTA Bank Directory Plus files on csm data ingestion service
-
Bank Directory Plus file has the following format: BANKDIRECTORYPLUS_XX_DELTA_YYYYMMDD.XML or BANKDIRECTORYPLUS_XX_FULL_YYYYMMDD.XML where XX is version number (currently V3)
-
Added option to process DELTA Tips Participant files on csm data ingestion service
-
TIPS Directory file has the following format: TIPSXXXDLTAYYYYMMDD.XML or TIPSXXXFULLYYYYMMDD.XML where XXX is alphabetic text