THE GUIDE · FOR TEAMS

The onboarding plan is a reading order.

Payments onboarding usually means a wiki of stale links and a month of overheard acronyms. Replace the reading half of it: send one link, and the guide's chapter order does the sequencing.

THE PITCH, IN PLAIN WORDS

The chapters are already in teaching order: every idea lands before the idea that needs it. So the onboarding plan is simply the reading order. A new hire reads under an hour a day for five days, takes the short quiz at the end of each chapter (nobody sees the score), and keeps the tools open once they're on the desk.

Free. No accounts, no seats, nothing to install. Progress lives in each reader's own browser and goes nowhere else.

25
chapters, drawn and animated
hours of reading, total
<1
hour a day for one week
$0
per seat — no ads, no sponsors
WEEK ONE

Five days, five themes.

Reading times are measured, not guessed — they match the header of every chapter. Tick the boxes on paper or in your head; the site also remembers finished chapters per browser.

Day 1THE LEDGER UNDERNEATH≈ 53 MINWhere money lives, and why a bank is a promise.
The history of money12 MIN What money actually is17 MIN The banking system10 MIN Blockchain from zero14 MIN
THE KICKOFF MESSAGE

Paste this into Slack.

Written to be sent as-is on someone's first morning. Edit freely; the link is the part that matters.

Welcome to payments 👋 Before anyone throws acronyms at you: read tokensandrails.com in chapter order, top to bottom. It is the onboarding plan — under an hour a day for a week. Take the short quiz at the end of each chapter; nobody sees your score. Once you're on the desk, keep the glossary and the decline decoder open in a tab. Bring anything confusing to Friday's catch-up.
COMMON QUESTIONS

Before you send the link.

DO YOU TRACK WHAT OUR TEAM READS?
No. There are no accounts and nothing is sent anywhere. Finished chapters and quiz scores are saved in each reader's own browser, only there, and the chapter drawer has a clear-my-progress button. If your security team asks: the site is static files, no backend.
CAN WE COPY THIS INTO OUR INTERNAL WIKI?
Link it rather than copy it. Payments rules change and figures on the site get re-verified and corrected as they do (each chapter shows its last-verified date). A pasted copy goes stale quietly; a link always serves the corrected version.
OUR HIRE IS AN ENGINEER / RISK ANALYST / PM. SAME ORDER?
Keep days one and two for everyone, then let the role trails on the Learn page take over: there is a trail each for engineers, operators, product managers, founders and the crypto-curious, skipping what that role doesn't need.
Ramping a specialist instead of a generalist? The role trails skip what they don't need →

Want the whole library first? Browse the full curriculum →