101 — How Things Work
Explainers that start at the beginning. Each guide takes one piece of payment or financial infrastructure — a protocol, a rail, a settlement model — and explains what it is, how the money and the messages actually move, and what it means if you are building on it.
Most explanations of payment infrastructure are written either for engineers who already know the vocabulary, or for readers who will never need it. This section is for the people in between: operators, founders, compliance teams and investors who have to make decisions about a system they did not build.
Each guide takes one thing and explains it properly; what it is, how a transaction actually moves through it, where the money sits at each step, what it costs, and what it does not do. Where a subject has real regulatory weight, that is covered too, because the mechanics and the licensing question are rarely separable.
How Things Work: Guides in This Section
How to use these
Every guide is written to be read on its own. The pillar page for each subject answers the whole question in one place; the pages beneath it go deeper on the parts that need it; the mechanics, the economics, the security model, the regulatory position.
They assume no prior knowledge of the subject and no tolerance for hand-waving. Where a number matters, it is given. Where something is genuinely unsettled; a standard still in draft, a regulatory position that has not been tested — that is said plainly rather than smoothed over, because a confident answer to an open question is worse than no answer.
If a subject touches licensing, banking or settlement in a way that affects what you are building, the relevant licensing pathways and banking structures are set out under Solutions.