Request Processing

The SEPA DD STEP2 CSM Service exposes the Direct Debit API to support SEPA DD Request Processing. Requests made through these interfaces instruct the CSM Service to carry out required validations at both bulk and transaction level, map the messages to appropriate versions of ISO20022 messages, perform schema check and submit the individual transactions for bulking, so they can be added to the files to be sent to the scheme.

Creditor Direct Debit Collection/Creditor Payment Reversal Request (pacs.003 and pacs.007)

The following responses are provided:

A Technical acknowledgement of submission of bulk message from the client implementation flows
1. Successful Submission (Positive Ack)
2. Unsuccessful Submission e.g. message cannot be unmarshalled (Negative Ack)
IPF Validation Response (a pacs.002 response in IPF Canonical format).
1. Below values are used for bulk level validation (OrgnlGrpInfAndSts.GrpSts)
  1. ACTC - Entire bulk has passed IPF Validation
  2. RJCT - Entire bulk has failed IPF validation (Appropriate ISO/Proprietary code mapped within OrgnlGrpInfAndSts.StsRsnInf.Rsn). There will not be any further responses sent for this bulk
  3. PART - Some transactions within the bulk failed IPF Validation (Status of all transactions conveyed in the response)
2. Below values are used for Transaction level validation results (TxInfAndSts.TxSts)
  1. ACTC - Transaction passed IPF Validation
  2. RJCT - Transaction failed IPF Validation (Appropriate ISO/Proprietary Code within TxInfAndSts.StsRsnInf.Rsn)
Scheme Validation Response (a pacs.002 response in IPF Canonical format)
1. Scheme Validation results are generated on the back of STEP2 SDD CSM Service receiving the DVF file from the scheme. The CSM Service maps and generates pacs.002 responses in IPF Canonical format.
2. Any transactions that had failed IPF validations, will not be available on the scheme validation response
3. Below values are used for bulk level validation (OrgnlGrpInfAndSts.GrpSts)
  1. ACSP - Entire bulk has passed Scheme Validation and the settlement is in progress
  2. RJCT - Entire bulk has failed Scheme validation (Appropriate ISO/Proprietary code mapped within OrgnlGrpInfAndSts.StsRsnInf.Rsn). The transaction within the bulk will not be settled. There will not be any further responses sent for this bulk
  3. PART - Some transactions within the bulk failed Scheme Validation (Status of all transactions conveyed in the response)
4. Below values are used for Transaction level validation results (TxInfAndSts.TxSts)
  1. ACSP - Transaction passed Scheme Validation
  2. RJCT - Transaction failed Scheme Validation (Appropriate ISO/Proprietary Code within TxInfAndSts.StsRsnInf.Rsn). Transactions that failed scheme validations, will not be settled
Settlement Response (a pacs.002 response in IPF Canonical format)
1. Settlement Responses are provided on the Interbank Settlement Date quoted within the bulk submitted from client implementation flows (GrpHdr.IntrBkSttlmDt). The settlement responses will be generated after processing of the RSF files received from the scheme.
2. The transactions that had failed scheme validations, will not be included on the Settlement Response
3. Below values are used for bulk level validation (OrgnlGrpInfAndSts.GrpSts)
  1. ACSC - Entire bulk has been settled
  2. RJCT - Entire bulk has failed settlement. (Appropriate ISO/Proprietary code mapped within OrgnlGrpInfAndSts.StsRsnInf.Rsn).
  3. PART - Some transactions within the bulk failed settlement (Status of all transactions conveyed in the response)
4. Below values are used for Transaction level validation results (TxInfAndSts.TxSts)
  1. ACSC - Transaction settled
  2. RJCT - Transaction failed settlement (Appropriate ISO/Proprietary Code within TxInfAndSts.StsRsnInf.Rsn)

Creditor Payment Cancellation Request (camt.056)

This differs from a pacs.003/pacs.007 request because there is no actual settlement of camt.056

The following responses are provided:

A Technical acknowledgement of submission of bulk message from the client implementation flows
1. Successful Submission (Positive Ack)
2. Unsuccessful Submission e.g. message cannot be unmarshalled (Negative Ack)
IPF Validation Response (a pacs.002 response in IPF Canonical format).
1. Below values are used for bulk level validation (OrgnlGrpInfAndSts.GrpSts)
  1. ACTC - Entire bulk has passed IPF Validation
  2. RJCT - Entire bulk has failed IPF validation (Appropriate ISO/Proprietary code mapped within OrgnlGrpInfAndSts.StsRsnInf.Rsn). There will not be any further responses sent for this bulk
  3. PART - Some transactions within the bulk failed IPF Validation (Status of all transactions conveyed in the response)
2. Below values are used for Transaction level validation results (TxInfAndSts.TxSts)
  1. ACTC - Transaction passed IPF Validation
  2. RJCT - Transaction failed IPF Validation (Appropriate ISO/Proprietary Code within TxInfAndSts.StsRsnInf.Rsn)
Scheme Validation Response (a pacs.002 response in IPF Canonical format)
1. Scheme Validation results are generated on the back of STEP2 SDD CSM Service receiving the DVF file from the scheme. The CSM Service maps and generates pacs.002 responses in IPF Canonical format
2. Any transactions that had failed IPF validations, will not be available on the scheme validation response
3. Below values are used for bulk level validation (OrgnlGrpInfAndSts.GrpSts)
  1. ACCP - Entire bulk has passed Scheme Validation
  2. RJCT - Entire bulk has failed Scheme validation (Appropriate ISO/Proprietary code mapped within OrgnlGrpInfAndSts.StsRsnInf.Rsn)
  3. PART - Some transactions within the bulk failed Scheme Validation (Status of all transactions conveyed in the response)
4. Below values are used for Transaction level validation results (TxInfAndSts.TxSts)
  1. ACCP - Transaction passed Scheme Validation
  2. RJCT - Transaction failed Scheme Validation (Appropriate ISO/Proprietary Code within TxInfAndSts.StsRsnInf.Rsn)