SlimPay Developer Center

  • Web API
  • File API
  • Resources
  • Overview
  • Checkout by link
  • Payments
  • Remittance Files
  • Payment Issues
  • Account Statement Report
 

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 and card, 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, ;):

12345 to 789
"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/card payment (payer) or a credit transfer (payee)
  • the specific payment issue
Column
number
Description FormatMax length
1"5" for a direct debit or card payment issue
"6" for a credit transfer issue
Integer1
2Subscriber reference Alphanumeric35
3Initial transaction reference Alphanumeric35
4Payer/payee company name Alphanumeric35
5Payer/payee full name Alphabetic103
6Payer/payee email address Alphanumeric70
7Payer/payee phone number E.164 standard
E.g. +33612345678
16
8Date of initial transaction ISO 8601 Date format
(e.g. 2020-07-25)
10
9Amount of initial transaction Decimal19
10BIC (SWIFT code) Alphanumeric11
11IBAN Alphanumeric34
12BBAN Bank code Alphanumeric
13BBAN Branch code Alphanumeric
14BBAN Account number Alphanumeric
15BBAN Key Alphanumeric
16Label of initial transaction Alphanumeric140
17Invoice reference Alphanumeric35
18Type of issue "REJ" before execution date
"RET" after execution date
"REB" transaction disputed by debtor
3
19Date of payment issue ISO 8601 Date format
(e.g. 2020-07-25)
10
20Issue code Alphanumeric
4
21Issue description Alphanumeric128
22Mandate reference Alphanumeric35

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:

12 to 89
"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.

 
SlimPay
  • Developer Center
  • Help Center
  • Website
  • Web API
    • Overview
    • Guides
    • Reference
    • Browser
    • Clients
  • File API
    • Overview
    • Checkout
    • Payments
    • Payments Issues
    • Account Reporting
  • Resources
    • FAQ
    • IBANs