File management overview
There will often be times when you as a merchant will want to transmit multiple payment orders simultaneously, rather than making individual calls to the API. SlimPay’s File API allows you to process high volumes of data, meaning that dozens, hundreds or even thousands of orders can be injected in a single operation.
At the same time, SlimPay offers merchants a range of output files giving information regarding the status of payments, account balances and other important data.
Here you will find a summary of the various input and output files you can expect to encounter when using SlimPay’s File API. For more detailed information on each of the files, click on the links included in the tables below.
|Input file||Purpose||Format||Further information|
|SEPA direct debits (v1 format)||Create direct debits||CSV||Remittance files|
|SEPA direct debits (v2 format)||Create direct debits||CSV||SFTP payments|
|SEPA credit transfers||Create credit transfers||CSV||Remittance files|
|Update bank accounts||Update debtor bank account details||CSV||Remittance files|
|Back Office user creation||Create Back Office users||CSV||Remittance files|
|Mandate imports||Import existing debtor mandates||CSV||Remittance files|
|Create direct debit plans||Create recurrent direct debit plans||CSV||Remittance files|
|Modify direct debit plans||Update recurrent direct debit plans||CSV||Remittance files|
|Cancel direct debit plans||Disable recurrent direct debit plans||CSV||Remittance files|
|Checkout by link||Create direct debits by link||CSV||Checkout by link|
|Output file||Purpose||Format||Further information|
||Acknowledge correctly formatted remittance files||CSV||File overview|
||Alert incorrectly formatted remittance files||CSV||File overview|
||Display results of remittance files||CSV||File overview|
|Account statement report||Periodic statement of transactions||CSV, XML||Account statement report|
|NOP file||Summary of cancelled / non-executed payments||CSV, XML||More information below|
|REJ file||Summary of rejected SDD, SCT or card payments||CSV, XML||More information below|
|CRE file||Summary of rejected card payments||CSV, XML||More information below|
|Mandate report||Summary of created or amended mandates||CSV||More information below|
Following the injection of a remittance file, SlimPay generates a results file (
.res), which identifies any potential errors regarding the quality of the injected data. For example, a mandate’s unique reference may already exist, or a customer’s IBAN may be invalid etc.
Results files are only generated for orders to update bank accounts, import mandates, create Back Office users or to create, modify or cancel recurring payment plans. For direct debit and credit transfer orders, a
.res file is not created by default, because the outcome of the payment orders is not known at the time the file is processed. If a payment order does fail, SlimPay generates an R-transaction file outlining the specific payment issues.
In the event that payments fail, SlimPay generates a file detailing the reasons why the transactions were not successful. A merchant can nominate to have R-transaction files generated hourly, daily, weekly or monthly.
R-transaction file names have different prefixes, depending on the type of payment failures it contains:
- An NOP file is a summary of all transactions that were rejected by SlimPay before execution for internal system reasons
- A REJ file is a summary of all transactions that were rejected by the banks after execution (separate REJ files are created for SDD, SCT and card transactions)
- A CRE file is a summary of card transactions that were rejected by the banks after execution
A merchant can choose to combine the NOP and REJ files into a single REJ, rather than receiving them separately. If you would like to activate this option, get in touch with our Customer Care team.
Merchants can nominate to receive a mandate report, which offers a complete overview of all SEPA mandates that have been created, amended or revoked for a given period of time. The file is transmitted in CSV format.
As an alternative to the standard SlimPay CSV format for R-transaction files and Account Statement Reports, a merchant can opt to receive these as CAMT files (camt.054 and camt.053 respectively). The file is transmitted in XML format.
If you would like to activate this option, get in touch with our Customer Care team.