SEPA DIRECT DEBIT chargebacks
| ISO code | Reason - Description |
|---|---|
| AC01 | Incorrect Account Number
|
| AC03 | Wrong IBAN |
| AC04 | Closed Account Number The account has been closed. The buyer may have used an old account number or closed the account since the mandate was implemented. |
| AC06 | Blocked account The account has been blocked for direct debits:
|
| ACNR | Acceptance of claim of non-receipt |
| ACVA | Acceptance of value date change |
| AG01 | Transaction forbidden on this type of account The SEPA direct debit cannot be implemented for this type of account. E.g.: savings account. |
| AG02 | Invalid Bank Operation Code Technical error |
| AM04 | Insufficient funds The debtor’s bank could not cover the direct debit due to insufficient funds. |
| AM05 | Duplication Collection has already been made. This could either be due to an incorrect transaction ID, or if two transactions have been submitted. |
| AM09 | Wrong amount |
| ARDT | Original operation already returned |
| ARJT | Operation already rejected |
| BE04 | Missing Creditor Address |
| BE05 | Unrecognised Initiating Party The provided Creditor ID is incorrect or invalid. |
| CERI | ERI check |
| CNOR | Non-trading bank |
| CUST | By customer’s order |
| CVAA | Correct value date already applied |
| DNOR | BIC code of the debtor’s bank unknown or does not match the IBAN. This may occur if the IBAN corresponds to an account in Switzerland but the debtor’s address has not been transmitted. |
| DUPL | Duplicate |
| ED05 | Settlement Failed |
| ERIN | ERI option not supported |
| FF01 (Previously MD03) | Invalid File Format Technical error |
| FF05 | Direct debit type incorrect Technical error |
| FOCR | Positive response to a recall |
| FRAD | Transfer of fraudulent origin |
| LEGL | Regulatory reason |
| MD01 | No valid mandate The mandate for the buyer’s account is no longer valid. The mandate may have been canceled by the buyer. It is also used when a customer requests a refund, stating that the transaction was not authorized. This can occur up to 13 months after the settlement. |
| MD02 | Mandate data missing or incorrect Technical error. |
| MD03 | Invalid File Format Technical error. |
| MD06 | Disputed authorized transaction The buyer has requested a refund of an authorized transaction. May be received up to 8 weeks after the settlement. |
| MD07 | Debtor deceased You have attempted to set up a mandate for the account of a deceased individual. Extremely rare. |
| MODI | Modified upon request |
| MS02 | Refusal by the debtor - Not Specified Reason The buyer rejects the direct debit. This code may be received pre- or post-settlement, depending on how quickly the buyer's bank responds to the rejection. |
| MS03 | Reason not specified One of the most common error codes. Often used when banks choose to not provide more specific explanatory codes, such as MD07 and AM04, due to data protection reasons. |
| NERI | ERI absent |
| NOAS | No authorization |
| NOOR | Payment not processed |
| RC01 | Bank Identifier Incorrect Bank identifier incorrect (i.e. invalid BIC). |
| RJNR | Rejection of claim of non-receipt |
| RJVA | Rejection of value date change |
| RNPR | Original transaction received but not usable |
| RR01 | Regulatory reason - Missing Debtor Account Or Identification Technical error. |
| RR02 | Regulatory reason - Missing Debtor Name Or Address Technical error. |
| RR03 | Regulatory reason - Missing Creditor Name Or Address Technical error. |
| RR04 | Regulatory reason R04 can be used for a regulatory reason different from RR01, RR02 or RR03. |
| SL01 | Specific Service Offered By Debtor Agent The request clashes with specific instructions that the buyer has configured for his or her account. E.g.: the creditor is blacklisted. |
| TECH | Technical problem |
| TM01 | File received after Cut Off Time The time limit has passed. |