Three independent studies in payments, money movement and technical leadership. Each pairs an architecture proposal with a small executable model. These are not employer projects or deployed backend services.
Separating payment intent from provider attempts, so retries and late confirmations don't create a second charge.
What happens when the provider accepts a payment, but the response never arrives?
Architecture · API sketch · Tested model
Holds, settlement and reversals modelled as balanced journal entries, not destructive balance updates.
Can every balance change be explained, even after a reversal?
Architecture · API sketch · Tested model
Versioned decisions with explicit ownership, review boundaries and a record of the trade-offs a team accepted.
Six months later, can the team still explain why a decision was made?
Architecture · API sketch · Tested model
Start a conversation
I'm interested in senior backend and Tech Lead roles across fintech, payments, SaaS and platform engineering in Canada.