Security guard in a corporate lobby

Your fraud strategy has a blind spot.

Should you ever stand on the Lions Gate Bridge looking out over Vancouver’s Burrard Inlet in British Columbia, you’ll see more than a beautiful sunset. You’ll see the lifeblood of Canadian commerce in motion. Massive container vessels move through the harbour carrying millions of dollars in timber, minerals, automotive parts and consumer goods.

Now imagine if every incoming ship had to drop anchor in English Bay for a six-hour inspection before entering the port. The supply chain would quickly grind to a halt.

To keep trade moving without compromising security, maritime operations rely on different layers of protection. The Coast Guard’s Marine Communications and Traffic Services (MCTS) monitor vessel movements and identify suspicious activity in coastal waters. The Canada Border Services Agency (CBSA), meanwhile, conducts inspections and verifies cargo when vessels arrive.

Each has a different job. Both are essential.

Digital commerce faces a similar challenge. As transaction volumes grow and automated botnets launch waves of stolen-card attacks against online storefronts, merchants evaluating Elavon’s security solutions, particularly Pay Defense and 3DS 2.0, sometimes assume the two tools do the same thing.

They don’t.

Just as maritime security separates monitoring from inspection, Elavon’s security tools address different stages of payment risk. Understanding the distinction is key to building a strategy that protects your business without slowing down legitimate transactions.

Pay Defense: Your early-warning system

Elavon’s Pay Defense is your coastal traffic tower, scanning the horizon for suspicious activity before a transaction reaches the payment authorization stage.

Powered by machine learning, Pay Defense is designed to identify potentially fraudulent behaviour before an authorization is attempted.

As a customer approaches checkout, the system evaluates the signals surrounding that transaction. Is someone accessing the site at 3:00 AM through a masked VPN? Are they interacting with hidden honeypot fields? Are they testing dozens of different card numbers in under a minute?

These are the kinds of behavioural signals that can indicate automated attacks or suspicious activity.

By identifying potential threats early, Pay Defense can help merchants stop risky transactions before they enter the payment channel or generate unnecessary authorization costs. It also provides a risk score and recommendation to help guide the decision.

Pay Defense can operate as a standalone value-added service, providing an important early-warning layer within your payments infrastructure.

But here’s the distinction that catches many merchants off guard: identifying suspicious behaviour is not the same as verifying the cardholder’s identity or transferring fraud liability.

A transaction can look perfectly legitimate to a behavioural risk model and still involve a stolen card. If that transaction is approved and later disputed as fraud, Pay Defense’s risk assessment does not, on its own, shift the financial liability.

That’s where 3DS 2.0 comes in.

3DS 2.0: The identity check at the dock

If Pay Defense is the coastal watch, 3DS 2.0 is the customs inspection at the dock.

Rather than simply assessing how a transaction behaves, 3DS 2.0 helps verify whether the person initiating the purchase is the legitimate cardholder.

The protocol passes contextual transaction data directly to the cardholder’s issuing bank. Based on that information and its risk assessment, the transaction may be authenticated seamlessly or trigger an additional verification step, such as a biometric check or one-time passcode.

The objective is straightforward: give the issuing bank the information it needs to determine whether the person making the purchase is authorized to use the card.

And there’s another important distinction.

A fraud score is an internal risk assessment. Successful 3DS 2.0 authentication can provide a liability shift for eligible transactions, moving responsibility for certain fraud-related chargebacks from the merchant to the card issuer, subject to applicable card network rules and authentication requirements.

In other words, Pay Defense helps identify suspicious traffic before it reaches authorization. 3DS 2.0 adds a layer of cardholder authentication that can provide meaningful financial protection when a qualifying transaction is disputed.

Why you need both

The busiest ports don’t rely on a single security measure. They use multiple layers, each designed to do a different job.

Your payment environment should work the same way.

Using Pay Defense and 3DS 2.0 together allows merchants to assess risk before authorization and introduce stronger cardholder authentication when appropriate.

Pay Defense can help identify suspicious activity early, while 3DS 2.0 provides an additional authentication layer for transactions that require it. The objective isn’t to send every customer through an intensive verification process. It’s to apply the right level of scrutiny based on the risk.

That balance matters.

Too little protection leaves your business exposed to fraud. Too much friction can frustrate legitimate customers and lead to abandoned transactions. A well-designed strategy helps distinguish between the two, protecting revenue while keeping the checkout experience moving.

At Cartis Payments, we help businesses build payment security strategies that protect their bottom line without bottlenecking commerce. Our team can help you integrate Pay Defense and 3DS 2.0, configure the rules, calibrate risk thresholds and navigate the technical requirements.

Is your current fraud strategy leaving a gap?

Reach out to the team at Cartis Payments to discuss how the right combination of fraud prevention and authentication can help protect your business, reduce unnecessary friction and keep your checkout channel clear, fast and secure.

We’ll help you navigate the waters.

Contact Us