引導式測驗 · 中等 等級
基於風險的身份驗證和 3D 安全測驗
解釋基於風險的支付身份驗證、EMV 3DS 無摩擦和質疑流程以及商家控制的限制。
問題 1 的 8
When might risk-based authentication request additional proof from a cardholder?
預覽每個問題8 問題
當您參加測驗時,就會出現答案和解釋。
- When might risk-based authentication request additional proof from a cardholder?
- To guarantee every transaction is approved
- To set the customer’s credit limit
- To replace payment authorization
- When transaction context warrants it
- What happens in an EMV 3DS frictionless flow?
- The merchant permanently stores a password
- The issuer authenticates without an interactive cardholder prompt
- The card is automatically charged regardless of authorization
- The customer must call the merchant
- Who determines the 3DS authentication flow for a transaction?
- The merchant’s web designer
- The cardholder’s social-media account
- The issuer’s Access Control Server
- A job-board provider
- What does a 3DS challenge flow require?
- Additional authentication from the cardholder
- No cardholder interaction
- A new bank account
- A merchant-side legal decision
- Does successful authentication guarantee that the payment is authorized?
- Yes, it guarantees settlement
- No; authorization is a separate payment decision
- Yes, unless the merchant cancels
- Only for online purchases
- Can a merchant force the issuer to use a preferred 3DS flow?
- Yes, every time
- Only by hiding transaction data
- Only if the customer uses a desktop
- No; the issuer determines the final flow
- Which scenario should a payments team test?
- Challenge, timeout, failure and payment decline paths
- Only a successful frictionless result
- Only the checkout loading screen
- The issuer’s internal model source code
- What trade-off should a merchant monitor when using more challenges?
- Whether the logo appears correctly
- Whether all customers use one bank
- Fraud outcomes alongside checkout friction and legitimate failures
- 模型是否具有足夠的參數