> 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/tokenization/implement-tokenization/post-tokenization-requests/update-the-digital-card-assurance-method-e-commerce-only.md).

# Update the digital card assurance method (e-Commerce only)

## Update the digital card assurance method

This is a post-**Tokenization** **LCM** use case for a digital card.

These flows are typically initiated by the **Token requestor**. For example, an e-commerce merchant.

They increase the trust level of an existing token.

During e-commerce **Tokenization**, the issuer typically approves requests without conditions. It triggers step-up only when it detects risk signals, such as an expired card or an incorrect **CSC**.

This means no **ID\&V** method is used to validate the **Tokenization** outcome.

[EMVCo](https://www.emvco.com/emv-technologies/payment-tokenisation/) calls this trust level the token assurance method. It is also known as the token assurance level.

Payment networks support post-**Tokenization** flows that the **Token requestor** can trigger while the digital card is active. These flows update the token assurance method.

D1 supports these flows on behalf of the **Issuer**.

### Payment network frameworks

Payment networks define frameworks for post-**Tokenization** assurance updates.

Framework names are payment network-specific:

* Visa: Cloud Token Framework (CTF)
* Mastercard: MDES **ID\&V** (also called post-**Tokenization** authentication)

### Supported flows

Payment networks typically support two flows:

* [Device binding flow](/tokenization/implement-tokenization/post-tokenization-requests/update-the-digital-card-assurance-method-e-commerce-only/device-binding-flow.md)\
  The **Token requestor** requests device binding from the payment network **TSP**.
* [Cardholder verification flow](/tokenization/implement-tokenization/post-tokenization-requests/update-the-digital-card-assurance-method-e-commerce-only/cardholder-verification-flow.md)\
  The **Token requestor** requests, from the **Issuer** through the payment network **TSP**, a list of **ID\&V** methods. The **End User** completes one method to increase the token assurance method.

Both of those flows involves the issuer to take a decision and this is where D1 orchestrates those requests on behalf of the issuer.

### Result of a successful flow

If authentication succeeds, the payment network **TSP** can update:

* The digital card assurance method (assurance level).
* Device binding information (for device binding use cases).

When supported by the payment network, the **TSP** includes these signals in authorization requests. This gives the **Issuer** higher confidence during authorization.


---

# 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/tokenization/implement-tokenization/post-tokenization-requests/update-the-digital-card-assurance-method-e-commerce-only.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.