Interview / Learning brief
Understand payments in 10 days (No Charge)
Your notes
In simple terms / 01
What this means in plain language
Organizes free online reading into a ten-day study path for building a basic understanding of payment systems.
A short learning plan makes the payments field less overwhelming. Instead of trying to master every scheme at once, a learner can move from basic actors and account entries to clearing, settlement, domestic rails, cross-border banking, SWIFT, SEPA, card concepts, message standards, and exception handling. Each day should combine reading with a small exercise, such as drawing a flow or explaining a message in plain language. Ten days will not create an expert, but it can provide a useful map and vocabulary for deeper study at no cost.
Complete lesson / 02
Understand the full idea, step by step
From the outside, payments looks like a wall of acronyms — SWIFT, SEPA, RTGS, pacs, nostro — with no visible door. Here is the door: ten days, one layer per day, every layer added to the same single payment story. No fees, no sign-ups, no prior knowledge. By day ten you will not be an expert, but you will have something more useful — a map on which every new term has a place.
Why layers, not topics
Most beginners fail by studying payments as a pile of separate topics — a SWIFT day, a SEPA day, a compliance day — and end up with definitions that do not connect. This plan works differently: it follows one transfer from the moment a customer taps Send to the moment the receiving bank is truly paid, and each day widens the lens on that same journey. Parties first, then the journey, then the machinery underneath it, then the borders it can cross, then the messages that describe it, then the things that go wrong. Every acronym arrives with a place already waiting for it.
The ten-day arc
Day 1 — Who is involved. Payer, payee, and their banks; who keeps whose account, and why a bank can only ever edit its own books. Draw the four parties and label whose ledger each account lives in.
Day 2 — The life of one payment. Follow a single transfer end to end: instruction, validation, the debit, the interbank message, clearing, settlement, the credit, the notifications. This is the spine every later day hangs from.
Day 3 — Clearing versus settlement. The two words beginners merge and practitioners never do. Working out who owes whom is clearing; discharging that obligation is settlement. Add gross versus net, immediate versus deferred.
Day 4 — Domestic rails. Batch systems for everyday volume, instant schemes for speed, and the central bank's RTGS — real-time gross settlement — system for large and urgent payments. One country, several machines, different promises.
Day 5 — Crossing a border. Correspondent banking: banks holding accounts for other banks, nostro and vostro, and why a payment abroad becomes a chain of book entries rather than one hop.
Day 6 — The messages. SWIFT as a secure messaging network and standards body — not a settlement system — and the MT messages banks have exchanged for decades. Read one MT103 slowly, field by field.
Day 7 — ISO 20022. The newer standard: a methodology and data dictionary, not just a format. Meet pain, pacs, and camt messages and see how much more structure they carry than their MT ancestors.
Day 8 — Schemes and rulebooks. What a scheme actually is — a rulebook every participant implements — using SEPA as the worked example: one euro area, several schemes, classic and instant.
Day 9 — When it goes wrong. Rejects, returns, recalls, and investigations. Exceptions are not the system failing; they are the system working. Trace one failed payment and name who owns each step of fixing it.
Day 10 — The controls, then teach it back. Sanctions screening and anti-money-laundering basics: why banks check the parties in a message and what happens when a name matches a list. Then the final exercise — explain a full cross-border payment, out loud, to someone else.
The daily method
- One topic
- A single focused subject per session — depth beats coverage
- One drawing
- Redraw the day's flow from memory: actors, messages, account entries
- Five terms
- Define the day's key terms in your own words — no copying
- One question
- Write down the thing you still cannot answer; date it
- Teach-back
- End the plan by explaining one payment end to end to another person
You may be wondering: can ten days really be enough?
Enough for a map, not for mastery — and the map is the valuable part. After day ten you will be able to place any new scheme, message, or job title in context, follow a payments conversation without drowning, and know precisely which gaps you want to close next. Practitioners spend years on the territory; ten days buys you the map they navigate it with.
COMMON CONFUSION
“The fastest route in is to start with the message formats — memorize the MT103 fields and the pacs.008 elements, and the rest will follow.”
Fields without a flow are furniture without a house. A message only makes sense as a description of a business event — who owes whom, which bank is asking which bank to do what. Learn the events first (days 1–5); the formats (days 6–7) then read almost like forms. Learners who start from the fields usually end up memorizing tags they cannot connect to money.
REMEMBER IT
Whenever a topic stops making sense, return to the four questions: who owes whom · what instruction was exchanged · where did the obligation change · what evidence confirms it. Every payments concept, on any rail, in any country, is an answer to one of these four.
STRICTLY SPEAKING
Strictly speaking, this plan is an editorial construction — a study sequence, not an industry standard. The free sources it points you toward differ in depth and currency: scheme rulebooks are precise but versioned, official explainers are stable but general, and anything with numbers in it — limits, timings, participation — changes. Record the source and date for any detail that could move, and prefer the current rulebook over any summary of it, including ours.
FOR NOW, REMEMBER
- Ten days, one layer per day, all layers added to the same single payment story — parties, journey, machinery, borders, messages, failures, controls.
- Every session ends with something you made: a drawing, five definitions in your own words, one logged question.
- Business events before message formats — fields only make sense as descriptions of who owes whom.
- When lost, ask the four questions: who owes whom, what instruction, where did the obligation change, what evidence confirms it.
- The plan buys a map, not mastery — day ten's teach-back tells you honestly which territory to study next.
TRY IT YOURSELF
It is Day 6. Riya is deep inside an MT103 sample, and the field tags have stopped meaning anything — 32A, 50K, 59, blur. What is the best next move?
Day 1 starts now. Watch Riya's rent leave her account and discover the one idea the entire field is built on: the message asks, the ledgers answer.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
Learn core actors before studying individual message types.
- 02
Daily exercises turn reading into usable understanding.
- 03
The plan is a foundation, not an expert qualification.
Practical use cases / 04
Where you would use this
A new business analyst follows the plan before joining a payment-engine project.
A developer studies one rail daily to understand integration requirements.
A career changer builds a vocabulary for payments interviews and networking.
Worked example / 05
Put the idea into a real situation
Illustrative plan: day one covers payer, payee, PSP, and accounts; day two covers clearing versus settlement; later days introduce domestic and cross-border routes, SWIFT, SEPA, ISO 20022, and exceptions. After each session, the learner draws one flow and writes five terms in their own words. On the final day, they explain an end-to-end transfer to a colleague and note topics requiring deeper study.
Evidence & review / 07
Evidence & review
Study plan — scheme- and jurisdiction-neutral orientation; individual days reference concepts (RTGS, SEPA, SWIFT, ISO 20022) taught in their own sourced lessons.
What this brief simplifies: The ten-day sequence is an editorial teaching construction, not an industry curriculum. Day summaries compress concepts that their dedicated lessons state precisely (e.g. SWIFT's role, clearing vs settlement).
Sources for this brief2
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal · Ten-day study sequence
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
- Market practiceMarch 2003 edition
A glossary of terms used in payments and settlement systems ↗ — CPSS (now CPMI), Bank for International Settlements · Clearing, settlement, and payment system terminology used in the day descriptions
Terminology has evolved since this edition; newer CPMI publications refine some definitions.