Payments Academy

Payment Exception Investigation Simulator

Twenty-one exceptions, as operations sees them. Read the symptom, pick the first investigation action you would take, and learn immediately whether it is right, what evidence it produces, and what happens next. Work through all 21 and see your score for correct first try investigations. Each scenario carries a timestamped message trail (MsgId, UETR, EndToEndId, status code) where one exists, because an investigation is proved by its audit trail, not by prose alone.

Score: 0 correct first try out of 0 investigated (21 scenarios)

1. Insufficient funds

What operations sees. A pacs.002 arrives with reason code AM04. The customer account held USD 8,000, but the payment was USD 25,000. The customer calls to ask where the money is.

What is your first investigation action?

Reject, return, recall, cancellation, reversal, repair, retry, investigation: keep them distinct

Reject (pacs.002 RJCT): before settlement. Nothing settled, the customer is re-credited in full. Return (pacs.004): after settlement, when the creditor agent cannot credit (for example AC04 closed account). Only the creditor agent sends it. Recall / cancellation request (camt.056): the debtor agent asks for funds back, before settlement or after credit; the answer is a pacs.004 with reason FOCR (positive) or a camt.029 (negative). Reversal: a distinct R-transaction, for example pacs.007 for a SEPA direct debit reversal, or an automatic scheme reversal on a Faster Payments timeout. Repair: the same payment with corrected data, re-released as a new instruction with a fresh InstrId and the same EndToEndId. Retry: resending the same message with the same MsgId and UETR, only after proving the original was not received. Investigation: a pacs.028 status request (answered by pacs.002) when a payment already sent has no confirmation; for SCT Inst it is sent if no response arrives after 25 seconds.