---
updatedAt: 2025-07-28T13:11:43.000Z
agentTools:
  projectIndex: https://developer.norbr.io/llms.txt
---

# 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.

<Image align="center" border={false} caption="3DS Challenge flow after frictionless attempt" src="https://files.readme.io/c18217c807c1e9d12ad5e47abecfb558fcf317d90b8ab90fd543424ebaa11483-3.png" />

```mermaid
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]
```