Overview > Main uses of FEX

Main uses of FEX

Three different solutions

FEX4B

FEX4C

FEX for SWIFTNet

Three different solutions

The market that FEX addresses is organized along three main themes:

Financial services institutions, including banks
Bank customers: corporates, administrations, and so on
SWIFTNet network users

The FEX offering is therefore organized into three solutions:

FEX4B (FEX for Banks)
FEX4C (FEX for Corporates)
FEX for SWIFTNet

The division of FEX into these three categories is just a way to simplify the presentation and deployment for well-known needs. As it relies on a highly flexible framework, FEX can be adapted to any specific need.

FEX4B

FEX4B is a multi-channel financial service collaboration interface, used by banks and other financial institutions to manage their exchanges between their back-end applications and the various partners they are engaged in a B2B relation with. These partners can be corporate customers, other banks and financial institutions, Market infrastructures and service providers (ACH, RTGS, CSD, regulators, etc.).

The following figure illustrates FEX deployed as a multi-channel collaboration interface for financial institutions.

FEX4C

FEX4C can be deployed as a financial flow concentrator enabling corporates to:

Concentrate financial message flows originating in several back-end applications
Distribute incoming financial flows to several back-end applications

The following figure illustrates FEX deployed as a financial flow concentrator in a national and international corporate payment environment.

FEX for SWIFTNet

SWIFTNet is often seen as a specific channel, involving its own message services, vocabulary, partners and activities. It is frequently managed within the institutions as a standalone domain, with dedicated administration and operation teams. For this reason, Axway provides FEX for SWIFTNet as a specific product offering.

FEX for SWIFTNet covers the needs of SWIFTNet connectivity through the FileAct and InterAct protocols. It provides:

The connectivity to the SWIFTNet network through the RA-HA API of the SWIFTAlliance Gateway (SAG)
Full support of all the protocol features:
- FileAct real-time Send requestor & responder, Receive requestor & responder
- FileAct Store & Forward with the use of output channels
- InterAct including the Application to Application synchronous mode (Business response given in the InterAct response payload)
- The management of the Service profiles (ASP)
- The filtering of the exchange against the RMA authorization
Full management of the RMA authorization within an RMA application (planned for FEX 2.9)
Full integration of the SWIFTNet channel with the other channels provided by FEX.

FEX for SWIFTNet is certified by SWIFT as a SWIFTNet V7 Messaging Interface

FEX for SWIFTNet addresses three levels of needs:

A simplified SWIFTNet connectivity for customers whose only need is to make use of FileAct or InterAct.
SWIFTNet connectivity for services requiring the RMA filtering mechanism to prevent unsolicited exchanges.
A full integration of the SWIFTNet channel in FEX, be it FEX4B or FEX4C, in order to process with the same level of added-value and integration, the document received through SWIFTNet and the documents received through the other channels.

These three levels are addressed through three packages:

Gateway SWIFTNet 7 Connectivity:
This package provides the only FileAct and InterAct protocols, including the ASP management.
FEX SWIFTNet 7 Connectivity:
This package provides, beside the services offered in the previous package, the RMA Filtering and as an option the full service of a RMA application (UI to manage and monitor the issued Authorization to receive and the received Authorization to send)
FEX with SWIFTNet:
This packaging is simply the full integration of the SWIFTNet connectivity such as carried by the previous package beside the services provided by FEX.