Skip to main content

Blocking SEPA Direct Debits

Deprecation notice

This feature is scheduled for deprecation. We recommend contacting Mambu Support to discuss alternative options.

Example Use Case

A client discovers a charge on their account that they do not recognise, the payment is identified as a recurring SEPA Direct Debit and the client wants to ensure that they will not be charged again while they contact the creditor to investigate further.

Prerequisites

  • The specific deposit account must exist in the system.

Steps

  1. Identify the Creditor Mandate ID from a previous direct debit payment initiated by this creditor. This can either be by using our API or the Mambu Payment Gateway (MPG) UI.
  2. Use our API to create a blocking rule for the client's account blocking any further SEPA Direct Debit collection requests using the identified Mandate ID.

POST /api/v1/accounts/{account_id}/blocking-rules

{
"creditorMandate": {
"creditorSchemeIdentification": {
"identification": {
"iban": "DE13439339003030393",
}
},
"mandateRelatedInformation": {
"mandateIdentification": "ABC123"
}
},
"product": "SEPA_DIRECT_DEBIT"
}
  1. If another PACS.003 collection request is received for this account for the blocked Mandate, the MPG will immediately generate a PACS.002 MS02 response message indicating that the debtor has prohibited transactions initiated by this creditor. Payments for other SEPA DD Mandates, which can also include other payments for the same merchant, will not be affected.

SEPA Direct Debit Rejection Flow

note

It is also possible to block all SEPA Direct Debit mandates for a client by sending a request to the Blocking Rules API without providing a specific Creditor Mandate (see example below), in this case, all payment collection requests for this client’s account will be rejected.

POST /api/v1/accounts/{account_id}/blocking-rules

{
"product": "SEPA_DIRECT_DEBIT"
}