Payments
A payment gateway from scratch that became its own business
The gateway outgrew the company that built it and became a business of its own.
See the project ↗Services / Payments
Payment flows, gateway integrations, and boundaries designed with the care that moving money deserves.
Does this sound familiar?
From the problem to the handover
Money moves through your software, and every change carries risk: to customers, to compliance and to the business itself. The safest-looking option is to change nothing, which is how payment code goes stale.
Map where card data travels today and which systems truly need to see it.
Keep card data out of everything else with tokenization, so compliance scope stays small by design.
Wire fraud signals and monitoring into the transaction path.
Ship each change behind tests and review that treat every payment path as critical.
Experience you can inspect
Earlier work that informs how I approach this service. Each engagement has its own scope.
Before we start
Bring the current or planned payment flow and provider. We’ll trace where data travels, what needs to change, and which paths need protection.
More about working together ↗Yes. I built a PCI-compliant payment gateway from scratch as employee number seven at Ministry Brands. By my account, with no public source, it grew to process $15B+ a year across 90+ brands, and it was spun out as its own company.
Card numbers are swapped for tokens as early as possible, so only the systems that truly need card data ever hold it. On that gateway, tokenization per brand kept each acquired brand out of its parent's compliance scope.
Yes. By my own account from an earlier role, with no proof page, real-time fraud analytics put the risk on monitored attack vectors 96.7% below average and cut fraud damages by 60%.