> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/3d-secure/implement-3ds/implement-frictionless-flow.md).

# Implement frictionless flow

## Overview

The 3DS frictionless flow authenticates the end user without a challenge when the transaction is assessed as low risk based on your configured risk rules. This preserves a seamless checkout while remaining compliant with EMV 3‑D Secure (3DS).

{% hint style="info" %}
To enable frictionless outcomes, configure your thresholds and conditions in [Configure rulesets for 3DS decisioning](/3d-secure/implement-3ds/configure-rulesets-for-3ds-decisioning.md).
{% endhint %}

## User experience

<figure><img src="/files/GJsoQUpUhqR17IafPOIL" alt=""><figcaption><p>End user experience for a frictionless 3DS authentication (no challenge presented).</p></figcaption></figure>

## Flow

<figure><img src="/files/gGcaLvMmDnT8fRSnYevo" alt=""><figcaption><p>High‑level frictionless flow from the merchant’s 3DS request to Issuer Backend notification.</p></figcaption></figure>

## Sequence diagram

### Prerequisites

* Card products are configured in the D1 backend and in the payment network directory server.
* The end user and card are registered in the D1 backend.

<figure><img src="/files/S10AlVeu86zj0O33vW2H" alt=""><figcaption><p>End‑to‑end message sequence for 3DS frictionless authentication.</p></figcaption></figure>

At the end of the flow, the issuer backend is informed about the authentication details via the [Notify 3DS Card Operation](/3d-secure/integrate-d1-api/d1-api-reference/outbound-api-from-d1.md) endpoint.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.payments.thalescloud.io/3d-secure/implement-3ds/implement-frictionless-flow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.