You don't need to read all of this. Grab 20% and the other 80% follows.
Core share · Of 32 pages, only 3 concepts truly matter. The rest are footnotes to these three.
Start with just these
- Payment state flow (pending -> approved -> settled) — half the doc re-explains this from different angles. Get the state transitions and the refund, error, and settlement chapters all read as "exceptions to this flow".
- The 3 permission tiers — the rest of the feature docs are variations on "who can do what", so knowing the tier differences means you don't memorize individual features.
- How to read error codes — not memorizing 60 codes, but one rule: 'first digits = area, last digits = cause'. That decodes codes you've never seen.
Why this is the 20%
- The remaining chapters (exceptions, FAQ, per-screen guides) are the three cores applied to specific situations. Grasp the principle first and look up the cases when needed.
- Memorize cases first and you stall on anything new — which is why the 'vital 20%' sits on the principles, not the cases.
30-second recap
Payment is 'pending -> approved -> settled', people are '3 permission tiers', problems are 'code front/back rule'. Those three sentences carry today's work. Search the rest when you get stuck.





