Writing
Notes from systems meeting real devices.
Notes on payment systems, device software, transaction uncertainty, platform design, and the emerging role of AI in commerce. I write from the questions that appear in real operating conditions.
The compliance-security gap
Passing an audit is not the same as being secure. Where the gap is widest, and how to close it.
Scaling settlement batching
Settlement batching sounds like accounting. It's actually a distributed systems problem with financial-grade correctness requirements.
Growing a distributed team across three time zones
A team distributed across three time zones has specific coordination costs. What scales, and what stops scaling.
Tokenized deposits vs. stablecoins
Tokenized bank deposits and stablecoins look similar from the outside. The regulatory, credit, and operational profiles diverge sharply.
Card-not-present fraud patterns, 2024
What the year's CNP fraud looked like — signal patterns, response effectiveness, and where the loss actually landed.
Why AI won't replace fraud analysts (yet)
Fraud detection is one of the areas where AI hype is loudest. What actually improves fraud analyst productivity, and what the models still can't do.
Key exchange in offline-capable terminals
Terminals that operate offline for periods need a key-exchange design that doesn't assume connectivity at all the right moments.
Technical decisions that need a stakeholder
Some technical decisions should be made by engineers alone. Others need explicit stakeholder input, and getting the line wrong causes friction later.
Why blockchain payments still need rails
"Blockchain payments" as a category is often marketed as if it replaces rails. In practice, blockchain settlement sits inside a broader payment rail architecture.
Cross-region failover for payment platforms
Cross-region failover for a payment platform has different constraints from a general web application. What the design has to preserve.