The Fintech Grimoire

Production patterns for systems that move real money

The Handbook teaches you the fundamentals. This takes you deeper.

Every pattern here comes from a system that moved real money — and from the production constraint that shaped how it was built. The Handbook explains what a ledger is. The Grimoire explains what happens when that ledger processes 10,000 entries per second and your hot account contention drops your p99 latency from 50ms to 8 seconds. The Handbook explains what a matching engine does. The Grimoire explains why it’s single-threaded on purpose.

Who this is for

Senior and staff engineers working in financial infrastructure — and engineers in one domain who want to understand the depth of another. You might be a payments engineer who has never touched a matching engine, or a trading systems engineer who wants to understand how stablecoin settlement actually works. Each part is a deep dive into a domain you can explore on your own terms.

How it’s organized

Each part covers a domain of production fintech engineering. Within each part, chapters are standalone patterns — you can read them in any order. Cross-references link related patterns across parts.

Ledger Engineering — Balance derivation at scale, hot account contention, sub-ledger boundaries, reconciliation engineering, immutability guarantees, DynamoDB vs Postgres tradeoffs.

Smart Contract Engineering — Mint/burn infrastructure, contract security, monitoring, multi-chain deployment, hot wallet architecture, cross-chain messaging, bytecode optimization, circuit breakers. Not DeFi — payment contracts where bugs create or destroy real money.

Settlement Architecture — Dual-ledger reconciliation (fiat + on-chain), real-time settlement paths, atomic settlement, cross-border mechanics beyond correspondent banking.

Payment Rails at Depth — ACH processing internals, real-time payment systems (RTP, Pix, UPI, SEPA Instant), FedNow architecture, SWIFT ISO 20022, card network settlement, payment orchestration and routing.

Stablecoin Infrastructure — The issuance stack from reserve management to distribution. Regulatory frameworks (OCC charter, EMI licence). White-label issuance as a platform. Tokenized deposit operations.

FX Operations — Hedging and exposure management, nostro/vostro account funding, multi-currency position management. The operational engineering of moving money across currencies.

Trading Infrastructure — Order book mechanics, matching engine architecture, market data infrastructure, execution algorithms, position management and P&L, latency-sensitive systems. From microsecond matching to nanosecond measurement.

Insurance Engineering — Claims processing pipelines, underwriting automation, actuarial model deployment, policy administration systems. A different domain with its own engineering culture.

Compliance Engineering — AML pipelines at scale, sanctions screening under latency constraints, KYC orchestration, SAR automation, regulatory reporting infrastructure, cross-chain compliance architecture.

Risk Systems — Credit decisioning at 250ms, fraud model deployment and rollback, feature stores in production, model monitoring and drift detection, model risk management (SR 11-7).

Financial Cryptography — HSMs, MPC, threshold signatures, key rotation policies, tamper evidence without blockchain.

Data Infrastructure for Finance — Point-in-time correctness, financial data lineage, bitemporal data patterns. The discipline of building data systems where every query answer has regulatory weight.

Platform Architecture — Multi-tenant ledger isolation, API design when money moves, idempotency at scale, state machines for money, webhook reliability, core banking integration, architecture-as-code, event mesh design, saga orchestration, agent payment authorization.

Multi-Chain Operations — Chain agent architecture, nonce management and transaction recovery, on-chain financial calculations. Running production backend services across multiple blockchains.

Agentic Finance — Agent identity and delegation, agent transaction monitoring, safety-constrained architectures. The engineering of systems where AI agents initiate financial transactions.

Financial Incident Response — When money has moved and you can’t roll back, regulatory notification windows, ledger drift runbooks. Incident response when the stakes have dollar signs.

Relationship to the Handbook

Handbook → What you need to get started in fintech
Grimoire → What you need to operate at staff level

For deep fintech analysis, engineering deep dives, and industry coverage, see LedgerDrift.

Prerequisite: The Fintech Engineering Handbook covers the foundational concepts this book builds on. If a term here is unfamiliar, start there.