The Lists section contains data used to categorize payments, statements, group entities, partners. The user can also benefit from using black lists and white lists functionalities. The application allows configuration of entities members of the group and their bank accounts. It also allows adding partners and suppliers as external entities, also with their linked accounts. There is a list of banks available, with BIC codes, bank names and addresses. This prevents human error and allows every transaction to be enriched with contextual data. Here's a short demo of the Lists section: https://fintp.org/topic/fintpc-lists-demo/

Scope FinTP-SEPA functionality, processing Euro payment instructions in compliance to SEPA regulation and schemes, includes 2 components: FinTP-SCT for processing credit transfer instructions and FinTP-SDD for processing direct debit instructions.
This document is intended to outline requirements for assuring the connction between a bank internal applications and the SWIFT network in order to process outgoing SEPA Credit Transfer transactions.
Overview FinTP-SCT ensures the processing of Euro payment instructions (credit transfer) corresponding to the business flows in relation with the correspondent bank (XYZ Bank) which acts as a CSM. FinTP-SCT is processing the credit transfer – pacs.008 – low value payment instruction
The base functionality of FinTP assures:
• Technical integration with back-office applications
• Duplicate detection for outgoing transactions
• Conversion into/from SWIFT FIN and XML ISO20022 format
• Embedded message routing mechanism, with two routing modes: based on rules and on content
• Advanced capabilities for transaction searching and reporting
• Transactions tracing and logging into history database
• Persistent end-to-end transactions
• Communication breaks detection along with connection restoring
• Security module, including the management of groups and users, profiles, functions etc.
• Transactions archiving
• Facilities to view and manage transactions (processing, monitoring, authorization, exceptions investigation, reporting)
• Administration: users/groups settings, message routing and formatting rules, lists management, audit logs inquiring, data archiving
Reports:
• Search reports
Business Flow Outgoing instructions flows – credit transfer instructions
[table id=3 /] Notes: 1. Duplicate criteria – all business transaction data, except reference
2. Authorization – the authorization mode will be configured at queue level depending on the bank policies:
• Manual authorization – users will select and manually authorize the instructions
• Scheduled authorization – specific cut-off periods will be configured, at cut-off all instructions in the specific queue will be automatically
authorized. • Real-time authorization – instructions will not be stopped
Response to outgoing transactions flows
FinTP could send alarms to Back Office when a final negative status for each transaction will be received. The following type of responses can be expected:
• Transaction manually rejected from FinTP
• Transaction rejected by SAA/SWIFT network
• Transaction rejected by XYZ Bank
Support files
The configuration files and scripts required to run this scenario are available on GitHub :
• Release Notes
• Connector configuration files
• Server configuration files
• Scripts needed to start/stop and monitor the deployment
• Database scripts for the MT103 and pacs008 message types
You will also need to download the precompiled in FinTP binaries from the Releases section of this site, or build your own binaries using the code published on GitHub.
For additional instructions see the wiki of every project :
• Installation instructions for details on how to deploy the binaries and configuration file for a connector.

ScopeFinTP-SEPA functionality, processing Euro payment instructions in compliance to SEPA regulation and schemes, includes 2 components: FinTP-SCT for processing credit transfer instructions and FinTP-SDD for processing direct debit instructions.
This document is intended to outline requirements for assuring the connection between a bank internal applications and the SWIFT network in order to process outgoing SEPA Credit Transfer transactions.
Overview FinTP-SCT ensures the processing of Euro payment instructions (credit transfer) corresponding to the business flows in relation with the correspondent bank (XYZ Bank) which acts as a CSM. FinTP-SCT is processing the credit transfer – pacs.008 – low value payment instructionThe base functionality of FinTP assures:
• Technical integration with back-office applications
• Duplicate detection for outgoing transactions
• Conversion into/from SWIFT FIN and XML ISO20022 format
• Embedded message routing mechanism, with two routing modes: based on rules and on content
• Advanced capabilities for transaction searching and reporting
• Transactions tracing and logging into history database
• Persistent end-to-end transactions
• Communication breaks detection along with connection restoring
• Security module, including the management of groups and users, profiles, functions etc.
• Transactions archiving
• Facilities to view and manage transactions (processing, monitoring, authorization, exceptions investigation, reporting)
• Administration: users/groups settings, message routing and formatting rules, lists management, audit logs enquiring, data archivingReports:
• Search reportsBusiness FlowOutgoing instructions flows – credit transfer instructions[table id=3 /]
Notes:1. Duplicate criteria – all business transaction data, except reference2.
Authorization – the authorization mode will be configured at queue level depending on the bank policies:
• Manual authorization – users will select and manually authorize the instructions
• Scheduled authorization – specific cut-off periods will be configured, at cut-off all instructions in the specific queue will be automatically authorized.
• Real-time authorization – instructions will not be stopped
Response to outgoing transactions flows
FinTP could send alarms to Back Office when a final negative status for each transaction will be received. The following type of responses can be expected:
• Transaction manually rejected from FinTP
• Transaction rejected by SAA/SWIFT network
• Transaction rejected by XYZ BankSupport files
The configuration files and scripts required to run this scenario are available on GitHub :
• Release Notes
• Connector configuration files
• Server configuration files
• Scripts needed to start/stop and monitor the deployment
• Database scripts for the MT103 and pacs008 message typesYou will also need to download the precompiled in FinTP binaries from the Releases section of this site, or build your own binaries using the code published on GitHub.For additional instructions see the wiki of every project :
• Installation instructions for details on how to deploy the binaries and configuration file for a connector.

Scope FinTP-SEPA functionality, processing Euro payment instructions in compliance to SEPA regulation and schemes, includes 2 components: FinTP-SCT for processing credit transfer instructions and FinTP-SDD for processing direct debit instructions.
This document is intended to outline requirements for assuring the connection between a bank internal applications and the SWIFT network in order to process outgoing SEPA Credit Transfer transactions.
Overview
FinTP-SCT ensures the processing of Euro payment instructions (credit transfer) corresponding to the business flows in relation with the correspondent bank (XYZ Bank) which acts as a CSM. FinTP-SCT is processing the credit transfer – pacs.008 – low value payment instruction
The base functionality of FinTP ensures:
• Technical integration with back-office applications
• Duplicate detection for outgoing transactions
• Conversion into/from SWIFT FIN and XML ISO20022 format
• Embedded message routing mechanism, with two routing modes: based on rules and on content
• Advanced capabilities for transaction searching and reporting
• Transactions tracing and logging into history database
• Persistent end-to-end transactions
• Communication breaks detection along with connection restoring
• Security module, including the management of groups and users, profiles, functions etc.
• Transactions archiving
• Facilities to view and manage transactions (processing, monitoring, authorization, exceptions investigation, reporting)
• Administration: users/groups settings, message routing and formatting rules, lists management, audit logs inquiring, data archiving
Reports:
• Search reports
Business Flow
Outgoing instructions flows – credit transfer instructions
[table id=3 /] Notes:
1. Duplicate criteria – all business transaction data, except reference
2. Authorization – the authorization mode will be configured at queue level depending on the bank policies:
• Manual authorization – users will select and manually authorize the instructions
• Scheduled authorization – specific cut-off periods will be configured, at cut-off all instructions in the specific queue will be automatically
authorized. • Real-time authorization – instructions will not be stopped
Response to outgoing transactions flows
FinTP could send alarms to Back Office when a final negative status for each transaction will be received. The following type of responses can be expected:
• Transaction manually rejected from FinTP
• Transaction rejected by SAA/SWIFT network
• Transaction rejected by XYZ Bank
Support files
The configuration files and scripts required to run this scenario are available on GitHub :
• Release Notes
• Connector configuration files
• Server configuration files
• Scripts needed to start/stop and monitor the deployment
• Database scripts for the MT103 and pacs008 message types
You will also need to download the precompiled in FinTP binaries from the Releases section of this site, or build your own binaries using the code published on GitHub.
For additional instructions see the wiki of every project :
• Installation instructions for details on how to deploy the binaries and configuration file for a connector.

FINkers United is an open source community, created by Allevo. Allevo contributes the documentation and source code of its projects on GitHub, liked from www.fintp.org.

GNU GPL v3 license. In short, this license recognizes the contribution of each developer. And it forces any redistributors to pass on software derived from the initial code under the same conditions. In other words, code published in the open source space can be modified by any third party, but it needs to be republished into the open source space, using the same license and giving the author credit for its initial contribution. More about GNU GPL here: http://www.gnu.org/licenses/gpl.html

There is a short video showing how to do this on our forum: https://fintp.org/topic/how-to-test-an-xslt-file/