.png?width=365&height=122&name=BTLogo%20(1).png)
Why I Joined Basis Theory as Principal Technical Account Manager
Table of Contents
A 15-year career in payments creates opportunities to see payments from many different angles. I kept running into the same problem across CardinalCommerce, Visa, Spreedly, and, most recently, DEUNA. Merchants want to optimize everything. Authorization rates, routing, fraud, network tokens, account updater, AI. But many don’t actually control the data layer that these optimizations depend on.
That gap is where I have spent a lot of my career. And it’s ultimately why I joined Basis Theory.
The clearest version of this problem showed up for me around orchestration. Orchestration solves a real connectivity problem, but it often spans too many layers at once. Merchants end up inheriting latency, data gaps, and failure modes across the stack. Then, when performance drops, it’s hard to isolate whether the issue is the processor, the token, the BIN data, retry logic, or the orchestration layer itself.
That was the unlock for me: orchestration solves access, but it doesn't automatically create control.
What Control Looks Like
I’ve seen the same patterns emerge at each of my career stops: enterprise merchants don’t want generic payment strategies. These merchants are looking for infrastructure, expertise, and partners that understand how complex their environments really are.
One example that has stuck with me was an enterprise merchant with more than 14 global brands on a shared commerce platform. When we focused on one of their largest brands, we found that Network Tokenization, Account Updater, and 3DS were each being managed through different Payment Service Providers (PSPs).
On paper, they had the right optimization tools. In practice, the data was fragmented. The opportunity was to centralize the data layer so those services could be measured, governed, and optimized together. That work identified nearly $2 million in annual savings, creating the foundation for an omnichannel vault strategy.
And the bigger unlock was the customer experience. Once payment credentials could move across the brand portfolio, the merchant could create a more seamless omnichannel experience that improved the customer lifetime value beyond an individual brand relationship.
Fragmented Payment Stacks
As automated and agentic commerce move from concept to reality, questions around identity, authorization performance, and who controls the customer relationship aren't getting simpler.
Enterprise payment environments are more complex than most vendors acknowledge. API structures, checkout channel requirements, PSP relationships, acquiring strategies, and reporting needs vary across brands, regions, and business units. Those details aren't just technical preferences, they're tied to how the business serves customers and how the payments team is measured.
Fragmented infrastructure makes all of it harder. When credentials are scattered across disconnected vaults and systems, optimization becomes guesswork. You're working through someone else's abstraction, and the gaps show up in authorization rates, renewal performance, false declines, and rising costs.
At a certain point, I didn't want to keep helping companies work around fragmented infrastructure. I wanted to help fix the foundation.
That's why Basis Theory stands out. By sitting underneath orchestration and AI, merchants get programmable, independent control over the sensitive payment data layer, and the workflows around it. Without control of that foundation, merchants are still working from someone else’s roadmap.
Putting the Puzzle Together
My approach has always been simple: earn trust and understand the merchant’s reality. Complexity turns into progress when you understand what the end customer is experiencing, what the payments team is trying to improve, and what business outcomes matter most. Sometimes it means reducing costs, improving renewals, supporting global expansion, creating cleaner reporting, or giving engineering more flexibility.
The answer is rarely one thing. But it should start with the vault.
Basis Theory gives merchants the control to design the payments stack they need without introducing unnecessary lock-in. It hasn’t even been a month, yet I’m already seeing how our infrastructure helps companies protect what makes their business unique—and maintain the flexibility required for what comes next.
The best enterprise payment teams aren’t looking for someone to force a generic strategy into their stack. I try to be a trusted partner who can listen, understand the complexity, respect the work already done, and stay accountable to the outcomes that matter. I’m bringing that enterprise payments perspective to Basis Theory.
Let’s have a real dialogue about what control of your payment data layer could unlock for your business.
