Everything you'd want to know before you install.
A detailed look at how SEPA Direct Debit with Online Mandates for PrestaShop 1.7.8, 8 & 9 works, why we built it the way we did, and the thinking behind the features above.
SEPA direct debit or a Stripe subscription
Payment providers offer SEPA direct debit, but every instalment is charged, funds pass through their account before reaching you and your mandates stay with them. With this module, the mandate is signed on your shop, the file leaves from your bank and the money lands in your account. You need a SEPA creditor identifier and a direct debit agreement, both provided by your bank. After that, the cost is limited to your bank's fees on each file.
B2B or Core mandate: what the module applies
The B2B scheme is for business customers: the debtor cannot request a refund after the debit and must register the mandate with their bank before the first collection. At signature, they confirm it with a box recorded in the evidence. The Core scheme suits any customer, with an 8-week refund right. The PDF carries the official mandate title, the type of payment, the place and date of signature, your name, address and creditor identifier.
From cart to bank statement
The customer orders and signs a mandate, or picks one already signed. The order moves to “SEPA direct debit scheduled” and a collection is created at the end of your pre-notification period, announced to the customer by email and on the invoice. You preview then generate the bank file, validated against the ISO 20022 schema, and upload it to your bank. After the period you set without reject, or when you import the camt.054, the order moves to payment accepted.
Signature evidence you can verify
The mandate signed online rests on a time-stamped snapshot, a sealed PDF whose SHA-256 is kept, and an audit trail where each event is chained to the previous one: creation, code sent or wrong, signature, downloads, IBAN displays, collections, rejects and revocation. The email code is an electronic signature within the meaning of the eIDAS Regulation; the module does not promise any particular legal value, which you assess with your bank and advisers.
Rejects, from reason code to retry
A reject arrives a few days after the due date, sometimes later for a refund under the Core scheme. When the return file is imported, the module finds the collection by its end-to-end reference, records the code and its label, moves the order to “SEPA direct debit rejected” and alerts you. Depending on the code, it schedules a pre-notified retry or revokes the mandate. Beyond the number of rejects you set, the payment method is no longer offered to the customer.
Bank data and GDPR
IBANs and bank files are encrypted, emails never contain the full version, and only employees with the edit permission can download a bank file or display an IBAN. On an erasure request, mandates still needed as evidence are kept for the period you set, at least 13 months under the EPC rulebooks; your national law may require more.
There are no reviews yet.