BadPaymentRequestRequiringRepair.103

The bad payment message fails the validation implemented in FTM. The validation is run on the mapped ISF and checks that the InterbankSettlementAmount currency is valid (valid is defined as being listed in the FTM classification table). In the case of the MT103 format, this field has been mapped from field 32A. In the bad message, this field contains DEM, which is one of the pre-euro currencies.

After submitting the bad 103 payment message that requires repair, you should be able to search for and list the transmission and transaction objects. A repair request is sent to the repair service as shown in the following figure.

Figure 1. Transmission search: bad payment
SampAppSearchTransBad.jpg

The following figure shows that the payment origination transaction has a status of waiting for repair and the status of the repair request transaction is waiting for response.

Figure 2. Transaction search: bad payment
SampAppSearchTxnBad.jpg

If no response is received within 10 minutes, the repair request transaction enters an alert state as shown in the following figure. The timeout value is defined by setting REPAIR_REQUEST_TIMEOUT_DELAY to 600 in the Value table.

Figure 3. Alerts: repair timeout
SampAppRepairTimeout.jpg

After a repair response is received, the payment should run to completion. Transmission search results: bad payment/repair shows all of the transmissions and Transaction search results: bad payment/repair shows the transactions.

Figure 4. Transmission search results: bad payment/repair
SampAppSearchTransBadRepair.jpg
Figure 5. Transaction search results: bad payment/repair
SampAppSearchTxnBadRepair.jpg

The following figure shows the state transitions for the bad payment as it is processed and successfully repaired.

Figure 6. Payment origination transaction: bad payment/timeout/repair state history
SampAppTxnPaytBadMisc.jpg