SEPA Direct Debit (Debtor flows)

Example Use Case

A bank client has opened an account with an online music streaming service based in a European country and signed up for a one-year subscription. They have provided their bank details and a signed sepa mandate and are expecting their subscription to start immediately, with the first payment being taken from their account over the next few days and, for the remainder of the contract, to be billed for the same amount on the 15th of every month.

Prerequisites

• Mambu Payment Gateway (MPG) feature must be enabled
• Account must be mapped to an iban using our accounts API
• Direct Debit SEPA messages must be sent to the same endpoint as for SEPA Credit Transfer.
• Bank account must be in Euro denomination

Steps

1. The online service's bank sends a pacs.003.001.02 Collection Instruction XML file to your bank, which is routed via the clearing system to Mambu's payments/incoming API

2. The payment is accepted and logged by the MPG and a transaction is scheduled for the settlement date indicated in the pac.003.001.02 message. At this point the transaction will be visible in the MPG in the € SEPA DD PENDING list of pending SEPA DD transactions (which is sorted by creation date), but not yet recorded as a transaction in the client’s account.
3. On the collection date Mambu creates a transaction from the payer's bank to the creditor bank using the IBAN given in the pacs.003 message. If the transaction fails but retries are configured, the payment status will remain in Pending Settlement and further retries will be executed according to the retry schedule. If the account has sufficient funds, the payment status will change to ‘SETTLED’ and the date recorded. The transaction will then be visible in the incoming SEPA DD page, where you can click for further information, including a full audit trail for the transaction. See the troubleshooting section below for information on what happens if the payment fails, for example, if there is not enough money in the account to cover the transaction.
4. On the 10th of the next month and for the following 10 months, the online service sends another pacs.003 message to the bank with the settlement date indicated as the 15th and steps 2 and 3 are repeated
5. With the final payment a Collection Instruction will be received with FNAL, this code indicates that we are dealing with the last transaction in the series. Given the mandate management is not yet supported by Mambu, please keep in mind that the recurrence code will not be validated on our side and the collections will be processed regardless of the value of the code.

Troubleshooting

The main places where you can troubleshoot any issue with the transaction are the following:

Mambu Payment Gateway UI

1. You can check the information and status of a specific collection directly from the web app.
   

2. Instructions API: this API can be used to retrieve the pacs.003.001.02 information in json format, as well as other metadata like the Collection ID.

3. Collection Details API: based on the generated Collection ID, you can view the details of a collection transaction as well as its status.

4. Collection Order Activity Event Streaming: subscribing to this topic will allow you to be notified on each status change during collection processing.