Overview

Banks provide feedback on SEPA Direct Debit (SDD) transactions in multiple stages. Early feedback is often provisional and may be corrected in the days that follow. Below is an overview of how this feedback typically evolves over time.

Feedback timeline

Day X - Initial feedback

• On Day X, the bank provides initial feedback indicating that all transactions were successful.
• This feedback may already include some intrabank corrections (e.g. Deutsche Bank → Deutsche Bank).
• At this stage, the actual settlement status is often not yet fully known. The bank therefore assumes success by default.

Day X+1 - First corrections

• On Day X+1, the bank may report failed transactions.
• This feedback corrects the initial Day X status.
• These corrections typically concern intrabank transactions or feedback from faster-processing banks.

Day X+2 to Day X+5 - Final corrections

• From Day X+2 onwards, additional failures may be reported, further correcting earlier feedback.
• This mainly concerns interbank (cross-bank) transactions, which typically require more processing time. In most cases, the transaction status is known with more than 99% certainty at this stage.

Final confirmation timeline

CORE Mandates

• Final confirmation can take up to 8 weeks
• In fraud-related cases, this can extend to 13 months

B2B Mandates

• Final confirmation is typically received within 2–3 business days

Using bank feedback delay

Banks can correct transaction feedback in the days following the initial settlement.Without a delay, these corrections are immediately reflected in the API, which can cause transaction statuses to change multiple times (for example from paid to unpaid). Introducing a delay in the API transaction feed helps you manage this uncertainty in a controlled way. The delay can be set in the settings of your profile via the submenu payments.

This mechanism applies only to the API transaction feed. The user interface (UI) always displays the latest transaction status as received from the bank and is not affected by the configured delay.

Transactions are accumulated in a pending buffer and exposed in the API transaction feed after the configured delay (in bank working days).The delay starts from the moment we receive feedback about the batch from the bank.

Key benefits

• More stable downstream processing
• Fewer reversals and corrections to make
• Improved financial accuracy in your systems

You can choose how bank feedback is exposed to your systems f.ex. :

Without a delay

• Feedback is passed through immediately to the API, exactly as received from the bank.
• This ensures maximum transparency and timeliness.
• Your system must be able to handle status transitions (e.g. from paid to unpaid).

With a 2-day delay

• Transactions are temporarily withheld from the API transaction feed until Day X+2.
• This prevents interim status changes while the final outcome is still uncertain.