Payment Issues
Every payment has a transaction timeline, and payment failures can occur at various stages of the process.
A payment can be:
- rejected before the execution date (i.e. the payment won't be settled by the clearing house)
- returned after the execution date within five IBBD for SEPA CORE and two IBBD for SEPA B2B (i.e. the payment was executed, then credited back to the debtor on the debtor bank’s request)
- refunded on the debtor's request up to 13 months after the execution date (for SEPA CORE only)
These R-Transactions can occur for many reasons, depending on the information system in charge of clearing the payment. When working with SlimPay, a single payment can pass through up to two information systems:
- SlimPay
- A SEPA clearing house
For a complete list of error codes and the reasons for payment failure, please refer to the European Payment Council guide on R-transactions. SlimPay has also compiled a list of common payment failure codes for direct debit, which you can find on our Help Center.
In light of all this, SlimPay compiles a list of all your payment issues and generates a daily reporting file which can be viewed in the Back Office. This file contains a header, a list of the payment issues, and a footer.
Please note: This file can be split into two; one file for SlimPay payment issues and another file for clearing house payment issues.
Header
The header contains a single line with the following structure (remember, fields are separated by a semi-colon, ;):
| 1 | 2 | 3 | 4 | 5 to 7 | 8 | 9 | ||
|---|---|---|---|---|---|---|---|---|
| "0" | Creditor reference Up to 35 characters |
File reference Up to 35 characters |
Merchant's company name Up to 35 characters |
Empty | Date YYYY-MM-DD |
Number of issues | ||
Below is an example of a header line:
0;testCreditor;REJ-20200927-171015-307;testCompany;;;;2020-09-27;2;Payment Issues
Each payment issue line consists of up to 21 values containing information about:
- the initial transaction
- the payer or the payee, depending on whether the initial transaction is a direct debit (payer) or a credit transfer (payee)
- the specific payment issue
| Column number | Description | Format | Max length |
|---|---|---|---|
| 1 | "5" for a direct debit "6" for a credit transfer issue |
Integer | 1 |
| 2 | Subscriber reference | Alphanumeric | 35 |
| 3 | Initial transaction reference | Alphanumeric | 35 |
| 4 | Payer/payee company name | Alphanumeric | 35 |
| 5 | Payer/payee full name | Alphabetic | 103 |
| 6 | Payer/payee email address | Alphanumeric | 70 |
| 7 | Payer/payee phone number | E.164 standard E.g. +33612345678 | 16 |
| 8 | Date of initial transaction | ISO 8601 Date format (e.g. 2020-07-25) | 10 |
| 9 | Amount of initial transaction | Decimal | 19 |
| 10 | BIC (SWIFT code) | Alphanumeric | 11 |
| 11 | IBAN | Alphanumeric | 34 |
| 12 | BBAN Bank code | Alphanumeric | |
| 13 | BBAN Branch code | Alphanumeric | |
| 14 | BBAN Account number | Alphanumeric | |
| 15 | BBAN Key | Alphanumeric | |
| 16 | Label of initial transaction | Alphanumeric | 140 |
| 17 | Invoice reference | Alphanumeric | 35 |
| 18 | Type of issue | "REJ" before execution date "RET" after execution date "REB" transaction disputed by debtor | 3 |
| 19 | Date of payment issue | ISO 8601 Date format (e.g. 2020-07-25) | 10 |
| 20 | Issue code | Alphanumeric | 4 |
| 21 | Issue description | Alphanumeric | 128 |
| 22 | Mandate reference | Alphanumeric | 35 |
Below is an example of two payment issues: a direct debit issue and a credit transfer issue:
6;REF-00123;;;;;;2020-07-27;200.00;CMCIFR2A;FR7610278001114441111122508;10278;00111;44411111225;08;;;;2020-08-05;BE05;Creditor account not found;
5;REF-Cli-65412;REF-Trans-01000012;;John Doe;flebeuf@gmail.com;+33677553322;2020-08-13;218.40;CRLYFRPP;FR7644444555556666666666677;44444;55555;66666666666;77;First payment of tuition fees for 2012;Bill_1647;REJ;2020-08-22;AM04;Insufficient funds;Footer
The footer contains a single line with the following structure:
| 1 | 2 to 8 | 9 | ||||||
|---|---|---|---|---|---|---|---|---|
| "9" | Empty | Total amount of rejected or returned payments | ||||||
Below is an example of a footer line:
9;;;;;;;;418.40;Below is an example a complete payment issues file:
0;testCreditor;REJ-20200927-171015-307;testCompany;;;;2020-09-27;2;
6;REF-00123;;;;;;2020-07-27;200.00;CMCIFR2A;FR7610278001114441111122508;10278;00111;44411111225;08;;;;2020-08-05;BE05;Creditor account not found;
5;REF-Cli-65412;REF-Trans-01000012;;John Doe;flebeuf@gmail.com;+33677553322;2020-08-13;218.40;CRLYFRPP;FR7644444555556666666666677;44444;55555;66666666666;77;First payment of tuition fees for 2012;Bill_1647;REJ;2020-08-22;AM04;Insufficient funds;
9;;;;;;;;418.40;Handling payment issues
For information on how to recover failed payments, please refer to SlimPay Help Center.