Payment stuck in processing
USD 48,250 from a London corporate to a Singapore supplier, held after screening.
USD 48,250.00 · SWIFT gpi · Status ACSP, held
Best: not attempted yet
Mission Control
Run payment operations. Four live missions: a payment stuck in processing, a duplicate submission, a clearing rejection, and an API timeout. Investigate the evidence, make the decisions, and see the outcome scored. All data is synthetic and for education only. Nothing here connects to a real banking system and nothing moves real money.
How to play. Pick a mission below. Read the transaction, the lifecycle, the timeline and the logs. Use the investigation tools in any order, each tool reveals one finding and earns 5 points the first time you use it. Then answer the two decision points. Each correct decision earns 20 points. The outcome appears after both decisions, and your best score is saved in this browser only.
Best score: not attempted yet
Mission dashboard
Duplicate payment submission
The same EndToEndId submitted twice within minutes after a slow response.
EUR 32,150.00 · SEPA Credit Transfer · First settled, second held
Best: not attempted yet
Clearing rejection
A EUR 120,000 SEPA credit transfer rejected at clearing with a pacs.002 rejection.
EUR 120,000.00 · SEPA · Status RJCT, reason AC01
Best: not attempted yet
API timeout
A payment API call timed out after 30 seconds with no response.
USD 9,850.00 · API initiated · Status unknown
Best: not attempted yet
Teaching note. These missions are simplified for learning. Real screening, clearing and API behaviour varies by bank, scheme and system, and real cases involve more checks, approvals and audit steps than shown here. Status codes used include ACCP (accepted), ACSP (accepted, settlement in process) and RJCT (rejected). Reason code AC01 means incorrect account number. Check current scheme rules before relying on any of this in live work.