You are here: Resources > SEPA Error Codes

SEPA Error Codes

Direct Debit transactions can be unsuccessful for various reasons and when a payment fails, the original transaction's status is updated. The new status will generally be set to REJECTED, REFUSED, RETURNED or REFUNDED (Collectively these statuses are ofter referred to as R-transactions). To help you to identify why the payment failed, error codes are provided by your payer's bank.

In this section we outline the various failed payments (R-transactions) and error codes that are possible, what they mean and what corrective action you should take based on the code.

The following guidance is based on the EPC recommendations (see the EPC Web site for more details).
NOTE: Certain error codes may be received both pre- and post-settlement.

Some banks may determine before the settlement date that your payer will have insufficient funds to make a payment; in this case you will receive a pre-settlement AM04 REJECT; other banks may wait until the actual settlement date to debit funds. If the funds are not available on the settlement date this would again result in an AM04 but in this scenario the R-transaction would be a post-settlement AM04 RETURN.

In the table below the R-Transaction Type column indicates when the error code may be treated as a REJECT, RETURN or a REFUND.

 

The following is a summary of all possible SEPA R-transaction codes:

Error Code Description R-Transaction Type Suggested Actions
AC01 Format of the account number specified is not correct

REJECT

RETURN

  • Contact the Debtor in order to confirm the correctness of the Debtor’s IBAN
  • In case of mandate amendment: check the data provided by the Debtor
  • Verify the database used for the BBAN conversion into IBAN
AC04 Account number specified has been closed This code cannot be used in certain SEPA countries for reasons of data protection. MS03 could be used as an alternative.

REJECT

RETURN

  • Contact the Debtor for the new account

AC06 Account specified is blocked, prohibiting posting of transactions against it

REJECT

RETURN

  • Contact the Debtor for alternative account/ solution to pay
AC13 Invalid debtor account typeA collection has been made against a scheme that is not supported by the payer's account. This can happen if you have attempted to make a Business-to-Business (B2B) collection against a non-business account.

REJECT

RETURN

  • Contact the Debtor for clarification and to agree on another means of payment
  • Conclude SDD Core mandate with Debtor
AG01 Transaction forbidden on this type of account (formerly No Agreement)

REJECT

RETURN

  • Contact the Debtor in order to get information about the payment account to be used
AG02 Bank Operation code1. An incorrect code/value on the PAIN.008 file submitted for processing 2. An incorrect sequence type submitted specified in the message is not valid for receiver

REJECT

RETURN

  • Contact your merchant bank to confirm what has caused this issue
  • Correct the wrong information
AM04 Amount of funds available to cover specified message amount is insufficient

REJECT

RETURN

  • Contact the Debtor to ensure that there are funds on his account
  • (Optionally) Re-present the payment
AM05 Duplication

REJECT

RETURN

  • Check if the collection is really duplicated
BE05 Party who initiated the message is not recognised by the end customer

REJECT

RETURN

  • Creditor to contact the Creditor Bank
CNOR Creditor Bank is not registered under this BIC in the CSM REJECT
  • Creditor to contact the Creditor Bank
CUST Cancellation of Credit Transfer payment, requested by the originator CANCEL

 

CUTA Cancellation requested because an investigation request has been received and no remediation is possible. CANCEL  
DNOR Debtor Bank is not registeredThe payer's bank (identified by its BIC code) is not a registered bank under SEPA (its BIC is unreachable) under this BIC in the CSM REJECT
  • Ask the Creditor Bank to check the reachability of the Debtor Bank
  • Contact Debtor to agree on another means of payment
DUPL Payment is a duplicate of another payment. CANCEL  
FF01 File formatThe payments XML file contained a syntax error. Contact Nuapay support if you receive this error code incomplete or invalid REJECT
  • Contact Nuapay support
MD01 No mandateYour payer's bank may have cancelled the mandate (upon instruction from the payer) In the case of an UNATHORISED REFUND, the payer is disputing that a mandate exists

REJECT

RETURN

REFUND

  • Analyse the characteristics of the SEPA Direct Debit transaction
  • Contact the Debtor in the case of a refund
MD02 Mandate related information data required by the scheme is missing- Mandate data in the mandate related information is not identical to those in the mandate (amendments had not been communicated) - Mandate data not consistent with version already received for the UMR - In case of mandate amendment: the original IBAN and the IBAN in the collection are the same REJECT
  • Contact Nuapay Support
MD06 Return of fundsDisputed authorized transaction received no later than 8 weeks after the collection must be refunded unconditionally. This could be related to a discrepancy between the amount pre-notified to the customer and the amount of the collection requested by end customer REFUND
  • Contact the debtor
MD07 End customer is deceasedThis code cannot be used in certain SEPA countries for reasons of data protection; AC06 or MS03 may be used instead

REJECT

RETURN

MS02 Reason has not been specified by end customer

REJECT

RETURN

  • Contact the debtor
MS03 Reason has not been specified by agentUsed by the payers' banks in the cases where national legislation (e.g., data protection laws) does not allow the use of AC04, AM04, MD07, RR01, RR02, RR03 and RR04

REJECT

RETURN

  • Contact the debtor
RC01 Bank Identifier code specified in the message has an incorrect format

REJECT

RETURN

  • Contact Nuapay Support
RR01 Specification of the debtor's account or unique identification needed for reasons of regulatory requirements is insufficient or missing

REJECT

RETURN

  • Contact your bank
RR02 Specification of the Debtor’s nameThe payer's name is mandatory and/or address needed for regulatory requirements is insufficient or missing

REJECT

RETURN

  • Contact Nuapay Support
RR03 Specification of the creditor’s nameThe merchant name is mandatory and/or address needed for regulatory requirements is insufficient or missing

REJECT

RETURN

  • Contact Nuapay Support
RR04 Regulatory Reason

REJECT

RETURN

  • Contact your bank
SL01 Due to specific service offered by the Debtor AgentYour payer has invoked a block against your business; has imposed a limit on the value of collections (and your Direct Debit exceeded this limit); or may have applied a limit to the frequency of collections.

REJECT

RETURN

  • Contact your payer
UPAY Payment is not justified. CANCEL