Challenge after frictionless attempt

Even if the transaction is initially allowed to proceed as frictionless, the issuer can later require a challenge based on risk signals or policies.

Why This Happens:

• The issuer determines that additional authentication is necessary.
• The issuer reevaluates the risk partway through the transaction and may decide that Strong Customer Authentication is needed.
• After the initial authentication, fraud detection systems identify potential risk and trigger a challenge before final approval.

flowchart LR 
 A[Initially frictionless transaction] --- B[fa:fa-spinner Issuer risk analysis]
 B --> C[fa:fa-ban Issuer determins challenge required] 
 B --> D[fa:fa-check Issuer determins challenge no required]
 C --> E[Challenge flow]
 D --> F[Frictionless flow]