The Complete Guide to Card Payments, Banking & Fintech

When you pay with a card at a store or café, everything seems to happen in seconds.

In reality, the payment goes through several participants and steps:

• The card is read by the terminal — you tap, insert, or swipe it.

• The request is sent to the merchant’s bank — the terminal forwards the transaction details.

• The payment network (Visa, Mastercard, etc.) routes the request to the customer’s bank.

• The issuing bank checks available funds, limits, and risk parameters.

• The response travels back through the same chain.

• The terminal displays the result (“approved” or “declined”) and prints the receipt.

The entire process usually takes less than 2–3 seconds.

Learn how money actually moves in a card payment. We break down the Merchant Discount Rate (MDR), how it's split between the acquirer and the issuer, what interchange is and who sets it, and why credit cards generate more revenue for banks than debit cards.

Every card payment goes through three stages — and most people have no idea. In this lesson, we break down authorization, clearing, and settlement: what actually happens at each stage, why the money isn't taken instantly, and why that's a deliberate design decision rather than a technical limitation.

Authorization is the first stage of every card payment — and it all happens in seconds. In this lesson, we break down exactly what gets checked, how the request travels through the chain, what a hold actually means for your account, and why not all declines are the same.

In this lesson, we explore the second stage of a card payment: clearing.

You’ll learn how daily transaction batches are sent from the acquirer to the payment network, how they are routed to issuing banks, and how an authorization hold becomes a finalized charge.

By the end, you’ll clearly understand why clearing is the moment funds are officially debited from the cardholder’s account — but the merchant still hasn’t been paid yet.

Settlement is the final stage of a card payment — the moment banks actually settle up with each other and the merchant gets paid. In this lesson, we break down how the payment network calculates net settlement amounts, how funds move between issuers and acquirers, and how the money ultimately reaches the merchant's account.

In this lecture, we break down the core building blocks of ISO 8583 messages.

You’ll learn what Data Elements are, why they matter, and how they carry the real substance of every card transaction — from the card number and amount to timestamps, response codes, and terminal identifiers.

We’ll go through the most commonly used fields in real-world payment flows and explain how fixed-length and variable-length elements (LLVAR / LLLVAR) work in practice.

By the end of this lesson, you won’t just recognize field numbers like DE2, DE4, or DE39 — you’ll understand how they shape every authorization, ATM withdrawal, and card payment behind the scenes.

Payment ecosystems are more complex than they appear. In this lesson, we go beyond the basic four-party model and look at the real infrastructure behind every card transaction — payment gateways, acquiring and issuing processors, and PSPs. You'll learn what each player actually does, why they exist, and how to choose between a standalone gateway, a processor, and an all-in-one PSP for your business.

Currency conversion is one of those things that happens invisibly — until you check your statement and wonder why you paid more than expected. In this lesson, we break down exactly what happens when Emma pays by card in a foreign currency: who converts the money, when the rate is locked, and what fees are applied. You'll learn the difference between network conversion through Visa or Mastercard and Dynamic Currency Conversion (DCC) — and why one of them almost always costs more than the other.

Every payment leaves a paper trail — and that trail is built on double-entry accounting. In this lesson, we break down how accounting actually works in payment systems: what the balance sheet equation means, why debit and credit behave differently depending on the account type, and how a single card payment generates journal entries across three general ledgers simultaneously. You'll also finally understand why your card is called a debit card — and what that name reveals about how banks record your transactions.

Payment cards have been around for nearly a century — but most people have no idea how dramatically they've changed. In this lesson, we trace the full arc of that transformation: from embossed metal charge plates and mechanical imprinters in the 1930s, to EMV chips, contactless NFC payments, mobile wallets, and tokenization today.

Along the way, you'll learn why Diners Club changed everything in 1950, how the magnetic stripe made payments faster but opened the door to skimming fraud, why France introduced the chip card in 1984, and what tokenization actually means under the hood.

By the end of this lesson, you'll have a clear mental model of how each technology built on the last — and why the payment card looks and works the way it does today.

Every bank card you carry contains more information than most people realize. In this lesson, we go element by element through the anatomy of a bank card — front and back — and explain exactly what each component does and why it exists.

You'll learn how the 16-digit PAN is structured, what the BIN tells the payment network in milliseconds, and how the Luhn algorithm silently catches typos before a transaction is ever sent. You'll understand why the code on the back of your card isn't stored anywhere in readable form — not even at your bank. And you'll see why the magnetic stripe and the EMV chip represent fundamentally different approaches to security: one stores a photograph, the other holds a live conversation.

By the end of this lesson, you'll be able to look at any bank card and know precisely what you're looking at — and why every element is there.

Every card transaction starts with a question the bank can't answer by looking at you: is this the real cardholder, or a fraudster? In this lesson, we break down exactly how banks solve that problem — through the three fundamental factors of authentication.

You'll learn why cybersecurity defines identity verification as something you know, something you have, and something you are — and how each of these abstract principles maps directly onto the mechanisms on your bank card. PIN. CVV. Biometrics. Each one addresses a different attack vector. Each one has its own vulnerabilities. And when layered together, they form a system that's dramatically harder to defeat than any single factor alone.

This lesson sets the foundation for the lessons ahead, where we'll go deep into the mathematics behind each method — how PINs are verified, how CVV codes are calculated, and what actually happens inside the chip when you tap to pay.

You enter a PIN dozens of times a month — but do you know what actually happens after you press the last digit? In this lesson, we go inside the PIN verification process and look at the real algorithms banks use to authenticate cardholders.

You'll learn how a PIN is generated in the first place — including the difference between the IBM 3624 natural PIN method and the Visa PVV approach, and why changing your card number can change your PIN. You'll understand why the PIN is never transmitted in plain text, how it gets re-encrypted at every hop in the payment chain, and what the HSM — the bank's tamper-proof security module — actually does with it. And you'll see why the bank never compares your PIN directly: only its mathematical fingerprint, the PVV, ever gets stored or compared.

We also cover offline PIN verification — the simpler but equally important algorithm that works entirely on the chip, with no bank or network involved. Including the one practical trap most cardholders don't know about: why changing your PIN remotely can silently break offline payments.

Every time you type a 3-digit code at online checkout, or tap your card at a contactless terminal, a verification process runs silently in the background. This lesson explains exactly what that process is, how it works mathematically, and why it keeps your card secure.

You'll learn the difference between three types of card verification codes — CVV1, CVV2, and dCVV — and understand why they exist as separate systems. We'll trace the full verification flow step by step: from the moment you enter your CVV2 on a website, through the acquiring bank and payment network, all the way to the issuing bank's Hardware Security Module. Then we'll do the same for dCVV — the dynamic code generated fresh by your EMV chip for every contactless tap.

Along the way you'll understand the Service Code, a three-digit value hidden in the magnetic stripe that defines your card's usage rules and feeds directly into the CVV calculation. You'll also see why dCVV protects against replay attacks in a way that static codes simply can't.

By the end of this lesson you'll know how CVV codes are computed, where they live, who verifies them, and what makes one stronger than another — the kind of detail that matters if you work in payments, card issuing, fraud prevention, or fintech product development.

In this lesson, we bring together everything covered in the card security section — PIN, Offline PIN, CVV1, CVV2, dCVV, and ARQC — and place them side by side to see how they fit together.

Each security value was designed for a specific transaction channel. Online PIN covers ATMs and card-insertion at POS terminals. Offline PIN handles chip cards in environments without a bank connection. CVV1 belongs to the magnetic stripe era. CVV2 protects every online and phone-based transaction. dCVV regenerates with every contactless tap. And ARQC — the Authorization Request Cryptogram — is what the EMV chip produces for every contact chip transaction.

You will also learn which values are static and which are dynamic, what actually changes when a card is reissued, why changing your PIN in a mobile app does not update the Offline PIN on your chip, and where all the critical calculations happen — inside Hardware Security Modules that never expose their keys.

By the end of this lesson, you will understand not just what each code is, but why it exists, where it works, and how these mechanisms combine into a layered defense system that protects every card transaction.

Not all bank cards work the same way — and that's by design. This lesson opens Section 3 by answering a question that sounds simple but has real depth: why do so many different card types exist, and what actually separates them?

The answer starts with one fundamental question: whose money are you spending? That single distinction divides all bank cards into two groups — cards that use your own funds, and cards that use the bank's. From there, four core card types emerge: debit cards, prepaid cards, credit cards, and charge cards. Each solves a different problem, serves a different customer, and operates on a different financial model.

By the end of this lesson, you will understand the primary classification axis used across the payments industry, the key mechanic that defines each card type, and the critical difference between revolving credit and a charge card — a distinction that trips up even experienced professionals.

Debit cards are the most widely used payment card in the world — but most people who carry one have never thought about how it actually works, or why banks issue them in the first place.

This lesson examines debit cards from both sides of the relationship. From the cardholder's perspective, you'll learn what makes debit cards simple and accessible, where their real limitations lie, and why hotels and car rental companies often refuse them — even though they work on the same Visa and Mastercard networks as credit cards. From the bank's perspective, you'll see how interchange fees, deposit base economics, and cross-selling turn a low-margin product into a strategically critical one.

The lesson also covers a common point of confusion: what happens when a debit card comes with an overdraft facility — and why it is still classified as a debit card, not a credit card.

By the end of this lesson, you will understand the full mechanics of a debit card, the regulatory landscape around debit interchange in key markets, and the business logic that makes debit cards the foundation of every retail bank's card portfolio.

A Starbucks gift card, a Wise travel wallet, a Paysafecard voucher — all prepaid, all built on the same core mechanic: load first, spend second, no bank account required.

This lesson explains how prepaid cards actually work, including details most courses skip: why a prepaid balance is a ledger entry rather than a bank account, how issuers manage FX risk when the card cannot go negative, and why gift card breakage is a meaningful revenue line. You will also learn why regulators impose spending limits on low-KYC prepaid and how companies like Wise and Revolut used prepaid wallets as their entry point into full banking.

By the end, you will understand prepaid cards from three angles — the cardholder experience, the issuer business model, and the regulatory framework that shapes both.

Credit cards are the most profitable product in retail banking — and the most misunderstood by the people who carry them. This lesson covers how they actually work, from both sides of the relationship.

You will learn what revolving credit means in practice, how the grace period can make a credit card completely free to use, and why carrying even a small balance changes the economics entirely. On the bank side, you will see how interchange and interest combine to make credit cards uniquely profitable — and why cash advance fees are priced the way they are.

The lesson also covers the billing cycle, credit score implications of missed payments, and how instalment plans offered by card issuers differ from standalone BNPL products.

Charge cards look like credit cards and work like credit cards — until the bill arrives. Then the difference becomes very clear: the full balance is due, every month, without exception. No minimum payment, no revolving option, no carrying debt forward.

This lesson covers how charge cards work, why that mandatory repayment rule is both the product's main appeal and its biggest constraint, and how banks make money without revolving interest income. You will also learn why charge cards are a premium niche in the US but effectively the default card type in Germany — a market difference that surprises most people in the industry.

By the end, you will understand all four card types by funding source — debit, prepaid, credit, and charge — and what distinguishes each one at a product and business model level.

Every card covered so far — debit, prepaid, credit, charge — can be issued in two completely different ways: as a physical card you carry, or as a virtual card that exists only in your phone. This lesson covers both, including the production process that explains why physical cards take 7-10 days to reach you, and the tokenisation mechanism that lets a virtual card pay at a physical terminal.

You will also learn why banks still invest heavily in physical cards despite the cost, why B2B virtual cards dominate the corporate payments market, and why neobanks issue a virtual card the moment you open an account rather than waiting for plastic to arrive.

Whether your card works in rural Japan or a market in Cairo comes down to one thing — which network is on the back of it. This lesson covers the geographic dimension of card classification: international networks built for global acceptance, and national networks built to keep payments at home.

You will learn what separates Visa, Mastercard, and Amex from schemes like UnionPay, RuPay, JCB, and Girocard — not just in acceptance, but in fee structure, geopolitical exposure, and strategic purpose. The lesson includes current market data: why RuPay's exclusive UPI linkage is reshaping India's credit card market, why UnionPay can no longer be called a purely domestic network, and what Capital One's $35 billion acquisition of Discover means for the global payments landscape.

Loyalty programs look like banks giving money away. They are not. This lesson covers the business logic behind every major reward format: cashback, bonus points, travel miles, partner discounts, and premium privileges. You will learn who funds each type, what the bank actually gets in return, and why cardholder lock-in is often the real goal.

The lesson also covers what most cardholders never think about: how interchange regulation explains why US rewards programs are far more generous than European ones, what breakage means and why issuers depend on it, and why cardholders who carry a revolving balance often pay more in interest than they earn in rewards.

Every card payment in the world belongs to one of two categories: Card Present or Card Not Present. That single distinction determines the fraud risk, interchange rate, and authentication requirements for the transaction. This lesson gives you the classification framework before the rest of Section 4 goes into each transaction type in detail.

When you insert a card or tap your phone at a terminal, the interaction looks simple. The mechanics behind it are not. This lesson covers the two Card Present transaction types: contact and contactless, including how NFC works, why the contactless limit exists, and why the authorization process is identical for both despite the very different capture methods.

When you tap your phone to pay, your real card number never leaves your bank. What reaches the merchant is a token — a device-specific digital substitute generated by the payment network. This lesson explains how that works, step by step, from the moment you add a card to Apple Wallet all the way through to the authorization response arriving at the terminal.

You will learn the nine-step provisioning flow: how the BIN identifies your issuing bank, what the Token Service Provider actually does, and why the Secure Element is the hardware component that makes the whole architecture trustworthy. You will also learn what happens at payment time — what three pieces of data leave the phone via NFC, how the dynamic cryptogram prevents replay attacks, and at exactly which point in the authorization chain the real card number first appears.

ATMs handle far more than cash withdrawals. This lesson covers the full range of ATM operations, how the authorization flow works for both withdrawals and deposits, and what makes ATM transactions technically different from POS card purchases.

The key difference: ATM transactions combine authorization and financial completion in a single message with no separate clearing step. You will learn why, along with the on-us vs. off-us distinction, the three-fee structure at third-party ATMs, how ATM interchange runs in the opposite direction from purchase interchange, and what happens when a dispense failure occurs.

Every card transaction belongs to one of two models: pull or push. In a pull payment, the recipient initiates the debit — the merchant requests funds from the cardholder's account. In a push payment, the sender initiates the transfer, pushing funds directly to the recipient. This lesson covers both models, including the counterintuitive reality that a standard card purchase is technically a pull even though the cardholder taps the terminal.

The second half covers Push to Card: how Visa Direct and Mastercard Send use the OCT (Original Credit Transaction) to move money in the reverse direction through the card network, why only a card number is needed to send a cross-border payout, and the use cases that have made push payments the backbone of gig economy disbursements, insurance payouts, and marketplace settlements.

PSD2 reshaped payments in Europe across three dimensions: it forced banks to open account access to licensed third parties (XS2A), mandated strong authentication for online payments (SCA), and significantly strengthened consumer rights. This lesson covers all three pillars, including the full terminology - PSU, ASPSP, TPP, AISP, PISP - and how Open Banking emerged from the AISP and PISP framework.

The SCA section explains the two-of-three factor requirement, clarifies a common misconception about where CVV fits in the authentication model, and covers both SCA exemptions and the transactions that fall entirely outside PSD2 scope. Consumer protection provisions are covered including the next-business-day refund obligation and the surcharge ban.

PSD2 left three structural gaps: it offered little protection against APP fraud, produced fragmented Open Banking with inconsistent APIs, and created an uneven playing field between banks and fintechs. PSD3 and PSR are the EU's response. This lesson covers what each document changes, why two separate legislative instruments are needed, and where the regulation stands as of 2026.

PSD3 refines authentication rules, introduces an accessibility requirement for SCA, and shifts liability to banks when customers are deceived into authorizing fraudulent payments. PSR standardizes Open Banking APIs, introduces a customer permissions dashboard, mandates Verification of Payee for all credit transfers, and gives customers an unconditional 8-week refund right for recurring charges.

PCI DSS is the security standard that governs how card data must be handled by every organization in the payment chain. This lesson covers what the standard requires, who must comply, and what happens when they don't. You will learn the 12 requirements grouped across 6 control objectives, including the hard prohibition on CVV2 storage that applies regardless of encryption method or compliance tier.

The lesson also covers the four compliance levels and what each requires, from annual QSA audits at Level 1 down to self-assessment at Level 4. Two real breach cases illustrate the cost of non-compliance: the Target 2013 breach caused by excessive third-party access, and the Ticketmaster 2024 breach caused by a third-party cloud account with no MFA — a direct violation of PCI DSS v4.0 requirements.

That SMS code your bank sends before an online payment completes - that is 3-D Secure. This lesson explains what is actually happening behind that step: how three domains (acquirer, issuer, and interoperability) exchange messages to verify your identity before any money moves, and why 3DS authentication and payment authorization are two completely separate processes that run one after the other.

The lesson covers both 3DS flows in detail. Frictionless flow completes silently in the background when the issuing bank's risk assessment clears the transaction automatically. Challenge flow adds a cardholder verification step - SMS, push notification, or biometric - when the risk score is elevated. You will also learn why a transaction can pass 3DS authentication and still be declined, who bears fraud liability when authentication is skipped, and why merchants almost never operate their own 3DS infrastructure.

GDPR is the EU's data protection regulation, but its reach extends well beyond Europe. Any organization that processes personal data of EU residents must comply - regardless of where it is headquartered. This lesson covers what GDPR is, what counts as personal data, and the seven core principles that govern how data can be collected, used, and stored. You will also learn the important distinction between consent and other legal bases for processing, which is one of the most commonly misunderstood points in GDPR.

The second half of the lesson applies GDPR directly to fintech: KYC documents, payment data, customer rights (including the right of access and right to erasure), and third-party processor accountability. A fintech that outsources data handling to a cloud provider or payment processor remains the data controller and cannot transfer its compliance obligations. Fines reach up to €20 million or 4% of global annual turnover, whichever is higher.

Fraud is a double threat for banks and fintechs: direct financial losses from refunds and chargebacks, and reputational damage when customers lose trust. This lesson covers the four main fraud types - card-not-present fraud, card-present fraud, friendly fraud, and account takeover - with clear explanations of how each works and who bears the financial consequences.

The second half covers the four layers of fraud prevention that work together in modern payment systems: customer authentication (including 3-D Secure and biometrics), real-time fraud detection systems using machine learning, transaction limits and velocity checks, and shared fraud intelligence networks maintained by Visa, Mastercard, and industry groups. Together these layers allow banks to intercept the majority of fraudulent transactions before money leaves the cardholder's account.

Every bank account, card, and fintech service starts the same way: the customer passes through an onboarding pipeline before gaining access. This lesson covers the four stages of that pipeline - Registration, KYC, AML, and Scoring - and explains what happens at each step, why it is legally required, and how the outcome of each stage feeds into the next.

The first half covers KYC (Know Your Customer) and AML (Anti-Money Laundering) screening: how identity documents are verified using OCR and AI, what a liveness check is, how sanctions lists and PEP databases work, and why banks use third-party providers like World-Check and LexisNexis rather than maintaining their own watchlists. The second half covers Scoring: the difference between credit scoring and fraud scoring, what data each model uses, and why two customers who both pass KYC and AML can end up with very different credit limits and interest rates.

Dispute and chargeback are two of the most misused terms in payments - most people treat them as synonyms, but they describe two different things at two different stages of the same process. This lesson defines both precisely, explains how they relate, and introduces the five-stage cycle that every disputed transaction passes through: from the original purchase all the way to a binding arbitration ruling.

The lesson also covers who is actually involved - the cardholder, issuing bank, payment network, acquiring bank, and merchant - and what each party's role is when a transaction is contested. One point that surprises most people: if a cardholder raises a dispute and loses, there are essentially no consequences for them. No penalty, no flag in any network system, no sanctions. All the financial burden - fees, operational costs, and chargeback ratio damage - falls on the merchant and the banks in the processing chain.

This lesson maps the full dispute cycle in detail - every step a contested transaction takes from the cardholder's initial objection through to final resolution. Using a 15-step flow diagram, you will see exactly what each party does and when: how the issuing bank issues a provisional credit the moment a chargeback is initiated, how the chargeback travels through the payment network to the acquiring bank and merchant, and what happens at each of the two decision points where the outcome branches.

The second half covers what happens when a merchant contests a chargeback through representment, why the issuing bank's response to that evidence determines whether the dispute closes or escalates to pre-arbitration and arbitration, and why the cost of arbitration - $500 for Visa, $250-$500 for Mastercard - is the main reason most disputes are resolved long before a payment network ruling is needed.

Every chargeback arrives with a reason code that tells the merchant why the dispute was filed and what evidence they need to fight it. This lesson covers the four reason code categories used by both Visa and Mastercard - fraud, authorization errors, processing errors, and consumer disputes - including the two most common subcategories in everyday commerce: INR (Item Not Received) and SNAD (Significantly Not As Described).

The second half covers what chargebacks actually cost a business and how to keep that cost under control. You will learn how the chargeback ratio is calculated, why the formula creates a structural problem for small merchants and how acquiring banks handle it in practice through an internal risk profile alongside the official number, and four concrete levers for reducing chargeback risk - from fraud monitoring and proactive refunds to clear return policies and evidence management.

Card payments get most of the attention, but a huge share of global transaction value moves through a completely different channel: bank transfers. This lesson maps the full landscape of bank transfers - domestic and international, standard and instant, traditional and alternative - and introduces the systems you will encounter throughout this section: ACH, SEPA, SWIFT, Faster Payments, PIX, Visa Direct, Project Nexus, Wise, and more.

The lesson also clarifies two distinctions that are easy to confuse. The first is credit transfer versus direct debit: one is initiated by the sender, the other by the recipient - the same push/pull logic covered in the card payments section, applied here to bank rails. The second is standard batch processing versus instant payment systems, which settle in seconds and run 24/7 regardless of bank working hours. Each system covered here gets its own dedicated lesson in the section that follows.

SEPA - the Single Euro Payments Area - is the infrastructure that connects 36 European countries and makes euro transfers across borders as simple as a domestic payment. This lesson covers how SEPA works, what IBAN and BIC are, and how the zone standardized bank transfers across an entire continent.

The lesson then goes inside three SEPA instruments - Credit Transfer, Instant Credit Transfer, and Direct Debit - tracing how each one moves through the banking infrastructure from initiation to settlement, and what makes each suited to a different payment need.

SWIFT is the network that carries almost every international bank transfer on the planet - yet most people fundamentally misunderstand what it does. This lesson starts by clearing up the biggest misconception: SWIFT does not move money. It transmits payment instructions. The actual funds travel a completely different route through correspondent bank accounts, CHIPS, and Fedwire.

The lesson then traces a real USD transfer from Japan to Mexico step by step, showing how information flow and money flow separate the moment a payment leaves the sender's bank - and why that separation is the key to understanding international banking. It also covers how SWIFT has evolved beyond slow cross-border wires with gpi and RT RPS, and how SWIFT and SEPA compare as infrastructure.

ACH - the Automated Clearing House - is the network that moves payroll, mortgage payments, utility bills, and government benefits for hundreds of millions of Americans every business day. This lesson covers how ACH works, who the five participants are, and why the network was built the way it was.

The lesson traces a complete payroll payment from the employer's payroll processor all the way to the employee's account, including the cut-off times and overnight processing that define how ACH operates. It also covers Same Day ACH, how FedNow and RTP fit alongside ACH as separate instant rails, and how ACH compares to SEPA as the European equivalent solving the same problem with different technology.

P2P transfers - payments between people - look simple on the surface but run on three very different types of infrastructure. This lesson maps all three: account-to-account transfers via national payment rails, Push to Card via Visa Direct and Mastercard Send, and wallet-to-wallet transfers within closed digital ecosystems like PayPal, Revolut, and WeChat Pay.

The lesson then goes inside the wallet model to explain why a transfer between two PayPal users is instant while withdrawing that money takes days. The answer lies in how wallets actually hold and move money - and understanding it changes how you think about every digital wallet product you will encounter in fintech.

Every payment system covered in this section - SEPA, SWIFT, FedNow, Faster Payments - now speaks the same language. That language is ISO 20022, and this lesson explains what it is, why it was needed, and how it works.

The lesson covers the message family taxonomy (pain, pacs, camt, and others), walks through a real pain.001 XML message field by field, and compares ISO 20022 to ISO 8583 - the card payment standard students encountered in Section 1. It also maps where the global migration stands today and identifies the one major system still outside it.

Buy Now, Pay Later has reshaped how consumers pay at checkout. In this lesson, you will learn how BNPL works under the hood: the three product types (Pay in 4, Pay in 30 days, and long-term installments), the three funding models behind them, and a step-by-step walkthrough of a real BNPL transaction from registration through recurring installment charges. We close with a direct comparison between BNPL and credit cards across approval process, repayment format, cost, and regulation.

QR payments have replaced card terminals across large parts of Asia, Latin America, and Africa - and are growing globally. In this lesson, you will learn how QR payments are classified along two axes: who presents the code and whether it is static or dynamic. You will then look at the three payment models that sit beneath the merchant-presented format - card-based QR, account-to-account QR, and wallet-based QR - and understand how each routes money differently. The lesson closes with a step-by-step walkthrough of a card-based QR transaction, including why the payment flow is initiated from the customer side rather than the merchant side, unlike in a standard card payment.

Digital wallets are not all built the same way. In this lesson, you will learn the three wallet types - pass-through, staged, and stored-value - and understand how each moves money differently. You will see why Apple Pay never touches your card number, how PayPal splits a transaction into two separate operations, and why Alipay can settle payments without involving a card network at all. The lesson closes with a direct comparison between a card payment and a closed-loop wallet payment, showing why fewer intermediaries means lower fees and faster processing.

Visa and Mastercard are everywhere - but they are not how most people pay in China, Brazil, Poland, or Kenya. In this lesson, you will learn what payment methods actually dominate in six regions, and why. For each region we cover the key characteristics, the reason those characteristics exist, and one standout example that illustrates the logic of that market. Asia-Pacific went wallet-first because super-apps arrived before cards did. Latin America has Pix because a central bank built what private companies could not. Africa has M-Pesa because payments were built on phones, not banks. By the end of the lesson, you will understand not just which methods exist - but why they won.

Traditional banks have branches, legacy systems, and fees that are not always easy to understand. Neobanks removed all of that and rebuilt banking from scratch in an app. In this lesson, you will learn what makes neobanks structurally different from traditional banks, how they actually make money through interchange, subscriptions, and a growing stack of financial services, and how the most ambitious neobanks are evolving into super-apps - single platforms that combine banking, investments, travel, and lifestyle services in one ecosystem. We look at the business model in detail, use Revolut as the primary Western example, and examine both the genuine advantages and the real risks of consolidating financial life into one platform.

Cryptocurrency is not one thing - it is an ecosystem of different asset types, each with a different purpose and a different risk profile. In this lesson, you will learn what cryptocurrency actually is and how blockchain technology makes it work, the four main categories (payment cryptocurrencies, tokens, stablecoins, and CBDCs), how the most important individual assets differ from each other, and how crypto is stored - covering the hot/cold and custodial/non-custodial distinctions that determine who actually controls your funds. The lesson also covers how fiat-backed stablecoins work step by step, and closes with an honest assessment of the real benefits and documented risks - including the $1.5 billion Bybit hack of February 2025, the largest crypto theft in history.

Governments are building a new form of money - not crypto, not stablecoins, but a direct digital equivalent of national currency issued by central banks. This lesson covers what CBDCs are, why governments want them, how the two-tier architecture works, and where the world stands today. You will look at China's e-CNY - the largest CBDC pilot on the planet - and the digital euro still in development, and close with a direct comparison of CBDCs and stablecoins.

Every financial transaction you have made has involved at least one intermediary. Web3 and DeFi ask what happens when you replace those intermediaries with code. This lesson covers how the web evolved from read-only pages to user-owned assets, how DeFi differs from traditional finance across access, governance, transactions, and risk, and what the five core DeFi service categories actually do - from DEXs and lending protocols to DAOs and yield farming. It closes with an honest assessment of both the opportunities and the risks.

Banks used to own your financial data completely - nobody else could see it, use it, or build on it. Open Banking changed that by giving customers the right to share their data and authorize payments through standardized APIs. This lesson covers how Open Banking works, how it compares to card payments, and what Embedded Finance means in practice - from BNPL at checkout to instant courier payouts to business loans inside a marketplace. It closes with an honest look at the opportunities and the risks, including data security, regulatory gaps, and the monopoly dynamics that could undermine the competition Open Banking was designed to create.

AI in fintech is not robots making decisions - it is a set of tools that find patterns in data faster and more consistently than human teams can. This lesson covers how AI actually works in financial services: what data it learns from, which techniques it uses, and where it is deployed today. You will look at six core applications - credit scoring, fraud detection, KYC and AML, investments and trading, customer service, and document processing - with an honest assessment of both what AI does well and where the limitations and regulatory risks are.