What is the correct order of actions for Radar for Teams?

What is the correct order of actions for Radar for Teams?

• A. Request 3DS, Allow, Block, Review
• B. Review, Block, Allow, Request 3DS
• C. Request 3DS, Review, Allow, Block
• D. Allow, Request 3DS, Block, Review

Answer: (A)

Radar for Teams is built to layer fraud defenses in a way that adds authentication when possible, preserves a smooth checkout for legitimate customers, and gives you a clear path for uncertain cases. Start by requesting 3DS because adding 3D Secure authentication provides an extra verification step that can validate the cardholder and, if successful, reduce risk and liability for the merchant. If the 3DS check passes or isn’t required, you move forward with allowing the transaction so legitimate customers aren’t slowed down. If there’s still risk after attempting 3DS, the next automatic step is to block to stop potentially fraudulent activity. If the decision isn’t clear—if signals are inconclusive—you then route the transaction to human review to apply judgment with fuller context. This sequence—request 3DS, then allow when safe, then block when risk remains, and escalate to review for ambiguous cases—optimizes security and user experience by authenticating first, approving safe cases automatically, blocking high risk, and involving a human only when needed.

Radar for Teams is built to layer fraud defenses in a way that adds authentication when possible, preserves a smooth checkout for legitimate customers, and gives you a clear path for uncertain cases. Start by requesting 3DS because adding 3D Secure authentication provides an extra verification step that can validate the cardholder and, if successful, reduce risk and liability for the merchant. If the 3DS check passes or isn’t required, you move forward with allowing the transaction so legitimate customers aren’t slowed down. If there’s still risk after attempting 3DS, the next automatic step is to block to stop potentially fraudulent activity. If the decision isn’t clear—if signals are inconclusive—you then route the transaction to human review to apply judgment with fuller context. This sequence—request 3DS, then allow when safe, then block when risk remains, and escalate to review for ambiguous cases—optimizes security and user experience by authenticating first, approving safe cases automatically, blocking high risk, and involving a human only when needed.