This paragraph describes the principles of the different methods of communication between the creditor and the SEPA Payment Suite platform. Use of one method does not preclude use of another method.
A table summarizing the methods supported by SEPA Payment Suite functionality may be found in Summary of modes of exchange by function.
File transfer
This method is useful when exchanges are initiated outside SEPA Payment Suite, particularly in contract management systems or by digitization service providers.
A file is sent to SEPA Payment Suite which carries out a number of checks (compliance with file syntax, consistency of control data, etc.) in order to integrate it into the platform. In particular, the issuer must be authorized to carry out the action(s) stated in the file.
In response, an acquisition report is generated for the file issuer: it shows the result of file integration (OK or KO) and states the reason for rejection where necessary. If the integration is successful, each registration of the file will have its own status and reason.
Files transferred to the application are in the standard SEPA Payment Suite format (XML or CSV). Other formats are supported for requests for direct debits (See Conversion of national orders. These formats are described in the product interfacing document. SEPA Payment Suite can also accommodate other formats at the specific request of the client.
Files can be transferred to the application either automatically (machine to machine) or manually (via the file import function available on the platform screens).
Web services
This method enables the various applications of the creditor’s or bank’s information system to submit requests to SEPA Payment Suite in real time in the form of a call for web services. Web services also make it easier to integrate the functionalities of the platform into websites or other external third-party applications. They are one of the resources which make it possible to implement remote banking (Online banking: architecture and principles).
When it receives a request, SEPA Payment Suite checks that it complies with the expected interface, processes it and generates the appropriate response. If it is rejected, SEPA Payment Suite states the reason.
The web services offered by the SEPA Payment Suite platform are described in the product interfacing document.
This exchange method is a software option.
Graphical User Interface
The SEPA Payment Suite Graphical User Interface (GUI) offers a number of screens which provide access to the various functionalities of the platform. In particular, forms are available to enable users to set up mandates or direct
debits. When the information entered does not match the expected data, a warning message appears on the screen: it states the rejection reason so that the user can make the necessary corrections.
The GUI is part of the software standard.
Summary of modes of exchange by function
The following table lists the various product features of the SEPA Payment Suite product and whether they can be accessed by file transfer, web services and/or GUI:
| File transfer | Web Services | GUI | |
|---|---|---|---|
| Migration of a mandate | Yes | No | No |
| Creation of the mandate | Yes | Yes | Yes (+ file import) |
| Double validation of the mandate | Yes | Yes | Yes |
| Modification of a mandate | Yes | Yes | Yes |
| Revocation of a mandate | Yes | Yes | Yes |
| Suspension of a mandate | Yes | Yes | Yes |
| Activation of a mandate | Yes | Yes | Yes |
| Mandate query and search | Yes | Yes | Yes |
| Form generation | Yes | Yes | Yes |
| Form query and search | Yes | Yes | Yes |
| Paper mandate generation | Yes | Yes | Yes |
| Electronic mandate generation | No | Yes | Yes |
| Copy of a mandate | No | Yes | Yes |
| Management of the payment schedule | Yes | Yes | Yes |
| Creation of unitary Direct debit | Yes | No | No |
| Direct debit application | Yes | Yes | Yes |
| Double validation of debits | Yes | Yes | Yes |
| Management of pre-notifications | Yes | Yes | Yes |
| Cancellation request | Yes | Yes | Yes |
| Debit query and search | No | Yes | Yes |
| Correction and recycling of abnormality transactions | No | Yes | Yes |
| Abnormality transactions query and search | No | No | Yes |
| Bank collection query and search | No | Yes | Yes |
| Double validation of bank collections | No | Yes | Yes |
| Modification of bank collections | No | Yes | Yes |
| Cancellation of bank collections | No | Yes | Yes |
| Bank collection file query and search | No | Yes | Yes |
| Received R-Transaction query and search | No | Yes | Yes |
| Alert management | No | Yes | Yes |
| Management of notifications | No | Yes | Yes |
| Management of the debtor client database | Yes | Yes | Yes |
| Set up a reseller organization | No | No | Yes |
| Set up a creditor organization | No | No | Yes |
| Set options | No | No | Yes |
| Configure notification templates an organization | No | No | Yes |