The inbound process converts a SWIFT FIN formatted message to an XML transaction.
In a basic message flow, inbound processing consists of the following components and steps. For an illustration of the components available in the construction of a message flow, see Using a Channel to Construct a Message Flow. You will define the components in the configuration instructions in Sample Configuration for Inbound Processing: SWIFT to XML.
Inlet
The preparser ensures that the message is converted to a structurally correct SWIFT XML message. The transformation templates that are provided in the Ebix are used to transform the structure of the document.
Set the option in the preparser to match the year of the SWIFT messages.
The iWay Integration Solution for SWIFT supports two preparsers, which are described in Preparsers.
Validation
The inbound SWIFT message is validated for structure and content. The published SWIFT FIN standards and user implementation guides define element types (for example, numeric, alpha, or date) and describe rules to apply for validation.
For example, here is a typical date segment in an inbound SWIFT message:
:98A::STAT//20190513
The Qualifier ("STAT") is validated against an allowed code list. The date is also validated. The tag is validated to insure correct structure.
Route
In the sample inbound channel, a process flow is used to apply specific logic.
For more information on available services, see the iWay Service Manager User's Guide.
Outlets
Outlets define how messages leave a channel at the end of a process. In the sample inbound channel, a Passthrough outlet is used. All write operations are handled in the process flow.