Outbound
The sample only uses the MT103 and Pain.002 outbound external formats, but a mapper is implemented for each
business level mapping requirement shown in the following table. An exception is for client acknowledgments,
where a business purpose is shared.
| Name | Format | Business purpose |
|---|---|---|
| ISF to MT | MT103 | Payment Initiation |
| ISF to Repair Request | MT103 | Repair Request |
| ISF to Liquidity Request | MT103 | Liquidity Request |
| ISF to Pain.002 | Pain.002.001.03 | Client Acknowledgment / Client Batch Acknowledgment |
All of the mappers that use the MT103 format use a common mapping procedure to map the ISF payment transaction to the MT103 block 4 fields. The common mapping procedure is called Map103Body(), and is defined in FIN103ToISFMapper_finsample.esql. The mappers differ in the way they map the location (element name and path) and the type of ISFPayment (ISFPayment, or ISFLiquidityResponse, and so on).
The following figure shows the outbound mappers.
