Sebastien Rousseau

Applied AI in financial services — model deployment, governance, AI agents, LLM tooling, and the AI infrastructure that runs in banking environments.

Autonomous AI agents in payments, treasury, and back-office banking — consent, liability, audit trails, and protocol interoperability.

Model risk, EU AI Act conformity, NIST AI RMF, board-level accountability, third-party AI vendors, and the compliance stack for AI in banks.

Large language models in financial workflows — fine-tuning, RAG, prompt engineering, on-device LLMs, and inference cost economics.

Generative models for banking — code, content, search, simulation — and the engineering required to ship them safely.

Wholesale and retail payments migration to ISO 20022 — pacs.008, pain.001, camt messaging, CBPR+, and the data-rich rail.

FX, correspondent banking, multi-rail routing, G20 roadmap targets, and the cost-plus-speed dimensions of moving money across borders.

Bank-issued deposit tokens, atomic settlement, programmable balance-sheet, and the policy framing around tokenised commercial bank money.

Issuance, reserves, redemption, regulation, and the role of stablecoins as a settlement asset alongside bank deposits.

Messaging, GPI, payment pre-validation, and SWIFT's evolving role in the multi-rail world.

Broad coverage of payment systems, rails, and the economics of moving money — sits above the rail-specific canonicals as the catch-all editorial entry point.

Cross-Border Payments and Reporting Plus — the SWIFT ISO 20022 usage guidelines for correspondent banking.

PSD2, PSD3, CMA9, FDX — open banking APIs, payment initiation, and the data-portability fabric.

Real-time treasury, intraday liquidity orchestration, programmable balance-sheet, and the agentic-treasury stack.

Interbank, large-value, market infrastructure payments — the wholesale side of banking infrastructure economics.

Customer payment initiation message — corporate payment factories, validation, and the migration off MT101.

Corporate and bank treasury operations — liquidity management, cash forecasting, FX hedging, and the operating model that sits behind real-time treasury. The agentic / autonomous- treasury angle lives under the more specific ``programmable-liquidity`` canonical.

DeFi protocols, smart-contract risk, on-chain liquidity, and where banks integrate (or intentionally don't) with the DeFi stack.

The customer credit transfer message at the heart of cross-border ISO 20022 — schema, validation, automation, and orchestration.

Account-to-account rails, open banking payment initiation, and the agentic-payments use cases that ride them.

Tokenised assets, custody, settlement infrastructure, and the institutional adoption of digital-asset rails alongside traditional finance.

Payment file creation, validation, exception handling, and the engineering side of payment ops.

RTP, FedNow, SEPA Instant, UK Faster Payments — instant rail mechanics, liquidity, fraud, and pricing.

Wholesale and retail central bank digital currencies — design choices, project status, and the policy debate.

Routing each payment by cost, finality, and liquidity — the multi-rail orchestration stack.

Real-time gross settlement systems — RTGS Renewal (UK), TARGET2/T2, Fedwire, and the operational windows banks integrate against.

AI agents initiating payments — consent, liability, fraud controls, audit, and the new payment UX.

NIST PQ standards, harvest-now-decrypt-later threat, hybrid handshakes, and the migration of banking cryptography to lattice-based primitives.

Hardware progress, quantum algorithms, the timeline-to-threat, and where quantum compute crosses paths with banking workloads.

Kubernetes, service mesh, multi-region resilience, and the cloud-native architecture patterns banks are adopting under DORA.

Internal developer platforms, golden paths, paved roads — how banking technology orgs ship engineering productivity.

Important business services, impact tolerances, severe-but- plausible scenarios, and the operational-resilience programme banks must run.

Applied cryptography in banking — hashes, signatures, KEMs, key management, and the cryptographic primitives that secure the rails.

Data-residency, regulatory-region cloud, and the architectural trade-offs of running banking workloads inside sovereign boundaries.

Distributed ledger technology in financial infrastructure — consensus, validators, smart-contract execution, and where the primitive shows up in banking.

Inventorying cryptographic assets, defining a migration path, and shipping replaceable crypto boundaries in production code.

Operational security in banking — threats, controls, incident response, and the regulatory expectations around resilience.

FIPS 203 — the standardised post-quantum key encapsulation mechanism (formerly CRYSTALS-Kyber).

The HNDL threat model — adversaries capturing encrypted traffic today to decrypt once quantum hardware is available.

FIPS 204 — the standardised post-quantum digital signature algorithm (formerly CRYSTALS-Dilithium).

Edge workers, anti-fraud at the edge, CDN-as-platform — the role of edge compute in financial workloads.

Digital Operational Resilience Act — register of information, ICT third-party risk, threat-led penetration testing, and the operational resilience programme banks must run.

Implementation guidance, supervisory expectations, high-risk system classification, and the conformity-assessment burden the Act puts on banks.

ICT third-party risk under DORA, EBA outsourcing guidelines, and the supervisory expectation around critical-vendor concentration.

NIST standards relevant to banking — FIPS 203/204, AI RMF, SP 800/1800 series — and the supervisory adoption patterns around them.

Open-source software in regulated banking — supply-chain risk, attestations, contribution policy, and the OSS projects banks rely on.

Rust in banking infrastructure — memory safety, performance, and the ecosystem of crates relevant to financial workloads.

Model Context Protocol — how AI clients discover and consume banking content as structured resources.

Static-site-generation patterns for editorial publishing — performance, security, and the build pipeline.

The banking industry as the editorial subject — what's changing, why, and what it means for technology, payments, risk, and the operating model.

Bank CTO / CIO concerns — make-vs-buy, build-vs-partner, organisational design, and the strategic technology agenda.

Editorial coverage of strategic technology shifts in banking — what's coming, who's shipping it, and what it changes.

Original analysis, indices, and benchmarks — the data work that backs the editorial position.