Which describes a built-in 3D Secure rule example?

Which describes a built-in 3D Secure rule example?

• A. Block the payment
• B. Automatically refunds the payment
• C. Prompts customers to complete an authentication step and shifts liability to the issuer
• D. Deny the transaction

Answer: (C)

Built-in 3D Secure rules center on authentication and shifting fraud liability. When a cardholder is enrolled and 3D Secure is invoked, the system prompts the customer to complete an authentication step (a 3DS challenge). If authentication succeeds, the liability for fraud shifts to the card issuer, not the merchant. This reflects the purpose of 3DS: add a user verification layer and, upon successful verification, reduce the merchant’s risk. The other options describe actions not inherent to the 3D Secure flow. Simply blocking the payment, automatically refunding, or denying the transaction are not the typical built-in 3DS outcomes; they are separate risk or processing decisions outside the standard authentication and liability-shifting mechanism.

Built-in 3D Secure rules center on authentication and shifting fraud liability. When a cardholder is enrolled and 3D Secure is invoked, the system prompts the customer to complete an authentication step (a 3DS challenge). If authentication succeeds, the liability for fraud shifts to the card issuer, not the merchant. This reflects the purpose of 3DS: add a user verification layer and, upon successful verification, reduce the merchant’s risk.

The other options describe actions not inherent to the 3D Secure flow. Simply blocking the payment, automatically refunding, or denying the transaction are not the typical built-in 3DS outcomes; they are separate risk or processing decisions outside the standard authentication and liability-shifting mechanism.