Inbound
The sample only uses the MT103 and Pain.001 inbound external formats, but a mapper is implemented for each
business level mapping shown in the following table.
| Name | Format | Business purpose |
|---|---|---|
| MT To ISF | MT103 | Payment Origination |
| Pain.001 To ISF | Pain.001.001.03 | Batch Payment Origination |
| Repair Response to ISF | MT103 | Repair Response |
| Liquidity Response to ISF | MT103 | Liquidity Response |
| Gateway Ack to ISF | MT103 | Gateway Acknowledgment |
All of the mappers that use the MT103 format use a common mapping procedure to map the MT block 4 fields to the ISF payment transaction. The common mapping procedure is called Map103Body(), and is defined in FIN103ToISFMapper_finsample.esql. The mappers differ in the way they map the ISF header (Business Concept, and so on) and the type of ISF transaction created (ISFPayment, or ISFLiquidityResponse, and so on).
The following figure shows the inbound mappers.
Note: The sample application also deploys the ISF To ISF mapper, which is supplied as part of FTM Core, to manage mapping of the inbound ISF command message. This message can be generated
using the FTM console to cancel an invalid payment that is not repaired.