Practice: hands-on payment operations
Reading about a payment is one thing. Running one, breaking it, investigating it and fixing it is how it sticks. These five practical experiences use synthetic educational data only. Nothing here connects to a real banking system and nothing moves real money. Your progress is stored in this browser only, and there is no sign-in and no payment to use any of it.
1. Mission ControlRun payment operations. Four live missions: a payment stuck in processing, a duplicate submission, a clearing rejection, and an API timeout. Investigate, decide, and see the outcome scored.
2. Payment Failure Investigation LabA payment failed. Read the transaction record, the events and the error, find the likely root cause, pick the next investigation step, and compare with the reference solution.
3. ISO 20022 Mapping WorkbenchMap fields between ISO 20022 messages. Inspect the XML, map source to target, define transformations, validate required elements, and generate the resulting XML. Includes a pain.001 to pacs.008 exercise.
4. Reconciliation War RoomMatch payment instructions, clearing records, settlement records and bank statement entries. Find the missing, the duplicates and the mismatches, then resolve the exceptions.
5. Payments Business Analyst StudioDo the BA work. Turn a realistic payments scenario into business requirements, user stories, Gherkin acceptance criteria, process flows, field mappings and test cases, with feedback on your actual submission.
How scoring works. Each experience scores your decisions and stores your best score in this browser only. Scores never leave your device. Reset any experience from its own page, or reset all practice progress below.
Already comfortable with the simulators? These five experiences sit on top of them: Simulators, Interactive Trace, Message Explorer, Labs, ISO Lab.