On 18 October 2023, we will disable the default rule for requesting 3DS on cards that require authentication. We anticipate that this may result in an increase in acceptance rates, with minimal impact on fraud rates.

This rule was used to determine the requirement to request 3DS based on the card details. This is now no longer necessary since Stripe automatically handles soft decline codes indicating that 3DS is required by issuers. Furthermore, we also trigger 3DS when necessary, adhering to regulations like the Strong Customer Authentication mandated by the PSD2.

Here are some alternative options to maintain the same level of 3DS coverage:

• Turn on Radar's default rules for cards where 3DS is supported
• Manually request 3DS via the API
• Create your own custom 3DS rules in Radar

Some examples of custom 3DS rules include:

• Request 3D Secure if :card_country: != :billing_address_country: and :risk_level: != ‘normal’
• Request 3D Secure if is_missing(:seconds_since_card_first_seen: ) and :risk_level: != ‘normal’

Custom rules are only available to Radar for Fraud Teams (RFFT) users. If you are not a current RFFT user, you can upgrade now or try it out with a 30-day free trial.