FinTech, explained from the beginning

You start with a simple question about money and end at the systems that move it, in Saudi Arabia and elsewhere. Most writing in this field is either a regulator's handbook nobody opens until they are hired, or a clipped blog post, and this is an attempt at a third option. Free to read, no signup.

Every topic is a page you can read on its own. Start at part 1, or go straight to whatever your work touches.

Part 01
Start here
You do not need any finance background to start. This part gives you the words and the big picture. Everything after it will make more sense once you have these.
After this part
- Explain what FinTech is to a friend, in under a minute
- Name the people and companies involved when you pay with a card
- Choose which part of the field to focus on first
Part 02
Money and banking basics
This is the "fin" half of FinTech. It is the part most technical people skip, and it is the part that makes everything afterwards click. None of it needs maths beyond percentages.
After this part
- Explain the difference between paying by card and transferring between accounts
- Explain why "paid" on the screen does not mean the money has arrived
- Work out what a loan really costs over a year
- Name which Saudi authority is responsible for which kind of company
Part 03
FinTech products
People hear "FinTech" and think of payments. Payments are the biggest slice, but only one slice. Read these once so you know what exists; you only need to go deep on the one you work in. Crypto, stablecoins, and tokenisation sit in the later Web3 phase.
After this part
- Name six kinds of FinTech product and a real company doing each
- Guess which Saudi authority would license a given product
- Explain why one payment system can serve a wallet, a shop and a payroll app
- Know that crypto and token products have their own later phase
Part 04
Payment rails
This is the densest part of the roadmap and the most useful one in a job interview. Take it slowly. Every one of these is just a different route the money can take, with different costs, speeds and risks.
After this part
- Draw a card payment with all six parties, showing the money moving the opposite way to the approval
- Say one real trade-off between paying by card and transferring between accounts
- Explain why a local transfer is instant but the same amount takes days to reach another country
- Say what ISO 20022 is and why banks spent ten years moving to it
Part 05
Web3 and digital assets
The name claims a third generation of the internet. What actually got built on the idea is money and ownership, not social networks nobody owns. So this part separates six families of product that one news story will happily blend together: crypto, stablecoins, wallets and exchanges, on-chain payments, tokenised assets, and DeFi. In Saudi Arabia nobody licenses retail trading yet, while the central bank has piloted the same technology between banks. Those are two different facts and worth keeping apart.
After this part
- Separate crypto, stablecoin, CBDC, and a tokenised real-world claim
- Name the product roles of wallet, custodian, exchange, and on/off-ramp
- Explain why stablecoins appear in cross-border and treasury payment designs
- Point to DeFi and chain infrastructure without confusing them with a bank licence
Part 06
RegTech products
Earlier parts showed products that move or grow money, traditional rails, and the Web3 lane. This part shows the products that sit beside them: tools compliance and risk teams buy so those products can launch and stay open. Read it as a product tour, then open the next phase for permission and fair-treatment rules.
After this part
- Name four RegTech product types and what each system of record holds
- Explain why a FinTech buys a KYC vendor instead of photographing IDs alone
- Separate AML monitoring software from the legal duty to file a report
- Point to a local identity rail such as Nafath when classifying an identity product
Part 07
Regulation and licensing
This part is not legal training. It covers permission to operate and fair treatment of customers. The software teams buy to meet AML, KYC, and fraud duties sits in the RegTech products phase you just left.
After this part
- Explain the difference between a sandbox and a licence
- Name who is accountable when a FinTech partners with a licensed bank
- Explain why fair outcomes matter beyond burying fees in terms
- Point back to RegTech tools when asked how evidence gets produced
1. Licensing and sandboxesالترخيص والبيئة التجريبية Sandbox
2. Consumer protectionحماية العملاء
Part 08
Data protection and privacy
This is a deeper part, kept separate on purpose. Read the first two topics, which apply to everyone. The rest is reference material for when a particular law becomes yours.
After this part
- List the handful of principles that appear in every privacy law in the world
- Explain why asking for consent is often the weakest way to justify using data
- Recognise when moving data to another country needs formal approval
- Know which questions to hand to a lawyer instead of answering yourself
Part 09
Product management
Financial products carry friction that ordinary apps do not: identity checks, legal wording, risk rules. You cannot remove that friction. The craft is in where you put it.
After this part
- Sketch a signup flow and mark where the compliance steps go
- Point at two places a financial app loses the customer's trust
- Read a pricing page and work out what the customer really pays in a year
- Pick metrics you could defend if someone audited them
Part 10
FinTech engineering
Three properties separate financial software from everything else: every movement has to balance, every operation has to be safe to repeat, and every action has to leave a trail someone can follow months later. Non-engineers should read the first two topics anyway, because they explain a lot of otherwise baffling product behaviour.
After this part
- Explain double-entry bookkeeping and why financial systems store movements rather than balances
- Explain what an idempotency key is and the exact bug it prevents
- Name three things you would require before accepting a webhook
- Describe what happens to a wallet top-up when step three times out
Part 11
Launch and operations
Launch discipline in financial services is stricter than in most software, for one blunt reason: rolling back a bad release does not roll back the money that moved while it was live.
After this part
- Write a launch checklist with a named owner for every line
- Say what evidence an auditor would want about a control you rely on
- Name the first role you would apply for and the two skills you still need

The roadmap

Start here

Money and banking basics

FinTech products

Payment rails

Web3 and digital assets

RegTech products

Regulation and licensing

Data protection and privacy

Product management

FinTech engineering

Launch and operations