New in Chargebee: Explore Reveal and understand your payment performance end-to-end.Try Now
Docschargebee docs
HomeBillingPaymentsRevRecGrowthReveal
Support

Product Updates


  • Release Notes

Payment Methods


  • Payment Methods Overview
  • Cards
  • Direct Debit
  • Bank Based Payments
  • Wallets
  • Vouchers
  • Articles and FAQ

Payment Gateways and Configuration


  • Payment Gateways Overview
  • Chargebee Test Gateway
  • Stripe
  • PayPal Payment Services
  • Chargebee Pay
  • Adyen
  • Authorize.net
  • Bambora (formerly Beanstream)
  • Bank of America
  • BluePay
  • BlueSnap
  • Braintree
  • Checkout.com
  • CyberSource
  • dLocal
  • EBANX
  • Ecentric
  • Elavon
  • E-xact Direct Integration
  • eWay Rapid
  • Global Payments
  • GoCardless
  • J.P. Morgan Mobility Payment Solutions
  • Metrics Global
  • Mollie
  • Moneris
  • Network Merchants Incorporated (NMI)
  • Nuvei
  • Orbital (Chase Paymentech)
  • Pay.com
  • Paymill
  • Paystack
  • Pin Payments
  • QuickBooks Payments
  • Razorpay
  • Sage Pay
  • Solidgate
  • Tempus
  • Twikey
  • Windcave
  • Worldline Online Payments(formerly Ingenico)
  • Worldpay
  • Articles and FAQ

Level 2/3 Data Support


  • Level 2/3 Data Support

Payment Optimization Engine


  • Overview
  • Defaults
  • Advanced Setup
  • Payment Method Display Rules
  • Verification Rules
  • Routing Rules

Dunning


  • Dunning
  • Articles and FAQ

Offline Checkout


  • Offline Checkout
  • Articles and FAQ

Transaction Sync & Invoice Mapping


  • Transaction Sync and Invoice Mapping

Fraud Management


  • Fraud Management

Error Handling


  • Errors with Root Cause and Troubleshooting

Payment Lifecycle Logs


  • Payment Intents
  • Transactions
  • Gateway Activity Logs
  • Gateway Webhook Logs
  • Articles and FAQ

Others


  • Reach (Merchant of Record)
  • Bulk Deletion of Payment Methods
  • Custom Payment Methods
  • Payment Initiator Parameter
  • PSD2 and Strong Customer Authentication
  • RBI e-Mandate
  • RBI Tokenization Regulations
  • Chargeback Management
  • Transaction Descriptors
  • Payment Preferences
  • Visa Trial Rules
  • Mastercard Trial Rules
  • Co-badged Card Compliance
  • Articles and FAQ
  1. Payments
  2. Payment Gateways and Configuration
  3. Articles and FAQ
  4. Adyen
  1. Payments
  2. Payment Gateways and Configuration
  3. Articles and FAQ
  4. Adyen

Why does the 3DS popup appear on every payment when using Adyen?

Problem Statement

When you use Chargebee's Custom Checkout with the Adyen gateway and call authorizeWith3ds to enable 3D Secure authentication, a 3DS overlay or popup may appear even for card transactions that qualify as frictionless flows, that is, transactions that don't require active customer authentication.

This adds unnecessary friction for your customers, because the 3DS challenge screen appears even when the card issuer has already approved the transaction silently.

Solution

The Dynamic 3D Secure configuration in your Adyen Dashboard controls this behavior. By default, Adyen might apply 3DS to all transactions. When you set the Request challenge field to Prefer not, Adyen skips the 3DS challenge unless the card issuer or a regulation requires it.

Configure Dynamic 3D Secure in Adyen

Follow these steps to configure Dynamic 3D Secure in Adyen.

  1. Log in to your Adyen Dashboard.
  2. Navigate to Revenue & Risk > Dynamic 3D Secure.
  3. For each rule, set Request challenge to Prefer not.
  4. Save your changes.

With this setting, Adyen still applies 3DS when:

  • A regulation requires it, such as PSD2 in Europe.
  • The card issuer mandates it.
  • It improves transaction outcomes, such as a liability shift.

For cards that support frictionless authentication, the 3DS overlay no longer appears unnecessarily.

Note

You manage this configuration entirely in the Adyen Dashboard. It doesn't require any changes to your Chargebee or Chargebee.js integration.

Related Articles

What is Adyen?
What are the prerequisites that needs to be set in Adyen before connecting it with Chargebee?
Adyen- Allowed Origins
'Adyen Error message: "010- Not allowed"'
Operation not supported for Adyen Gateway
'Error : "Required field ''billingAddress.street'' is not provided" in checkout while processing the payment to Adyen gateway'
In what scenario would Chargebee not log any record of the failed transactions in Adyen?
Error while enabling a payment method - Adyen

Show more

Was this article helpful?