Sardine | Fraud Prevention Technology for PSPs and Merchants

So over the years I’ve had a lot of conversations with Payment Service Providers that wanted to build fraud prevention technology.

Not necessarily for their own internal risk controls. That would almost be too obvious. What they really wanted was to offer fraud prevention software as a value-added service to their merchants.

Honestly, I get it. Payment fraud prevention can help PSPs differentiate, win deals, increase stickiness, and create new revenue. Pretty good on paper.

But then you get to the uncomfortable part.

A lot of teams assume fraud detection technology is basically an API, payment data, and a machine learning fraud detection model that returns a fraud score.

Not a good look.

I break down why fraud prevention technology is much harder to build, maintain, and operationalize than it looks, why fraud scoring alone does not solve merchant fraud prevention, and why payment service providers need to think seriously about fraud operations, chargeback prevention, false positive reduction, payment risk management, and the support merchants actually need.

What you will hear in this episode:

Why PSPs want to offer fraud prevention technology as a value-added service
Where fraud prevention software becomes more complicated than expected
Why AI fraud detection and machine learning fraud detection are not enough on their own
How fraud scoring can create confusion if merchants do not know how to act on it
Why merchant fraud prevention requires operational support, not just fraud detection software
How chargeback prevention, false positive reduction, and payment risk management affect real business outcomes
Why fraud prevention for payment service providers needs to include strategy, support, and fraud investigation tools

Who should listen:

Payment service providers considering fraud prevention technology
PSP product leaders building payment fraud prevention services
Fraud operations and payment risk management teams
Merchants evaluating fraud prevention software or fraud management software
Risk leaders responsible for chargeback prevention and false positive reduction
Teams working with fraud detection models, fraud scoring, or fraud investigation tools
Anyone trying to understand why fraud prevention technology is not just a model returning a score

This episode is for people who want to reduce fraud without pretending fraud risk management is magically solved because someone added “AI” to the roadmap.

Episode notes:

The broader context

More PSPs want to offer fraud prevention technology to their clients.

Okay, fair. Merchants already trust their PSPs, the integration path looks easier, and bundling payment fraud prevention into an existing payments relationship sounds clean.

But you’ve got to ask yourself: which merchants are actually buying fraud prevention services from their PSP instead of a dedicated vendor, and what do they really need?

What’s working

There is real value here. PSPs already sit close to payment data, transaction flows, chargebacks, and merchant relationships.

Modern fraud detection technology, AI fraud detection, machine learning fraud detection, and fraud scoring can help identify suspicious payments faster. Strong fraud prevention software can support chargeback prevention, reduce manual review, and improve payment risk management.

Where gaps remain

Here’s the problem. Fraud prevention technology is not finished when the model returns a score.

Now what?

Does the merchant know which cutoff to use? Can they review their fraud patterns? Can they investigate suspicious payments? Can they tune rules, reduce false positives, review chargebacks, or block repeat abuse?

The human impact

A bad fraud decision is not abstract.

A false positive can block a good customer. A missed fraud attack can create chargebacks. Weak fraud scoring can leave a merchant exposed. Fragmented fraud management software can make teams slower, less confident, and more reactive.

And for smaller merchants, especially the ones most likely to buy fraud prevention through a PSP, there may not be a fraud team at all.

So when the system says “high risk,” they may be thinking, “Great. What am I supposed to do with that?”

Honestly, fair question.

Ethical responsibility

It is easy to market AI fraud detection as if it solves everything.

It does not.

If PSPs sell fraud prevention technology as a simple add-on but do not support the operational reality behind it, merchants inherit the confusion.

That is not fraud risk management. That is outsourcing anxiety with a nicer UI.

The path forward

The better path is not necessarily “never build.”

Some PSPs can absolutely build strong fraud prevention software. But the real question is whether they can afford the long-term investment required to keep fraud detection models competitive, support merchants, manage fraud operations, and adapt as fraud patterns change.

Because the real product is not just the score.

The real product is helping merchants make better fraud decisions.

Key takeaways:

The question is not just whether PSPs should offer payment fraud prevention. Some should. Some probably should not. The better question is whether they understand what they are signing up for.

Fraud prevention software is not just something you launch. It has to be maintained, tuned, explained, supported, and adapted as fraud patterns change.

So if the plan is “we’ll train a model and merchants will figure it out,” then honestly, you’ve got to ask yourself:

Is that a product, or just a future support queue?