Direct debit
Direct debits are a European banking method where customers authorize automatic one-off or recurring debits directly from their bank account. It is available in 36 countries and supports Sofort and iDEAL.
Read how direct debits can benefit your business on multisafepay.com
Supports | Details |
---|---|
Countries | SEPA region ⚠️ Note: To avoid declined transactions, non-EEA countries must include name and address in the customer_object . |
Currencies | EUR |
Chargebacks | Yes (see below) |
Payment components | Yes |
Payment pages | Yes (current and deprecated versions) |
Recurring payments | Yes |
Refunds | Yes: Full and partial |
Second Chance | Yes |
Virtual IBANs | Yes, to better manage direct debits |
Payment flow
This diagram shows the flow for a successful transaction. Click to magnify.
Payment statuses
The table below sets out the order status and transaction status for payments and refunds.
Description | Order status | Transaction status |
---|---|---|
MultiSafepay's customer background check was successful and we've generated an e-mandate. | Uncleared | Initialized |
We've sent the e-mandate to the customer's bank. You can no longer cancel. | Uncleared | Uncleared |
MultiSafepay has collected payment. | Completed | Completed |
The customer cancelled the transaction or requested a chargeback, or their bank declined the transaction. | Void | Void |
The customer's bank declined the transaction. See the reason codes below. | Declined | Declined |
Refunds: Refund initiated. | Reserved | Reserved |
Refunds: Refund complete. | Completed | Completed |
Activation
-
Email a request to [email protected]
Include in the request the following information:
- Monthly and annual direct debit volume
- Minimum and maximum transaction amount
- Type of products sold using this payment method
- Whether you want to accept recurring payments
- Whether any subscriptions are monthly, quarterly, or annual
- Any additional information we request
We send you an agreement to sign and email back to us.
We check your eligibility and if approved, activate the payment method for your account.
-
Once approved, sign in to your MultiSafepay dashboard .
-
To activate the payment method for:
- All sites, go to Settings > Payment methods.
- A specific site, go to Sites, and then click the relevant site.
- Select the checkbox for the payment method, and then click Save changes.
💬 Support: If the payment method isn't visible in your dashboard, email [email protected]
Integration
API
-
See API reference – Create order > Banking order.
Example requests
For example requests, on the Create order page, in the black sandbox, see Examples > Direct debit direct/redirect.
Ready-made integrations
Supported in all ready-made integrations (direct).
Testing
To test direct debits, see Testing payment methods - Banking methods.
User guide
Chargebacks
Customers can request a chargeback within 56 days, or for unauthorized transactions (i.e. without verifiable consent from the customer) within 13 months. This makes direct debits unsuitable for most retail businesses, e.g. clothing.
You cannot dispute chargebacks and there is no facilitated process like there is for credit or debit card chargebacks. Chargebacks can cost up to 65 EUR in bank fees.
Declined transactions
If a direct debit is declined, a reason code is provided.
If the IBAN or BIC is incorrect, our bank informs us the next business day.
Reason codes and recommended responses
Code | Reason | Recommended response |
---|---|---|
AC01 | Incorrect account number | Contact the debtor to confirm the IBAN. If there is a mandate amendment, check the data provided by the debtor. |
AC04 | Closed account number | Contact the debtor to confirm the new IBAN. |
AC06 | Blocked account | Contact the debtor for another account or means of payment. |
AC13 | Debtor account type is missing or invalid | Contact the debtor for clarification and to agree another means of payment. |
AG01 | Transaction forbidden | Contact the debtor for another account or means of payment. |
AG02 | Invalid bank operation code | Resubmit the transaction with the correct authorization reference and transaction type: OOFF or RCUR . |
AM04 | Insufficient funds | Contact the debtor to add funds to their account. |
AM05 | Duplication | Contact your bank to confirm whether collection was duplicated. |
BE04 | Creditor address missing or incorrect | |
BE05 | Unrecognised initiating party | The creditor ID was incorrect or was changed without an amendment indicator. Check your contract for the correct creditor ID. If in doubt, contact your bank first. |
CNOR | Creditor bank is not registered | Contact your bank. |
DNOR | Debtor bank is not registered | Contact your bank. Contact the debtor for another means of payment. |
ED05 | Settlement failed | Depends on the SLA between the debtor's bank and the Clearing and Settlement Mechanism (CSM). |
FF01 | Invalid file format | Repair the XML file. |
FF05 | Direct debit type incorrect | |
FOCR | Return following a cancellation request | |
MD01 | No mandate | Analyse the characteristics of the SDD collection. Contact the debtor if they request a refund. |
MD02 | Required infomation missing from mandate | Amend the mandate. |
MD06 | Customer requested chargeback | Contact the debtor. |
MD07 | Customer deceased | Close the agreement with the deceased debtor. |
MS02 | Unspecified reason generated by customer | Contact the debtor. |
MS03 | Unspecified reason generated by agent | Contact the debtor. |
RC01 | Incorrect bank identifier | Contact the debtor for the correct BIC for a non-EEA collection. Ask your bank to allocate the debtor's bank's correct BIC in the interbank message. |
RR01 | Missing debtor account or identification | Repair the collection to complete the debtor's account information. Contact your bank. |
RR02 | Missing debtor name or address | Repair the collection to complete the debtor's name and/or address. Contact your bank. ⚠️ Note: To avoid declined transactions, non-EEA countries must include name and address in the customer_object . |
RR03 | Missing creditor name or address | Repair the collection to complete your name. Contact your bank. |
RR04 | Regulatory reason | Contact your bank. |
SL01 | Specific service offered by debtor agent | Contact the debtor. |
TM01 | File received after cut-off time |
For more information in:
- English, see European Payments Council – Guidance on reason codes .
- Dutch, see Betaal Vereniging – Reasoncodes en vervolgacties .
E-mandates
An e-mandate represents an agreement between you and the customer and is required for every direct debit. We create them automatically based on the customer's IBAN and the site_id
, and specify if it is a one-time, initial, or recurring debit (see Recurring payments).
E-mandates are needed when resolving customer disputes and chargebacks.
We send all e-mandates to our bank at the end of every business day.
Processing times
Transactions are processed within:
- Amounts less than 500 EUR: 9 days
- Amounts over 500 EUR: 22 days
Processing times can be reduced on request. Email [email protected]
Refund risk
There is a risk that if you refund a customer and they also request a chargeback, you pay their money back twice. Customers can even request a chargeback after successfully receiving a refund.
How to reduce refund risks
To reduce the chances of this happening, we strongly recomend:
- Only processing refunds for trusted, verified customers.
- Avoiding refunding a customer if you have any ongoing dispute with them.
- If refunding:
- First check if the customer has already requested a chargeback.
- Wait until 7 working days after payment was initiated to be sure payment is now complete.
- Communicate clearly to the customer that you are sending a refund and that the funds will take a few days to arrive in their account.
Support
Email [email protected]
Updated 3 months ago