✅ Exempting Customers from 3DS Processing

🕒 When to Exempt a User from 3DS

Exempting a user from 3DS allows transactions to process without additional authentication, which:

• Reduces friction
• Improves conversion rates

This is typically used for:

• Low-risk transactions (e.g., small purchases)
• Trusted, repeat customers

🚧

Note:

Some issuing banks, especially in the EU, may override 3DS exemptions, leading to declined transactions.

🛠️ How to Exempt a User from 3DS

Steps:

1. Navigate to the customer's record
2. Select Exempt 3DS Processing

🔍 How to Interpret 3DS Transactions

🧾 Key Definitions

• CAVV – Cardholder Authentication Verification Value
• ECI – Electronic Commerce Indicator
• DS Transaction ID – Unique ID for the transaction
• Version – 3DS protocol version used
• Authentication Status – Whether authentication succeeded or failed
• Transaction Status – Outcome of the issuer's authentication process
• Transaction Status Reason – Code indicating why a transaction was approved, rejected, or flagged
• Access Control Server (ACS) – Handles 3DS authentication between issuer, merchant, and cardholder

📊 Breakdown of Transaction Statuses

🔍 Details on the A (Attempted) Status

If the issuer does not support 3DS or has an internal error:

• The card network (Visa, Mastercard, etc.) may step in to assess the transaction.
• The network evaluates based on:
  • Transaction amount
  • Merchant category
  • Risk profile

Possible Outcomes:

• If approved: Issuer assumes liability.
• If rejected: A (Attempted) is returned and the issuer still assumes liability.

🧾 Transaction Status Reason Codes

Visual Examples

Successful 3DS Transactions

Rejected 3DS Transactions