HOME / Learning brief
WELCOME
Your notes
In simple terms / 01
What this means in plain language
Introduces the author's learning community and its aim to share approachable payments knowledge with industry newcomers.
Payments can feel difficult because one transaction touches customers, banks, messages, rules, accounts, and infrastructure. This learning hub is designed to make those connections easier to see. It starts with plain-language concepts, then adds message examples, end-to-end flows, operational exceptions, and interview practice. Readers should treat the material as educational guidance and confirm scheme, regulatory, and institution-specific details with current authoritative sources. The most effective way to learn is active: redraw a flow, explain it to someone else, test an example, and record the questions that remain.
Complete lesson / 02
Understand the full idea, step by step
A salary lands. Rent goes out. A refund crawls back over three days and nobody can say why. Payments touch every working day of your life, yet almost nowhere is the machinery behind them actually taught. That is the gap this site exists to close — patiently, from zero, with nothing assumed.
One payment story, told in layers
Everything here hangs off a single idea: follow one transfer all the way through, and keep two paths separate in your head. The information path is the instruction and the messages between banks — who pays, who receives, how much. The money path is the account entries — debits, credits, and the moment banks square up with each other. Messages carry information; only ledger entries move value. Each lesson adds one layer to that same story: parties, then messages, then clearing and settlement, then what happens when something fails. New acronyms stop being noise once they have a place in the story.
What is on the site
- Article lessons
- Short teaching briefs like this one — the beginner spine reads in order
- Flow player
- Step-through diagrams of real payment journeys, one hop at a time
- Message Lab
- Annotated real message formats — MT and ISO 20022 — on the dark board
- MT ↔ MX map
- How legacy SWIFT messages line up against their ISO 20022 successors
- Screening and settlement labs
- Interactive controls: watch a sanctions check or a settlement cycle run
- Glossary and checks
- Plain-terms definitions, plus applied questions at the end of every lesson
How to spend your first hours
Read the beginner spine in order — each lesson ends with a link to the exact next one, so you never have to guess where to go.
After a lesson that describes a journey, open the matching flow in the flow player and step through it. Seeing the hops fixes them far better than reading about them.
When a lesson shows a message, find it in the Message Lab and read the annotated fields. The formats look forbidding for about ten minutes; then they look like forms.
Answer the applied check at the end of every lesson honestly, before reading the explanations. The checks ask you to judge a situation, not to recite a definition — that is where understanding shows.
Keep a question log. Write down what you cannot yet answer and which lesson raised it. Most entries resolve themselves two or three lessons later; the rest tell you what to study next.
You may be wondering: do I need a banking background to start?
No. The beginner spine assumes no prior knowledge of banking, payments, ledgers, or messaging — every term is introduced before it is used, and every acronym is expanded the first time it appears. If you have ever paid rent or split a dinner bill, you already have all the raw material the first lessons build on.
COMMON CONFUSION
“Once I have read these lessons, I can use them as operating instructions — configure a system, answer a customer, decide a real case.”
The lessons teach concepts, and concepts here are accurate — but real services differ by provider, scheme, country, and rulebook version. Timing, limits, fees, and legal rights are set by the current rulebook and your institution's own procedures, not by a teaching example. Use the site to know which questions to ask; use current official sources to answer them before acting.
STRICTLY SPEAKING
Strictly speaking, every named party in these lessons — Riya, Arjun, Asha Traders, Bank Alfa, Nordbank, and the rest — is fictional, and every scenario is labelled SYNTHETIC — TRAINING ONLY. Real institutions appear only in their verified public roles, such as a scheme body publishing a rulebook. Amounts are exact and plausible but invented. When a fact could change over time, the lesson points at the authoritative source instead of freezing a number.
FOR NOW, REMEMBER
- The whole site follows one payment story, adding a layer per lesson — information path and money path kept deliberately separate.
- Lessons teach; the flow player, Message Lab, and the labs let you watch the same ideas run.
- Every lesson ends with an applied check and a link to the exact next step — read the spine in order.
- Examples are educational and synthetic: verify scheme, provider, and legal detail against current official sources before applying anything.
TRY IT YOURSELF
A lesson here walks through a transfer that reaches the payee in seconds. Riya sends a real payment from her own bank and it takes until the next morning. What should she conclude?
Riya has her map of the site. Next: the ten-day study plan — a day-by-day path from her first question to explaining a full payment journey to someone else.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
Learn the payment journey one layer at a time.
- 02
Use diagrams and examples to test understanding.
- 03
Confirm production decisions with current official guidance.
Practical use cases / 04
Where you would use this
A payments newcomer follows a guided path from basic parties to ISO 20022 messages.
A team lead assigns one article and one flow exercise for weekly learning sessions.
An interview candidate uses the hub to identify weak areas before practicing answers.
Worked example / 05
Put the idea into a real situation
Start with a simple bank-to-bank transfer. Name the payer, payee, their PSPs, and any infrastructure. Draw one line for messages and another for account value. Add the successful path first, then branch into a rejection before settlement and a return afterward. Finally, write three questions you cannot yet answer and verify them in reliable documentation. This illustrative exercise turns passive reading into a reusable mental model.
Evidence & review / 07
Evidence & review
Site orientation — scheme- and jurisdiction-neutral; no scheme-specific claims made.
What this brief simplifies: Describes the site's teaching method and materials only. The two-path model (information path vs money path) is the site's standard simplified teaching frame; real journeys add fees, FX, intermediaries, and exceptions, which later lessons introduce.
Sources for this brief1
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal · Site orientation; fiction and verification rules
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.