A payment can fail for many reasons. These reasons depend on the information system in charge of clearing these payments.
If we simplify it, when working with SlimPay, a single payment can pass through up to two information systems:
- The clearing house or network
SlimPay Error Codes
A payment is not processed (NOP) when it is never sent to the clearing house by SlimPay.
|AC01||Subscriber reference incorrect|
|AM04||Credit Transfer amount is greater than the available funds|
|AM05||Multiple "FIRST" payments|
|BE05||Creditor reference incorrect|
|CA01||No card alias found for the provided subscriber reference|
|CA02||Card alias provided isn't attached to any subscriber|
|CA03||Card alias expired|
|CA04||Card alias not found|
|MD01||Mandate reference incorrect|
Mandate not active
|NOP-FOCR||Following a cancellation request|
SEPA Error Codes
A payment can be:
- rejected (i.e. it won't be settled by the clearing house) before the execution date.
- returned (i.e. it was executed and then credited back to the debtor on the debtor's bank request) after the execution date within 5 IBBD for SEPA CORE and 2 IBBD for SEPA B2B.
- refunded on the debtor's request up to 13 months after the execution date (for SDD CORE only).
The following reasons are extracted from the EPC guide on R-transactions which should always be your number one reference for SEPA rules (SlimPay being your number two reference of course).
|Code||Reject||Return||Refund||Reason specified in the Rulebook||Suggested Creditor action|
|AC01||Account Identifier incorrect (i.e. invalid IBAN of the Debtor)||
|AC04||Account closed||Contact the Debtor for the new account|
|AC06||Account blocked||Contact the Debtor for alternative account/solution to pay|
|AC13||Debtor account is a consumer account (For SDD B2B collections only)||
|AG01||Direct Debit forbidden on this account for regulatory reasons||Contact the Debtor in order to get information about the payment account to be used|
|AG02||Operation code/transaction code/sequence type incorrect, invalid file format||Correct the wrong information|
|AM04||Insufficient funds||Contact the Debtor to ensure that the Debtor provides funds on his account|
|AM05||Duplicate collection||Check if the collection is really duplicated|
|BE05||Identifier of the Creditor Incorrect||Correct the CI|
|CNOR||Creditor Bank is not registered under this BIC in the CSM||Creditor to contact the Creditor Bank|
|DNOR||Debtor Bank is not registered under this BIC in the CSM||
|FF01||File format incomplete or invalid||Repair the XML file|
|MD02||Mandate data missing or incorrect||To repair the way to amend the mandate information or the amended information|
|MD06||Disputed authorized transaction
(For SDD Core collections only)
|To contact the Debtor|
(Only for SDD Core collections)
|To close the agreement with deceased Debtor|
|MS02||Refusal by the Debtor||To contact the Debtor|
|MS03||Reason not specified||To contact the Debtor|
|RC01||Bank Identifier (BIC) Incorrect||To contact the Debtor for the correct BIC|
|RR04||Regulatory Reason||To contact the Creditor Bank|
|SL01||Specific Service offered by the Debtor Bank||To contact the Debtor|
BACS Error Codes
The reasons for an unpaid direct debit are provided in the ARUDD report.
|0||Refer to Payer|
|4||Advanced Notice disputed|
|5||No account (or wrong account type)|
|8||Amount not yet due|
Card Error Codes
A card payment can be rejected before the money is debited or refunded (chargeback). Here are the possible reasons for a reject:
|IED||Invalid expiration date|
|ITR||Invalid transaction reference|
|OIE||Operator internal error|