FEX use cases > Payments Initiation

Payments Initiation

Additional deliverable objects for product configuration

Overview

User profile

Payment Initiation is a service provided by SWIFT, based on a set of XML messages. The Payments Initiation business area contains messages that are used to initiate credit transfers and direct debits. It also contains a set of messages to instruct related operations.

Provided services

Axway Financial Exchange provides the following messages for Payment Initiation:

CustomerCreditTransferInitiation: Sent by the initiating party to the forwarding agent or debtor agent. This message requests the movement of funds from the debtor account to a creditor.
PaymentStatusReport: Sent by an instructed agent to the previous party in the payment chain. This message informs this party about the positive or negative status of an instruction (either single or file). It can also report on a pending instruction.
PaymentCancellationRequest: Sent by the initiating party or any agent, to the next party in the payment chain. It requests the cancellation of an instruction previously sent
CustomerPaymentReversal: Sent by the initiating party to the next party in the payment chain. This message reverses a payment previously executed.
CustomerDirectDebitInitiation: Sent by the initiating party to the forwarding agent or creditor agent. This message requests single or bulk collection(s) of funds from one or various debtor's account(s) for a creditor.

Processing

On the customer side: Receiving requests from back-end applications, translating these requests into the corresponding XML messages, sending these messages via InterAct to the destination bank, acquiring and routing the messages to back office applications.

On the bank holding the account side: Receiving request XML messages via InterAct, transmitting these requests to back-end applications, acquiring the responses from back-end applications and transmitting responses via InterAct.

Axway Financial Exchange products

Product	Configuration characteristics
Gateway (mandatory)	Real-Time mode for FileAct
Integrator (mandatory)	Use Integrator to handle Payment Initiation SWIFT-XML messaging: See generic SWIFT-XML messaging platform use case Use the following Integrator objects, depending on processing needs: XML Classifier SWIFT-XML Wrapper SWIFT-XML Unwrapper XML Validator XML Business-Document Use the following Integrator Connectors: SWIFTNet Gateway Sentinel JMS for MQSA
SWIFTNet Portal (optional)	Message recycling features
Sentinel (optional)	Monitoring features

Additional deliverable objects for product configuration

Product	Add-on object
Gateway	Adaptable pre-built configuration samples: Generic SWIFT Remote Site object Generic SWIFTNet Trading Partner object for loop transfers in InterAct and FileAct protocols
Integrator	Payment Initiation SWIFT-XML message repository (four messages) (If used with SWIFTNet Portal) pre-built SWIFT-XML message validator Integration-Process
SWIFTNet Portal	Payment Initiation SWIFT-XML message repository
Sentinel	Tracked Objects for: Integrator Gateway SWIFTNet Portal Pre-built technical displays (Dashboards) for monitoring: SWIFT-XML exchanges and Integrator message flow Gateway transfers (if Gateway is used) SWIFTNet Portal message handling (if SWIFTNet Portal is used)

Documentation

Axway Financial Exchange documentation set
SWIFTNet Portal documentation
Gateway documentation set
Integrator documentation set
Sentinel documentation set