SEPA Credit Transfer Inquiries
  • 01 Dec 2022
  • 5 Minutes To Read
  • Dark
    Light
  • PDF

SEPA Credit Transfer Inquiries

  • Dark
    Light
  • PDF

Article summary

SEPA Credit Transfer Inquiries allow SEPA participants to request extra information or clarifications regarding the status of a SEPA Credit Transfer.

There are several possible inquiry types supported by the SEPA scheme, including:

  • Claim of Non-Receipt (camt.027.001.06) → the Beneficiary has claimed they did not receive the original Credit Transfer. In this case, the Originator Bank is asked by the Originator to investigate whether the Credit Transfer has been executed. The SEPA scheme assumes that the Beneficiary contacts the Originator outside the scheme, and the Originator, in turn, requests the start of the inquiry process with their Bank.
  • Claim for Value Date Correction (camt.087.001.05) → the Beneficiary has claimed that the initial SEPA Credit Transfer has been credited with a value date later than the expected value date. In a similar manner, the SEPA scheme assumes that the Beneficiary contacts the Originator outside the scheme, and the Originator will request the start of the inquiry process with the Originator Bank.
  • Request for Status Update (pacs.028.001.01) → the Originator Bank can request a response for a previously sent Inquiry, to which the Beneficiary Bank has not yet responded. Requests for status updates should be sent if an answer has not been received within 10 banking days of the original inquiry. You can send as many status update requests as you want, although we recommend not sending too many, so as to give the receiving back time to respond.

Generally, there are two ways to initiate an inquiry: using our API, or using the Mambu Payment Gateway (MPG) UI. This page will tell you how to do both.

For any inquiry, the SEPA scheme gives the receiving party a maximum of 10 banking days to respond. The response must be in the form of a camt.029 message, which you will be able to view from the list of incoming SEPA CT messages in the MPG UI.

Once an inquiry has been answered, there may be compensation due, such as an interest payment refund or other fees that were incurred because of an incorrect value date or non-receipt of payment. The amount of compensation due may be included in the camt.029 message

Initiating a Claim of Non-Receipt (camt.027.001.06)

Initiate via the API

To initiate a Claim of Non-Receipt (camt.027.001.06) inquiry for an existing SEPA Credit Transfer (pacs.008.001.02), a Payments user must execute the following API call:

POST /api/v1/payments/inquiries:claimNonReceipt

{
   "groupHeader": {
       "messageIdentification": "<pacs008.GrpHdr.MsgId>",
       "settlementDate": "<pacs008.GrpHdr.IntrBkSttlmDt>"
   },
   "paymentIdentification": {
       "transactionIdentification": "<pacs008.CdtTrfTxInf.PmtId.TxId>"
   },
}

The information highlighted in green must contain the reference for the original Credit Transfer: message identification, settlement date, and transaction identification.

Executing the API call will trigger the creation of a Claim of Non-Receipt instruction with the status To Be Sent. It will be picked up with the next Outgoing SEPA Scheduler execution.

You can find more information on the claim of non-receipt API call in our Payments API Reference.

Initiate via Mambu Payment Gateway UI

To initiate a Claim of Non-Receipt inquiry for an existing Credit Transfer through the MPG UI, navigate to the transaction details page and click Initiate Claim in the SEPA Inquiries section

sct-initiate-claim

In the confirmation dialog, select the Claim of Non-Receipt inquiry type and confirm by pressing the Initiate button. This action will will trigger the creation of a Claim of Non-Receipt instruction with status To Be Sent, which will be picked up with the next Outgoing SEPA Scheduler execution.

sct-initiate-claim-non-receipt

Initiating a Claim for Value Date Correction (camt.087.001.05)

Initiate via API

To initiate a Claim for Value Date Correction (camt.087.001.05) inquiry for an existing SEPA Credit Transfer (pacs.008.001.02), a Payments user must execute the following API call:

POST /api/v1/payments/inquiries:claimValueDateCorrection

{
   "groupHeader": {
       "messageIdentification": "<pacs008.GrpHdr.MsgId>",
       "settlementDate": "<pacs008.GrpHdr.IntrBkSttlmDt>"
   },
   "paymentIdentification": {
       "transactionIdentification": "<pacs008.CdtTrfTxInf.PmtId.TxId>"
   },
   "claimedValueDate": "yyyy-MM-dd"
}

The information highlighted in green must contain the reference for the original Credit Transfer: message identification, settlement date, and transaction identification. The claimedValueDate field must contain the value date which the Beneficiary states is the expected value date. You can find this information by calling the payment details endpoint with the ID of the original payment.

Executing this API call will trigger the creation of a Claim for Value Date Correction instruction with status To Be Sent, which will be picked up with the next Outgoing SEPA Scheduler execution.

You can find more information on the value date correction SPI call in our API Reference.

Initiate via Mambu Payment Gateway

To initiate a Claim for Value Date Correction inquiry for an existing Credit Transfer through the MPG, navigate to the transaction details page and click Initiate Claim in the SEPA Inquiries section

sct-initiate-claim

In the confirmation dialog, select the Claim for Value Date Correction inquiry type, introduce the expected value date and confirm by pressing the Initiate button. This will trigger the creation of a Claim for Value Date Correction instruction with status To Be Sent, which will be picked up with the next Outgoing SEPA Scheduler execution.

sct-initiate-value-date-correction

Initiating a Request for Status Update (pacs.028.001.01)

To initiate a Request for Status Update (pacs.028.001.01) for an already submitted inquiry, a Payments user must execute the following API call:

Initiate via API

POST /api/v1/payments/inquiries:requestStatusUpdateOnInquiry

{
   "messageTypeName": "CAMT_087_001_05 or CAMT_027_001_06",
   "assignment": {
       "identification": "<camt.027/camt.087.Assgnmt.Id>",
       "creationDateTime": "<camt.027/camt.087.Assgnmt.CreDtTm>"
   },
   "caseIdentification": "<camt.027/camt.087.Case.Id>"
}

The information highlighted in green must contain the reference for the original Inquiry instruction: message type, assignment identification, assignment creation date and case identification. You can find this information by calling the payment details endpoint with the ID of the original payment.

Executing this API call will trigger the creation of a Request for Status Update instruction with status To Be Sent, which will be picked up with the next Outgoing SEPA Scheduler execution.

You can find more information on the inquiry status update API call in our API reference.

Initiate via Mambu Payment Gateway

To initiate a Request for Status Update for an existing Inquiry through the MPG, navigate to the Inquiry details page and click Request Status Update in the SEPA Inquiries section

sct-initiate-status-update

In the confirmation dialog, confirm by pressing the OK button. This action will will trigger the creation of a Request for Status Update instruction with status To Be Sent, which will be picked up with the next Outgoing SEPA Scheduler execution.

sct-confirm-status-update


Was this article helpful?

ESC

Eddy, a generative AI, facilitating knowledge discovery through conversational intelligence