PrestaShop Accounting & Invoicing

SEPA Direct Debit with Online Mandates for PrestaShop 1.7.8, 8 & 9

Customers sign their SEPA mandate at checkout, you collect into your own bank.

  • 30-day refund
  • 12 months updates
  • 24h support

Selling B2B with recurring payments always raises the same question: how do you debit a business customer without a payment provider that takes a fee on every instalment and holds your funds for days? SEPA direct debit is built for this, but it requires a signed mandate, a bank file in the right format, pre-notifications and reject tracking. This module handles all of it inside PrestaShop. Customers sign their mandate online during checkout, with a one-time code sent by email and time-stamped evidence. Every order and every subscription instalment becomes a pre-notified collection. You generate the pain.008 file in one click, upload it to your bank, and the pain.002 or camt.054 return files update payments and rejects.

At a glance
  • SEPA B2B or Core mandate, recurrent or one-off, signed online in the checkout with an email code
  • Sealed mandate PDF (SHA-256) and chained audit trail: any change is detected
  • pain.008.001.08 or .02 file validated against the official ISO 20022 schema, stored encrypted, never emailed
  • Schedules, FRST/RCUR/OOFF/FNAL sequences, rejects imported from pain.002, camt.054 or camt.053
  • PrestaShop 1.7.8, 8 and 9, no commission: funds go straight to your account
PrestaShop 1.7.8, 8 & 9 SEPA B2B and Core pain.008 validated ISO 20022 No commission
  • PrestaShop Certified Agency 2026
  • PrestaShop Expert Certification — Core Skills
  • PrestaShop Expert, level 3

Built by a PrestaShop Certified Agency

www.datafirefly.com/en/
SEPA direct debit for PrestaShop: mandate signed online, pain.008 bank file, schedule and dashboard
v2.0.0 · updated 2026-11-07
SEPA Direct Debit with Online Mandates for PrestaShop 1.7.8, 8 & 9 €149.00
What it does

The short version.

01

Mandate signed without leaving checkout

In the payment block, customers complete their details, prefilled from the invoice address, and type their IBAN, formatted and checked as they type. They read the mandate text, confirm in B2B that the account is a business account, then receive a 6-digit code by email. The mandate is signed as soon as the code is entered. On the next order, they simply pick their saved account.

02

Sealed, verifiable evidence

At signature, the module freezes a time-stamped snapshot: exact mandate text, scheme, type of payment, place, IP address, browser, method and masked IBAN. The mandate PDF is produced once, stored encrypted, and its SHA-256 is recorded. Every event of the mandate goes into a chained audit trail: a row changed in the database is reported.

03

A bank file checked before upload

Due collections are grouped by scheme, sequence and date. A preview shows each block before export. The pain.008 file is validated against the official ISO 20022 schema before it is saved, then stored encrypted. Dates follow the TARGET calendar and your bank's submission deadline. Nothing is exported twice, even with two simultaneous clicks.

04

Recurrent or one-off, your choice

A recurrent mandate serves the next orders and schedules: a fixed amount every week, month, quarter, half-year or year, or a reference order repeated at current prices. A one-off mandate (OOFF) is valid for one order only. Optionally, the last debit of a limited schedule is sent as FNAL and closes the mandate.

05

Rejects handled without spreadsheets

Import your bank's pain.002, camt.054 or camt.053: each rejected collection gets its reason code, the order changes status and you are alerted. Insufficient funds trigger a pre-notified retry, with a reject fee if your terms of sale provide for it. A closed account or a mandate unknown to the bank revokes the mandate.

06

Bank data protected

IBANs and bank files are encrypted with AES-256-GCM. Downloading a bank file or the full PDF, or displaying the IBAN, requires the edit permission, and each access is logged. Emails never contain a full IBAN or a bank file. In multistore, each employee only sees the shops in their context.

The long version

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.

§ 01

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.

§ 02

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.

§ 03

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.

§ 04

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.

§ 05

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.

§ 06

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.

€149.00
One-time · 12 months updates
Read the docs
  • Unlimited dev & staging installs
  • Source code included
  • 30-day refund
  • 24h support · EN / FR
5.0/5 21 reviews
All customer reviews