Roadmap FinTech

Part 01 · Start here

How to use this roadmapكيف تستخدم هذه الخارطة

Read it all once without clicking anything. Then go back to the parts that matter for your work.

5 minute read

Share this:

The point of the first pass is not memorising. It is drawing a map in your head. If you stop at every external link you will leave with scattered facts and no whole picture. Read first, then deepen where it serves your work.

Every topic here is written to stand on its own. The few links that remain are citations for what the text claims, not homework you must finish before moving on. If a word is new, its definition sits directly under where it is used on the topic page.

Why not open the links and go deep on the first pass?

This is the first piece of advice you will resist, so it deserves a reason rather than an instruction.

Imagine reading about authorisation, then opening a link about fees, which leads to a page on disputes, which lands you in a forty-page document on network rules. Two hours later you have five precise facts and have lost the thread you were following.

The reason is that those facts have nowhere to live yet. Information sticks when it finds something to attach to, and the general map is that something. Someone reading about dispute fees before they know what an acquirer is has memorised a number hanging in mid-air.

You do not memorise a city map on your first visit. You learn where the sea is, where the market is, and where the district you need sits. Then you dig into the street you are going to live on.

First pass: read, do not branch

Walk the phases in order from "Start here" through what matters for your lane. Do not open external resources on this pass. You do not memorise a city on a first visit. You learn where the sea is, where the market is, and which neighbourhood you need.

If you see a topic marked optional, skip it on the first pass without guilt. The roadmap is built to give you a complete path without demanding every side branch on day one.

Prefer a short repeated session over one long day. Forty-five minutes on one or two topics sticks better than three hours mixing reading with ten articles about and mada. On this pass you want the names and the boxes to stay in your head, not to empty the regulator's website.

Tie every idea to something you have seen

After you finish a topic, ask: where have I seen this? A shop receipt, a fuel hold on a card, a transfer on , a "paid" screen in an app. An idea that never sticks to a live example dissolves within a week.

If you cannot find an example from your day, open one screen in a financial app you already use. Then name which of the six payment boxes appears there, or which stage of a payment the screen represents. That short exercise beats rereading the paragraph.

Try a second drill after the banks-and-partnership topic: open the app's terms and search for the sponsoring bank or licensed entity. If you find it, you have tied the partner-bank idea to a real page, not a theoretical summary. If you cannot find it, ask why it is missing. The product may not hold money at all.

How to use progress marks

The roadmap lets you mark topics you have finished. Use the mark after you can explain the idea to a non-specialist in two sentences, not after your eyes have passed over the text. The mark is a small promise to yourself, not a page counter.

If you return after a break, you do not have to start at the beginning. Start from the last topic you marked and read the first sentence of the next one. If it makes sense, you are ready to continue. If it looks like jargon, go back exactly one topic and redo it.

Do not widen the rewind circle beyond that at first. Going back three full topics every time creates a sense of retreat and kills continuity. One prior topic is enough to repair most gaps if you marked honestly.

Read with your lens, not someone else's

You picked a lane in the previous topic. Carry that choice into how you read. A product person slows down at customer moments, price and friction. A compliance person slows at SAMA, licensing and . An engineer slows where money can be lost or duplicated. A data person slows at the metric definition. An operations person slows at the partner, the incident and the settlement timetable.

It is fine to skim a paragraph outside your lane. The mistake is stopping to master every paragraph at the same depth, sliding back into the learn-everything habit that exhausted you before. Context is enough for the neighbour. Mastery is for your lane.

What you do not need to do

You do not need a separate glossary notebook when the definition already sits under the topic. You do not need to read a hundred-page global standard because a topic pointed at it. The standard is there for later verification. The text here is written to spare you that in the first learning stage.

Do not compare your pace with someone else's. A reader from software engineering moves quickly through systems topics and slows on licensing. A reader from compliance does the reverse. The right pace is the one that leaves the idea explainable.

Do not collect twenty external resources in a list before you finish the phase. The list soothes a false sense of progress while the map in your head is still incomplete. Finish the phase first, then pick one resource that serves one question from your work.

Right after this phase

When you finish "Start here", move into money basics without reopening every link you saw along the way. There you will meet what a bank balance really is, the payment lifecycle, interest, and the Saudi and GCC context. You will need the six boxes, the partner-bank idea and your lens so those pages do not turn into floating jargon.

If a money-basics topic seems to repeat an idea from here, do not skip it automatically. Read the first sentence: it may restate with a sharper angle, not empty repetition. The difference shows if you ask: can I explain this sentence to a colleague from outside the field?

After the whole roadmap

When you finish the core path, return to the part closest to your work and read it again slowly. The second reading is not empty repetition. It is catching detail you skipped because the big picture was not ready yet.

On the second pass you may open the links and documents. By then you know what you are looking for: a specific SAMA circular, an explanation of mada fees, a sarie settlement guide, or a Nafath page for developers. Search guided by a question from your work beats general browsing on the first pass.

The short version

  • First time through: read, do not click. You are drawing a map, not memorising it.
  • Anything marked "Optional" can be skipped completely at first.
  • Tie each topic to something real you have seen: an app, a fee, a receipt.

Check your understanding

Answer before reading the explanation. Getting one wrong here is worth more to you than a lucky guess.

  1. 1.Why not open the links and go deep on the first pass?
  2. 2.When should you mark a topic as read?
  3. 3.You come back after a few weeks away. Where do you restart?
  4. 4.A topic is marked optional. What do you do with it on the first pass?

This is a learning guide built from field experience. It is not legal, regulatory or investment advice, and it does not replace qualified professional counsel. FinTech rules change quickly and vary by country, so check the primary source before you make a decision that matters.

Back to the roadmap

How to use this roadmap | Roadmap FinTech