The 3D Secure liability shift is a rule protecting you from fraudulent transactions.

For example, if your consumer denies they authorised or made a purchase, (due to a lost or stolen card) and the 3D Secure authentication was successful (following either the frictionless or challenge flow), the liability for the payment shifts from you to the issuing bank.

Liability shift does not apply to transactions where authentication is not performed:

Authentication Outcomes

Liability Shift

Integration Steps

Judopay Developer Documentation

Quick Start

Introduction

Authentication Methods

Interact with the Transaction API

Payments Glossary

Managing SCA Compliance

What is 3D Secure?

How 3D Secure Works

Improving Authentication in your Payment Flow

Exemptions to SCA

Simulate 3D Secure Test Flows

Authentication

Android

React Native

Mobile SDKs

Web SDK

Web Payments

PayByLink

WooCommerce Plugin

Web Integrations

Virtual Terminal (MOTO)

.NET and PHP Integrations

Server SDK Integration

Apple Pay and Google Pay Wallets

Wallet Payments

PayPal

Incremental Authorisation

Merchant Initiated Transactions

Fraud Prevention Solutions

Testing your Direct (API) Integration

Testing your Web SDK Integration

Testing your Web Payments Integration

Testing your Mobile SDK Integration

Testing your Wallet Payment Integration

Sandbox Environment

Test Cards

Troubleshooting

Testing Overview

Go Live Checklist

Change Logs

Comms Log

Codes and Descriptions

Country Codes

Webhooks

Developer Tutorials

Deprecated Integration Methods

Developer Hub

Contact Us

Liability Shift

What is Liability Shift?

When Liability Shift does not apply