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.
Full reversals are well-covered in most integrations. Partial reversals are where the design assumptions leak.
TLS 1.3 became mandatory in most compliance frameworks by 2025. Deploying it across a device fleet has some rougher edges than the browser story suggested.
Documentation gets treated as an aftermath. Treating it as a deliverable — with the same discipline as code — changes what the team ships.
NPCI's cross-border UPI push is on. What the receiving markets are learning about live-integrated retail payments from India.
Compliance documents change slowly, are consulted often, and require precise citation. A well-shaped RAG use case with specific engineering demands.
Merchant payouts in stablecoins raise a custody question that fiat payouts don't. What operational patterns look like.
Pinning is a defense against a specific attack. On an Android POS fleet, the wrong pinning strategy is the operational problem that never leaves.
One database can serve both operational and reporting queries — until it can't. Where the split should go and how to build it.
Signature-based card verification in the US is quietly winding down. The remaining edge cases are worth planning around.
Most one-on-ones are status updates. The ones that build the relationship and surface problems have a different shape.