Have a tricky problem that you think requires a rewrite of your software? Join as a guest on our podcast and we’ll talk you out of it.

What the engagement looks like

Week 1: Follow the money

We trace every path a payment, refund, or payout takes through your services and mark the spots where a bug would move money, block it, or leave it unreconciled.

Weeks 2–4: Safeguards before migration

Off switches go in first, along with safety checks that block a transaction when the data they depend on is missing. Then the migration or remediation runs in stages: shadow traffic, then a small group, then everyone, and we reconcile at each step.

Hand-off

You get a runbook for the cutover and for rolling back, reconciliation reports your finance team can read, and evidence for your PCI assessor on the controls we put in place.

What you get

  • A map of how money flows across your services, banks, and processors
  • Off switches on refunds and payouts, plus safety checks that block the transaction when the data they depend on is missing
  • A staged sponsor bank or processor migration with reconciliation at every step
  • A script inventory and change detection on your payment pages for PCI DSS 6.4.3 and 11.6.1
  • Runbooks, plus evidence that’s ready for your assessor

Proof

This service comes from the experience of Isaac Askew, who runs YGG, rather than from a YGG client engagement. He spent five years as a principal software engineer on a payments platform that handles 50,000+ bill submissions a month.

  • Sponsor bank migration: He moved card issuing and ACH to a new sponsor bank across five services without a rewrite. Off switches went on every path that moves money, both banks’ programs ran side by side for a while instead of one cutover night, and at the end he deleted about 5,900 lines of the old bank’s code. Read the write-up.
  • PCI DSS 6.4.3 and 11.6.1: He put controls on the payment pages using a nonce-based Content Security Policy, Subresource Integrity, violation reporting, and a script inventory.
  • Refund safety: He replaced three refund jobs with one tested library of layered checks. After a real incident, those checks now block the refund whenever the data they depend on is missing. Read the write-up.

The patterns behind that work are written up in our pattern library.

Talk it through

A 15-minute call is enough to tell whether this is a good fit. Bring the system you’re worried about.

Book a call How we work & pricing

Prefer email? start@ygg.llc