The credentialing playbook in finance is straightforward. CPA. CMA. MBA. Maybe a Six Sigma belt or a Big 4 stint on the resume. Stack enough letters and the next role becomes more or less inevitable. It's the path most ambitious people are running, and on its face the logic is sound.
Look at who actually ended up in the most interesting senior controller seats in payments over the last decade — the people whose careers compounded into something worth having — and the pattern is different. They didn't have more credentials than their peers. They had something else. Something that's invisible from outside the function and overwhelmingly decisive once you're inside it.
The thing they had was domain depth. They actually understood how the business works at a level most of their peers did not. And that depth, more than any certification, is what compounded into outsized career outcomes.
This is unfashionable to say in a market that treats credentials as a proxy for capability. But the evidence in payments finance is overwhelming, and the implications for someone trying to build a career in this space are worth taking seriously.
What domain depth actually means in payments.
It's easy to wave at "domain depth" as a vague virtue. The specific version, in payments and acquiring, is concrete. It means understanding things like:
- How the four-corner model actually works — issuer, acquirer, cardholder, merchant — and which entity bears which risk and earns which fees in which scenario. Not the cartoon version. The real version, including how dispute liability shifts based on the EMV liability rules and the chargeback reason code.
- Why interchange is structured the way it is — that it isn't really a "fee," it's a transfer payment from the acquirer side to the issuer side, set by the networks, calibrated to keep the issuing economics viable. Knowing this changes how you think about acquirer margin compression.
- What scheme assessments are, what's in them, and how they shift — including the cross-border, currency conversion, and brand-specific assessments that don't look like much line by line but compound into real basis points of margin.
- How chargeback economics work in detail — the timing, the merit-based reason codes vs. the fraud reason codes, the pre-arbitration step, the impact of representment win rates on reserve adequacy, and how all of this interacts with the merchant onboarding underwriting decision.
- Why principal vs. agent classification under ASC 606 is genuinely hard in a payments context — and why the answer can flip based on contract terms that look minor.
- What scheme billing actually looks like — the lag, the true-ups, the credits that come months later, the specific accrual challenges that arise because the network's bill arrives weeks after the period it covers.
None of these are mysterious. They're all in some textbook or some scheme rules document. But none of them are picked up by getting a CPA, and most of them are not understood deeply by people whose payments knowledge stops at "we run cards through Stripe."
Why AI makes this more valuable, not less.
The most thoughtful objection to all of this is also the most current one. If AI can answer questions about interchange or chargebacks, why invest five years in learning them yourself? Domain depth might be a fading asset, the argument goes — a moat about to dry up.
The argument is wrong in a specific way that's worth understanding.
AI gets these questions right when the answer is documented somewhere it can find. AI gets them wrong — sometimes subtly, sometimes catastrophically — when the answer requires judgment that draws on context the model doesn't have. A new contract structure that breaks the standard interchange logic. A scheme rule update that changed the chargeback economics in a non-obvious way. An old reserve methodology that has to be defended to a new audit team.
As AI becomes more pervasive in finance, the value of being the person who can tell when the model is confidently wrong goes up, not down. The shallow practitioner with AI tooling produces output that is hard to defend, because they can't tell when the model is right. The deep practitioner with AI tooling is materially more productive than they were before, and their judgment is more valuable, not less.
The framing that's sometimes assumed — that AI levels the playing field by giving everyone access to the same knowledge — is wrong in this same specific way. AI gives everyone access to the same retrieval. It does not give everyone access to the same judgment. Judgment still has to be built the old way: by doing the work, watching what happens, and accumulating the context that doesn't live in the documentation.
Why domain depth compounds.
The interesting thing about domain depth is that the returns are non-linear. The first year of payments depth doesn't differentiate you much. The third year starts to. By the fifth or sixth year, the gap between someone with domain depth and someone without becomes very visible — particularly in moments where a complex question lands and someone has to actually figure out the answer.
The compounding mechanism is straightforward. Each new question in payments finance is a variation on questions you've encountered before. A new chargeback rule, a new pricing structure, a new regulatory requirement, a new product launch — none of them are entirely novel. They all hook into existing structures you understand. Someone with domain depth absorbs the new question quickly because they have somewhere to put it. Someone without domain depth treats every new question as a fresh research exercise.
Over time, this creates a meaningful productivity gap. The deep practitioner can answer in minutes what the shallow practitioner takes hours to research. The senior people in the function notice. The interesting work gets routed to the deep practitioner. The interesting work creates more depth. The cycle continues.
This is why people who stay in payments for ten years often end up running the function. Not because they were ten years more credentialed, but because they had ten years of a compounding advantage in actually understanding the business.
What I'd tell someone earlier in this.
None of what builds domain depth is exotic. None of it requires a special role or unusual access. It mostly comes down to deciding that depth is the thing you're optimizing for, and behaving accordingly for several years. The specific moves that compound:
- Read the scheme rules. Visa's Core Rules. Mastercard's Transaction Processing Rules. They are public, dense, and almost no one reads them. The people who do can answer questions others in the function cannot.
- Read the contracts. Merchant agreements, sponsor bank agreements, processor contracts. The economics of the business live in the contracts. People who understand them have an asymmetric advantage in every finance discussion they're in.
- Trace a transaction end to end. Pick one. Follow it through authorization, clearing, settlement, fee posting, and the chargeback eligibility window. Then do it again with a different card type, a different MCC, a different settlement currency. The first time is hard. The fifth time, things start to click.
- Build the math from first principles. Take a sample portfolio. Build the interchange waterfall. Build the assessment buildup. Build gross-to-net. Don't take any number for granted. The exercise reveals which parts you actually understand and which you've been taking on faith.
The thing all of these have in common: they're invisible to anyone outside the function, they don't show up on a resume, and they will quietly differentiate you over years in ways that nothing on a resume can.
The credential trap.
The trap with credentials is that they feel like progress. Studying for an exam is legible. Adding letters after your name is legible. The progress is visible and validating.
Building domain depth is not legible in the same way. There's no certificate at the end. The progress is invisible to anyone outside the function. For long stretches it can feel like you're not advancing because you can't point to anything new on your resume.
The reality is the opposite. Credentials are table stakes; almost everyone has them. Domain depth is the differentiator that almost no one has. Over a long enough arc, the career returns are dominated by depth, not by the credential stack.
This is hard to see in your first few years. It is impossible to miss by year ten. Whichever direction you're at in that arc, the implication is the same: spend the marginal hour on the work that builds depth, not the work that builds credentials. The math compounds, and at some point, it pays off all at once.
Deeper coverage of the acquiring controller function — from transaction lifecycle through revenue recognition, scheme economics, reserves, and FX exposure — lives at paymentscontroller.com.