Article summary

        The Sepa Direct Debit transaction starts by sending the request for a direct debit to the BPE transaction gateway. The gateway processes the request and sends a response to the merchant. Additionally, a transaction push can be sent to the merchant as well (Both contain the current status of the transaction). The Payment Engine will then perform the direct debit on the account of the customer. This will take a few days and will either fail or succeed after which the status is again pushed to the merchant site. If it succeeds, it is still possible that at a later point a reversal occurs. This will create a new transaction with a credit amount, to deduct the previous amount from the merchant account. Again, this status is pushed to the merchant site.

        Mandates SEPA Direct debit requires a merchant to obtain a mandate from a customer to be allowed to perform a direct debit. A reference to this mandate and the signing date of the mandate is then used for all direct debits.

        Recurring SEPA direct debits It is possible to perform multiple direct debits, using the same mandate. Performing a recurring direct debit has several requirements:

        The mandate must mention that it is given for recurring direct debits. The first transaction needs to be performed separately and needs to have the flag “StartRecurrent” set to true. The follow-up recurring transactions need to reference this original transaction. The maximum period between 2 recurring transactions is 36 months. (After 36 months of not using a mandate, it expires).

        Notification of a direct debit To have the Payment Engine send a notification to the consumer, notifying the consumer of an impending direct debit, add the supplementary Notification service with the action ExtraInfo to the request. Also, use the notification type ‘PreNotification’. Reversals and Rejects

        It is possible that direct debit initially appear to succeed, but after a few days actually turn out to have failed. This can be due to insufficient funds on a bank account or because a consumer has blocked his account for direct debit. Additionally, a consumer can contact his bank and reverse a specific direct debit. In all of these cases a reversal transaction is then created, to correct the merchant balance on his Buckaroo account. It is also possible that direct debit initially appear to succeed, but after the success we receive a reject due to a wrong account number. In this case a reject transaction is then created, to correct the merchant balance on his Buckaroo account. Lastly, if a reversal takes place 56 days or more after the original transaction there are additional bank costs. In this case we create a reversal and also a MOI transaction. The transactiontype of the MOI transaction is an informational transaction. This informational transaction has no influence on the balance since this is only a registration for the additional bank costs. MOIs cannot happen if the direct debit transaction was created in combination with an e-mandate. This is only possible for SEPA Direct Debit if you are using the ExtraInfo action to also send the mandatereference. For information on e-mandates, see the e-mandate manual. If you wish to use the e-mandate service, contact Buckaroo’s sales department.

        Servicecodes and actions

        Use the service code sepadirectdebit (b2c) or sepadirectdebitb2b (b2b).

        The SEPA Direct Debit service supports the following actions: Pay, Refund, ExtraInfo, PayRecurrent, Authorize. For Refund and Authorize use channel 'Backoffice'. The rest uses channel 'Web' (default).

        Was this article helpful?

        What's Next