When a charge matches a review rule, which of the following may also happen?

When a charge matches a review rule, which of the following may also happen?

• A. The payment is captured
• B. The payment is routed through 3D Secure
• C. The payment is authorized but not captured
• D. The payment is declined by the network

Answer: (B)

Radar review rules are used to flag transactions that look risky and may trigger extra verification in the payment flow. When a charge matches a review rule, Stripe may require the cardholder to complete 3D Secure authentication. This additional step involves the card-issuing bank verifying the cardholder, and it can be the path the payment takes before authorization proceeds. In other words, the charge may be routed through 3D Secure to add a layer of verification before the payment is approved. The other outcomes—capturing a payment, having an authorized-but-not-captured state, or a network decline—are parts of different parts of the flow and aren’t specifically triggered by simply matching a review rule.

Radar review rules are used to flag transactions that look risky and may trigger extra verification in the payment flow. When a charge matches a review rule, Stripe may require the cardholder to complete 3D Secure authentication. This additional step involves the card-issuing bank verifying the cardholder, and it can be the path the payment takes before authorization proceeds. In other words, the charge may be routed through 3D Secure to add a layer of verification before the payment is approved. The other outcomes—capturing a payment, having an authorized-but-not-captured state, or a network decline—are parts of different parts of the flow and aren’t specifically triggered by simply matching a review rule.