Product leadership

Payments work, where the merchant's ledger is the real spec.

I've spent my career on the part of payments that sits between what a merchant needs and what it takes to deliver at scale: enterprise checkout, in-store debit, and the platforms that connect merchants to processors and card networks.

PayPal / Braintree · In-store payments

Enterprise in-store PIN debit

Extending enterprise checkout from the browser into the physical terminal, where debit routing choices decide whether a merchant's costs and approval rates hold up at scale.

Full case study in progress

PayPal / Braintree · Online checkout

PayPal and Venmo checkout for enterprise merchants

Helping large merchants put PayPal and Venmo in front of their customers, then making the integration, rollout, and support model hold once real transaction volumes arrived.

Full case study in progress

United Airlines · Travel payments

Customer payments at United Airlines

Leading customer payments for an airline, where acceptance, refunds, and disruption handling all have to work at the same moment, in front of a customer who is already having a hard day.

Full case study in progress

Full case studies go up as each one is reviewed and cleared. If you'd like to talk through any of this work directly, get in touch.

How I work

Four habits that decide whether a payments product holds up.

01

Understanding the merchant problem

The starting point isn't a feature list, it's the merchant's ledger: what they're charged, what they're approved for, and what their operations team chases every week. I stay with that until the real constraint is clear, whether it's cost, approval rates, or a reconciliation nobody wants to own.

02

Working through technical and commercial tradeoffs

Payments decisions rarely land free. Routing that lowers cost can move approval rates. Adding an acceptance method can complicate settlement. I make those tradeoffs explicit, with numbers, so the business picks a direction it can defend later.

03

Bringing internal teams and partners together

Checkout and debit work spans product, engineering, compliance, risk, finance, and processors or networks outside the building. A lot of the job is keeping one plan and one definition of done across all of them.

04

Planning for adoption and operations after launch

Launch is the midpoint. Someone has to onboard merchants, watch declines, answer disputes, and keep the playbook current. I plan for that work before the first merchant goes live rather than after the first escalation.

Hiring for a payments product role?

I'm always glad to talk about the work, the tradeoffs, and where I can be most useful.

Start a conversation