Guest: Robert Capps
Today I’m talking with Robert Capps, and this is one of those conversations I especially love because it gets into trust and safety history in a way that still feels incredibly relevant now. Robert is one of those people who helped shape this space before a lot of the current playbooks, tools, and job titles were even fully formed.
Like a lot of us, he did not exactly map out a fraud career from the start. He got pulled into it because the business needed someone to solve a growing problem. In his case, that was StubHub in the earlier days of marketplaces, when online fraud and chargebacks were not nicely packaged into mature vendor categories and polished frameworks. Teams had to figure things out in real time. And a lot of what they built became the foundation for what many fraud teams now consider standard best practice.
That matters.
Because when I talk to fraud teams today, I still see the same core pressures. New business models. Fast growth. Limited context. Criminals moving faster than internal processes. The details change, but the underlying trust and safety challenges are pretty familiar. That is why Robert’s perspective holds up so well.
Here is what that means in practice:
- Trust and safety is often built through real operational pressure, not theory
- Early fraud prevention strategy still has a lot to teach modern teams
- Fraud team evolution usually happens when people are willing to solve problems before a formal playbook exists
- Marketplace risk management gets stronger when teams learn across functions, partners, and investigations
What you’ll hear in this episode:
- How Robert ended up leading trust and safety work at StubHub during a critical growth period
- Which fraud prevention best practices came out of those early marketplace lessons
- Why collaboration inside the company and outside of it mattered so much
- How law enforcement fraud partnerships helped create real consequences for bad actors
- What Robert learned as a merchant-side fraud leader that shaped later work in fraud technology leadership
You should listen to this episode if you:
- Work in fraud, trust and safety, or risk and want a better understanding of how this field evolved
- Lead a marketplace, ecommerce, or fintech fraud team and need stronger operational perspective
- Care about fraud collaboration strategies and law enforcement fraud partnerships
- Want merchant fraud lessons from someone who helped build an early best-in-class team
- Like hearing how online fraud innovation actually develops inside real businesses
If you liked this episode, be sure to subscribe and review the podcast on iTunes, Spotify, YouTube, or wherever you listen to podcasts. It really helps with getting the word out.
Episode notes & key takeaways
This episode is really about what it looks like when trust and safety gets built in a fast-moving business before the industry has all the answers. I’m talking with Robert about the kinds of lessons that only come from being early, being scrappy, and having to solve real fraud problems without much of a roadmap.
How trust and safety got built in the early marketplace era
Let’s break this down.
One of the reasons this conversation is so useful is that Robert was doing trust and safety work at a time when marketplaces were still figuring out what they were. The customer expectations were still being shaped. The fraud attacks were evolving quickly. And there were not nearly as many technology solutions or peer networks to rely on.
That usually forces a team to get practical very quickly.
And that is exactly why the StubHub trust and safety story matters. It was not built in a mature environment with endless vendor options and well-established processes. It was built by responding to what the business needed in the moment and figuring out how to protect growth without letting fraud define the company.
That is the part I think a lot of modern teams can still learn from.
- Trust and safety history matters because many current best practices came from teams solving early marketplace problems
- StubHub trust and safety developed under pressure, which made the lessons especially practical
- Early fraud prevention strategy often comes from experimentation, iteration, and fast learning
- Marketplace fraud leadership matters most when the business model is still maturing
Why fraud prevention best practices usually start as improvised solutions
Here’s what’s actually happening.
A lot of the fraud prevention best practices teams rely on now did not begin as “best practices.” They began as someone trying to stop a specific kind of abuse in a specific moment with the tools they had available. That is one of the most important themes in this conversation.
Robert helped create solutions that later became standard. And that is a really important reminder for fraud teams now. Today’s workaround, workflow, or operational habit can become tomorrow’s normal if it solves the problem well enough and other teams start learning from it.
Right.
That is also why fraud team evolution matters so much. Great teams do not just apply known playbooks. They create better ones when the old ones stop working.
- Fraud prevention best practices often begin as practical responses to real loss patterns
- Online fraud innovation usually comes from operators under pressure, not polished theory
- Fraud team evolution depends on learning fast and documenting what actually works
- Merchant fraud lessons are often the foundation for better industry-wide practices later
Why collaboration changed the outcome
This is where things get especially interesting.
Robert talks about the power of collaboration, and I do not think that can be overstated. Fraud teams that try to solve everything alone usually hit a ceiling pretty quickly. Internal collaboration matters because fraud touches product, operations, customer support, finance, legal, and leadership. External collaboration matters because criminals do not limit themselves to one merchant or one marketplace.
And then there is law enforcement.
That is a whole different layer, but an important one. When teams can connect patterns well enough and build a real case, law enforcement fraud partnerships can shift the entire conversation from loss prevention to actual deterrence. That usually changes how a team thinks about its role.
- Fraud collaboration strategies help teams move from reactive decisioning to stronger long-term defense
- Law enforcement fraud partnerships are more effective when the company has strong internal alignment first
- Fraud operations leadership depends on building influence across departments, not just within the fraud team
- Marketplace risk management gets stronger when intelligence and action are shared more effectively
What Robert’s career says about fraud leadership
One of the things I like most about Robert’s story is that it shows how deeply merchant-side experience can shape later leadership. He learned through the pressure of real fraud, real customers, real operational tradeoffs, and real consequences. That kind of background tends to create a very grounded view of risk.
And honestly, that matters more than people think.
It is one thing to talk about fraud technology leadership from the outside. It is another thing to do it after years of wrestling with fraud at the merchant level, where every decision affects revenue, customer trust, workload, and business growth. That is a very different perspective, and usually a much more useful one.
- Fraud technology leadership is stronger when it is rooted in operational reality
- Merchant fraud lessons often produce better product and strategy thinking later
- Fraud operations leadership grows through pressure, judgment, and repeated problem solving
- Anti-fraud pioneer stories are useful because they show how the field matured through experience
What trust and safety teams can take from this now
So what should teams take from this episode today?
First, do not underestimate how much can be built when a team is willing to solve the problem in front of it, even without perfect tools. Second, trust and safety is not a side function. It is a business-critical capability, especially in fast-growing digital environments. And third, some of the most durable lessons in fraud still come from the early teams that had to build the function while fighting the attacks at the same time.
That is the part that really holds up for me.
Robert’s story is not just interesting because it is early history. It is useful because the same principles still apply. Strong judgment. Cross-functional collaboration. Creative problem solving. Clear ownership. A willingness to learn quickly. That is still what good trust and safety work looks like.
The big takeaway from this episode is pretty straightforward. Trust and safety is not just a discipline shaped by tools. It is a discipline shaped by operators who learned how to protect fast-moving businesses before the industry had mature answers. And that is exactly why Robert Capps’s perspective is still worth listening to.
