3D Secure: what it covers and what it locks in on disputes

swype

WALLETS & SECURITY • 3D SECURE

3D Secure support and dispute liability

3DS is supported as an additional authentication layer — and it has a direct effect on which disputes your program can actually win. Here's the mechanics.

AUDIENCE

B2B Clients

PROTOCOLS

3DS 1.0 & 2.x

FRAUD DISPUTES

Auto-declined

Summary: 3D Secure is supported as an additional authentication layer for online transactions. Transactions successfully authenticated via 3DS — including 3DS 1.0 and 3DS 2.x — are deemed cardholder-authorized. Fraud and unauthorized-use disputes on those transactions are automatically declined, with no provisional credit issued.

①

What 3DS support covers

3D Secure adds a cardholder authentication step at checkout — commonly a one-time passcode, banking app confirmation, or biometric prompt — for online transactions where the merchant triggers it. Swype supports both legacy and current protocol versions:

●

3DS 1.0 (legacy protocol)

●

3DS 2.x (current protocol, including frictionless and challenge flows)

●

Any successor protocol recognized by the card networks as equivalent

②

The dispute rule that matters most

This is the part with direct financial impact for your program. Any transaction that completes 3DS authentication successfully is treated as cardholder-authorized as a matter of program policy — not just a presumption that can be argued case by case:

●

Fraud and unauthorized-use disputes on 3DS-authenticated transactions are automatically declined

●

No provisional credit or refund is issued by Swype or the issuing bank for that category of dispute

●

This is independent of whether the cardholder claims someone else completed the authentication step on their device

③

How this interacts with chargeback fees

3DS authentication doesn't exempt a dispute from the standard chargeback fee — it determines whether the dispute can succeed, not whether it costs anything to file. In practice:

●

A non-refundable chargeback fee applies to every dispute filed, regardless of outcome — including disputes that get auto-declined for being 3DS-authenticated

●

Encouraging end users to dispute a 3DS-authenticated transaction as fraud will reliably fail and still generate the fee

Important

Build this rule into your own end-user support scripting. If your front-line support tells a cardholder to dispute a 3DS-authenticated charge as unauthorized, you're setting an expectation that the dispute mechanics can't fulfill — route those cases to merchant-level resolution instead.

Seeing a pattern of disputed 3DS transactions?

Talk to us if you're seeing unusual dispute volume tied to authenticated transactions.

Contact Support →