https://charliehowes.com/tags/payments/Recent content in Payments on Charlie Howes | Contract Software EngineerHugo -- gohugo.ioen-us© Charlie HowesSat, 21 Mar 2026 11:00:00 +0000https://charliehowes.com/posts/first-post/Sat, 21 Mar 2026 11:00:00 +0000https://charliehowes.com/posts/first-post/<p>I have wanted to start writing consistently for a while, so this is the first post in what I plan to keep as a practical engineering log.</p> <p>The goal is simple: share useful patterns from real projects, especially where delivery speed, reliability, and compliance need to coexist.</p> <p>Most of my recent work sits at the intersection of:</p> <ul> <li>Go backend services and platform foundations</li> <li>Payments integrations and regulated system design</li> <li>Safe migration work across data stores, queues, and service boundaries</li> <li>Reliability improvements that teams can sustain after handover</li> </ul> <p>I am not aiming for generic tutorials. I want these posts to be concise and production-oriented: what worked, what failed, and the trade-offs that mattered.</p><p>I have wanted to start writing consistently for a while, so this is the first post in what I plan to keep as a practical engineering log.</p> <p>The goal is simple: share useful patterns from real projects, especially where delivery speed, reliability, and compliance need to coexist.</p> <p>Most of my recent work sits at the intersection of:</p> <ul> <li>Go backend services and platform foundations</li> <li>Payments integrations and regulated system design</li> <li>Safe migration work across data stores, queues, and service boundaries</li> <li>Reliability improvements that teams can sustain after handover</li> </ul> <p>I am not aiming for generic tutorials. I want these posts to be concise and production-oriented: what worked, what failed, and the trade-offs that mattered.</p> <h2 id="what-to-expect-next">What to expect next</h2> <p>Over the next few posts, I will cover:</p> <ol> <li>A migration playbook for reducing blast radius when changing core flows</li> <li>Practical observability baselines for high-throughput Go services</li> <li>Patterns for integrating external payment providers without locking the domain model to one vendor</li> </ol> <p>If you are working on similar problems, feel free to reach out and compare notes.</p>