Skip to content

SEPA Direct Debit

Olivia Felsberger edited this page Jan 22, 2020 · 7 revisions

With SEPA Direct Debit Core, creditors may collect payments in EUR both domestically and in other SEPA member countries.

On this page SEPA Direct Debit always refers to SEPA Direct Debit Core.

SEPA Direct Debit Configuration

  1. Navigate to Merchant Tools / Site Preferences / Custom Preferences.

  2. Select Wirecard Payment Gateway settings for SEPA Direct Debit: SEPA Direct Debit Site preferences

Payment Action

SEPA Direct Debit payment can be performed with two different payment actions:

1. Authorization: Payments for orders are not captured/invoiced but only authorized by the consumer and thus only reserved. For debit, you have to confirm/capture the amount manually.

  • This payment action triggers the transaction type authorization for payment method SEPA Direct Debit.
  • Authorization is possible through the payment provider services of either Wirecard Bank or Hobex (for Austrian, German and Dutch merchants).

2. Purchase: Payments for orders are captured/invoiced automatically.

  • This payment action triggers the transaction type debit for payment method SEPA Direct Debit.

SEPA Direct Debit payments require a notification from SEPA to be completed. Therefore, SEPA Direct Debit payments are marked as Pending for up to two days.

Descriptor

The descriptor is the text representing an order on the consumer's bank statement issued by their bank. It provides information for the consumer, as it associates a specific debit on the consumer's account with the respective purchase in your shop.

  • If the descriptor is set to No, the Provider Transaction Reference ID is provided for the bank statement.

  • If the descriptor is set to Yes, the default descriptor text consists of the first 9 characters of the shop name and the order number.

    • To modify the descriptor, check the script int_wirecard_core/cartridge/scripts/paymentgateway/transaction/entity/Descriptor.js.
    • Max. total descriptor length: 100 characters.

Set this feature to Yes to send the descriptor with each request/response.

BIC Enabled

Set this feature to Yes to display an input field for the consumer's BIC during the checkout process. In this case, this is a mandatory input field for your consumer.

Creditor ID

SEPA Direct Debit requires a Creditor ID to create a SEPA Direct Debit Mandate and supports configuration fields for creditor name and creditor city to be displayed in the mandate.

In order to be able to offer SEPA Direct Debit as a payment method, you have to apply for a Creditor Identifier. The Creditor ID is a mandatory identifier for anyone who wants to offer SEPA Direct Debit. It allows consumers to be able to manage their mandates with merchants more easily. SEPA Direct Debit supports configuration for the creditor name and the creditor city to be displayed in the mandate.

This strongly depends on the local rules and regulations. Depending on the country of origin, the merchant may need to apply for the Creditor ID at a tax office, local authority, or another organization.

A German merchant needs to apply for a Creditor ID at the Bundesbank Deutschland. To learn more about how to apply for a Creditor ID, please refer to http://www.bundesbank.de.

An Austrian merchant needs to apply for a Creditor ID at the Österreichische Nationalbank. To learn more about how to apply for a Creditor ID in Austria, refer to www.oenb.at.

SEPA Creditor

Supported Post-Processing Operations

To access post-processing operations, go to Merchant Tools / Wirecard Payment Gateway / Transaction Table to open the transaction table, which lists all successful transactions: Wirecard Transaction Table

Click a Transaction ID to open the transaction detail view. It shows all available post-processing operations, e.g.:

Wirecard Payment Gateway Transactiondetails

SEPA Direct Debit requires some time to confirm a transaction. Transactions are only visible in the transaction table if they have been confirmed as successful.

Please note that even when a transaction may have been successfully processed by the consumer's bank, the transaction might still be reversed due to, for example, insufficient funds on the consumer's bank account. Should this be the case, a new transaction using the transaction type debit-return will be created. This transaction will contain a detailed description of what happened.

It should further be noted that a consumer can object to any authorized debit without giving a reason for up to 8 weeks. In this case a transaction of type debit-return will be created.

Depending on your Payment Action settings, there are different options for SEPA Direct Debit post-processing operation workflow:

Payment Action Authorization

1. Capture: Triggers transaction type debit. The payment will be captured/invoiced, and the corresponding custom order attribute paymentGatewayOrderState will be updated to status Processing.

2. Refund: Triggers transaction type sepacredit. The payment/invoice will be refunded, and the corresponding custom order attribute paymentGatewayOrderState will be updated to status Refunded.

Payment Action Purchase

1. Refund: Triggers transaction type sepacredit. The payment/invoice will be refunded, and the corresponding custom order attribute paymentGatewayOrderState will be updated to status Refunded.

You also have the option of partial Refund/Capture. Partial Refund/Capture is possible until the payment has been refunded/captured in full.

SEPA Direct Debit supports the post-processing operation Refund via SEPA Credit Transfer. For more details on how to enable and configure refunds for SEPA Direct Debit, please see the SEPA Credit Transfer page.


Please be aware that stock management is not included in the post-processing operations triggered in the Wirecard cartridge but only in Salesforce order management.

You can’t perform that action at this time.