Loading…
Writing
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.
Passing an audit is not the same as being secure. Where the gap is widest, and how to close it.
Settlement batching sounds like accounting. It's actually a distributed systems problem with financial-grade correctness requirements.
A team distributed across three time zones has specific coordination costs. What scales, and what stops scaling.
Tokenized bank deposits and stablecoins look similar from the outside. The regulatory, credit, and operational profiles diverge sharply.
What the year's CNP fraud looked like — signal patterns, response effectiveness, and where the loss actually landed.
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.
Terminals that operate offline for periods need a key-exchange design that doesn't assume connectivity at all the right moments.
Some technical decisions should be made by engineers alone. Others need explicit stakeholder input, and getting the line wrong causes friction later.
"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 a payment platform has different constraints from a general web application. What the design has to preserve.