When a transaction fails, the bank generates an error code, which is then displayed in the Twikey user interface. This error code provides valuable information regarding the reason for the unsuccessful transaction, helping you identify and address the issue effectively.
R codes are displayed in the transaction detail or on the customer detail in the 'transactions' tab.
An overview of all R codes can be is available at this link: https://www.twikey.com/product/r-codes/
NL: https://www.twikey.com/nl/product/r-codes/
Setting dunning steps allows you to automate your workflow
You can set specific actions (dunning steps) based on these error codes to facilitate smooth direct debit payments and prompt customers to finalize their transactions effortlessly. These dunning steps run automatically. An example is shown further in this article.
Usually this means that the customer can't pay (or not from that account).
| CODE | ERROR REASON |
| MS03 | Reason not specified. |
| AM04 | Insufficient funds |
This means that the customer explicitly didn't want to pay (but may want to opt for another mechanism)
| CODE | ERROR REASON |
| MD06 | Disputed authorized transaction. Debtor has requested a refund within the 8 weeks refund period. |
| MS02 | The debtor refuses this particular collection. This code may be received pre- or post-settlement, depending on how quickly the debtor bank responds to the refusal. |
| SL01 | Specific service offered by the Debtor Bank. The creditor has been blocked by the debtor (blacklisted) or the collection amount is too high. |
This is the anything else, could either be because there was a problem with the registration of the mandate at bank side or
any other technical problem.
| CODE | ERROR REASON |
| AC01 | IBAN or IBAN/BIC combination of debtor is incorrect. |
| AC04 | Debtor account closed. |
| AC06 | Account of the debtor blocked (eg. succession/bankruptcy) or blocked for Direct Debit transactions by the debtor. |
| AC13 | Account type not allowed for Direct Debits. |
| AG01 | Account not allowed for Direct Debits for regulatory reasons. |
| AG02 | Bank Operation code specified in the message is not valid for the bank. |
| AM05 | Duplicate collection. |
| BE05 | Incorrect Creditor Identifier code. |
| FF01 | File Format incomplete or invalid. |
| MD01 | No valid mandate (no longer valid, not correctly registered, invalid sequence type). |
| MD02 | Mandate data missing or incorrect. Two FIRST transactions were received for the same mandate. |
| MD07 | Debtor deceased. |
| PY01 | Not routable. This can occur when the debtor's bank does not handle SDD's. |
| RC01 | Bank Identifier (BIC) incorrect. |
| RR01 | Regulatory Reason. The debtor account number is missing. |
| RR02 | Regulatory Reason. The debtor name and/or address is missing. |
| RR03 | Regulatory Reason. The creditor name and/or address is missing. |
| RR04 | Regulatory Reason. This code cannot be used in certain SEPA countries for data protection reasons. MS03 can be used as an alternative. |
Failed payments
Action(s) when insufficient funds MS03, AM04
Action(s) when customer refuses MD06, MS02, SL01
Action(s) on failure at bank AC01, AC04, AC06, AC13, AG01, AG02, AM05, BE05, FF01, MD01, MD02, MD07, PY01, RC01, RR01, RR02, RR03
For more info on how to adapt your failed payments flow; see Dunning