4. /determine-processing-entity

The industry identifier used for determining processing entity is checked for presence on two dynamic configurations, "Processing Entity" and "Generic Processing Settings - Intra Entity Parties". This is referred to as "Standard Processing entity derivation". The industry identifier is the identifier of the party on the message that the CSM service or the client flow has determined to be processing entity (e.g. it can be a BIC or national clearing code that belongs to InstdAgt, InstgAgt, DbtrAgt or CdtrAgt) and included on the input request to the endpoint /determine-processing-entity.

While determining the processing entity this way, the service can also refer to industry data through IBAN deconstruction or "Party Entity Directory" look up to get the required type of identifier associated with the provided input value so processing entity can be determined even if Intra Entity Parties does not register the provided type of identifier (e.g. A processing entity has registered intra entity parties using BIC values but the determine processing entity request is made with a National Clearing code. In these cases, the service can derive the BIC associated with the national clearing code using industry data available on party entity directory. This derived BIC value is then used to determine processing entity using BICs available on intra entity parties)

Standard processing entity determination is executed for a request when the deriveDirectParticipant flag is set to FALSE or the flag value is not set on the input (default value FALSE).

In most cases, inbound messages processed by CSM service contain the direct participant (e.g. in InstdAgt) and this can be used to determine processing entity using "Standard Processing Entity Determination" (as explained above).

However, some CSMs may not include the identifier of the direct participant on inbound messages. In these cases, the CSM service processing the inbound payment may want to derive the direct participant associated with the CdtrAgt first and then determine the processing entity using the identifier of the direct participant. This would allow the required processing steps to be executed with the direct participant’s processing entity, before executing the steps for the indirect participant (where processing entity will need to be determined again by the client implementation flows using the identifier of the CdtrAgt).

When requesting processing entity determination by deriving direct participant, the requester should also know the csmAgent ids of the CSMs as registered on CSM Participant dynamic configuration.

Once the direct participant has been derived, the processing entity determination follows the "Standard Processing Entity determination" as explained above, but using the identifier of derived direct participant.

A payment message being processed by a flow or a CSM Service can have multiple parties and associated industry identifiers (e.g. InstdAgt, InstgAgt, DbtrAgt, CdtrAgt etc) . It is the responsibility of the flow(s) and the CSM Service to determine which of the available parties on the message is the processing entity at each stage of processing and pass on the associated industry identifier to the endpoint to determine the linked processing entity ID and enrich the payment.

Determining which party on the message is the processing entity is not in scope of the CSM Reachability service. The service scope is limited to determining the processing entity ID associated with an industry identifier selected by the requester.

/determine-processing-entity will have to be called multiple times to determine the processing entity where messages are being processed for two or more entities that are defined as processing entities. E.g. an inbound payment sent to an indirect participant or an intra-group transfer.

It is responsibility of the API consumer to provide valid inputs to the service on the request. Incorrect inputs may lead to a processing entity not being determined or an incorrect processing entity being determined. These include: