Skip to main content
For fraud disputes, Decisionly retrieves authorization and clearing data from the card network after you create a case to determine if chargeback rights exist. For background on how authentication methods affect liability, see What Are Disputes?.

​
How Fraud Liability Works

When you create a fraud case, Decisionly automatically checks authorization and clearing data in the background for conditions that shift liability from the merchant to the issuer - things like 3D Secure authentication, a tokenized transaction, or a verified PIN. The exact set of checks depends on the card network. If any of these conditions are detected, the case cannot be filed because the card network will deny the chargeback. This doesn’t mean the cardholder’s fraud claim is invalid - it means you cannot hold the merchant liable for the transaction. The issuer may still need to reimburse the cardholder, but cannot recover funds from the merchant via chargeback.

​
Workflow Rules

You can configure workflow rules to control how fraud cases are handled based on the liability result. The workflow rule to set up is Issuer has Liability. This rule determines whether the issuer is liable for the fraud based on network data. You could use this rule to accept liability or flag for review when the issuer is liable.