Payments
In addition to creating payments for individual customers using SlimPay’s REST API, you can also process direct debits for many customers simultaneously by depositing a CSV file in your SFTP folder. This means you can collect dozens, hundreds or even thousands of payments in a single operation!
Please note: The documentation below is for processing batch SEPA direct debit payments only, using our v2 file format. To inject files for payment orders using v1 format, refer to our remittance file documentation for the appropriate file structure.
If your SlimPay account is configured with creditor entities, all batch direct debit orders must be injected using the v1 format.
In order to deposit a CSV file into your SFTP folder, the file must contain:
- Information about you, the merchant
- The number of transaction items to be expected in the file
- The name of the columns used (not all of them are mandatory)
- The transactions themselves
Merchant information
The file begins with the following line:
| 1 | 2 | 3 | 4 |
|---|---|---|---|
| "0" | "PAYMENTS" | Creditor reference | Merchant company name |
Below is an example of a merchant information line.
0;PAYMENTS;testCreditor;TestCompany;This is followed by one line to define the direction of payments and the currency. The structure of this line is:
| 1 | 2 | 3 | 4 | 5 |
|---|---|---|---|---|
| "1" | Item type:
|
Number of items of this type | Total amount (decimal) |
Currency:
|
Below is a line example designating three direct debit transactions, totalling €89.99.
1;IN;3;89.99;EUR;The next line defines which columns you intend to use in the file, based on your needs. Some columns are mandatory, others are optional. The order you place the columns is irrelevant, as long as the values entered below them correspond correctly.
Columns generic to each transaction
| Title | Description | Mandatory | Format | Max length |
|---|---|---|---|---|
| PAYMENT_DIRECTION |
|
 | Alphanumeric | 35 |
| PAYMENT_REFERENCE | Unique payment reference Generated by SlimPay if empty |
Alphanumeric | 35 | |
| PAYMENT_AMOUNT | Amount | | Decimal | 19 |
| PAYMENT_EXEC_DATE | Execution date If empty, SlimPay will apply the earliest possible date |
ISO 8601 Date format (2020-09-25) | 10 | |
| PAYMENT_LABEL | Label which will appear on the bank statement of the customer | | Alphanumeric | 140 |
Direct Debit Columns
| Title | Description | Mandatory | Format | Max length |
|---|---|---|---|---|
| MANDATE_REFERENCE | Unique mandate reference |
Alphanumeric | 35 |
Transactions
The rest of the file consists of the transactions themselves, each allocated one line. Make sure the values you enter are aligned with the appropriate columns.
Below is an example of a complete file, with three direct debit transactions, totalling €89.99.
0;PAYMENTS;testCreditor;TestCompany;
1;IN;3;89.99;EUR;
PAYMENT_DIRECTION;PAYMENT_AMOUNT;PAYMENT_LABEL;MANDATE_REFERENCE;
IN;29.99;Monthly Deezer payment;SLMP_0003214617;
IN;35.00;Invoice number 024;SLMP_0008231982;
IN;25.00;First transaction;SLMP_0004127437;Reporting file
If the file is acknowledged, you can expect a reporting file to let you know the total amount processed.