Skip to main content
For fraud disputes, Decisionly retrieves authorization data from the card network after you file 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 file a fraud case, Decisionly automatically checks authorization data in the background. If any of the conditions below are detected, the case cannot be filed because the card network will deny the chargeback.

​
Fraud Liability Checks

Decisionly checks network data for the following conditions:
  • 3D Secure Authenticated
  • Face-to-Face Card Read
  • ATM Transaction
  • PIN Verified
  • CAT Level 1
  • CAT Level 3
  • Automated Fuel Dispenser
  • Consumer Presented QR Code
  • CVV Check Failed
  • Cash Back Transaction
  • 35 Fraud Chargebacks on Card
When any of these conditions are present, liability for the fraud shifts from the merchant to the issuer. 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.