> 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-through-mobile-sdk/token-verification-for-e-commerce.md).

# Token verification for e-commerce

Use token verification to update the assurance method of an e-commerce token after successful ID\&V.

When the end user verifies through the issuer application, the issuer application must report the verification result. The D1 SDK supports this flow without changes to the issuer backend protocol.

For the end-to-end flow, supported payment networks, and ID\&V requirements, see [Token verification for e-commerce](https://docs.payments.thalescloud.io/tokenization/implement-tokenization/post-tokenization-requests/update-the-digital-card-assurance-method-e-commerce-only.md).

### High-level flow

This flow is already depicted in the section [Token verification for e-commerce](https://docs.payments.thalescloud.io/tokenization/implement-tokenization/post-tokenization-requests/update-the-digital-card-assurance-method-e-commerce-only.md) and, in particular, when it comes to the issuer application ID\&V (see [Verification by Issuer Application](https://docs.payments.thalescloud.io/tokenization/implement-tokenization/post-tokenization-requests/update-the-digital-card-assurance-method-e-commerce-only.md#verification-by-issuer-application)), the SDK can be used to accomplish the objective to report the result, as depicted in the below high level flow:

<figure><img src="https://2043231064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FW6dljaTEEzefPQILRFB7%2Fuploads%2FfII61NOIhDYNsZdFScI9%2FToken-Verification-by-SDK.png?alt=media&amp;token=edc5c681-417e-4dda-9fd6-f74d3e7a12d3" alt=""><figcaption></figcaption></figure>

Below, the related detailed sequence diagram and sample codes.

### Sequence diagram

#### Verification by the issuer application

For the full flow, check the [Token Verification for e-commerce](https://docs.payments.thalescloud.io/tokenization/implement-tokenization/post-tokenization-requests/update-the-digital-card-assurance-method-e-commerce-only-1.md) section.

<figure><img src="https://2043231064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FW6dljaTEEzefPQILRFB7%2Fuploads%2FHVLWJnmDmUJLX9hywS14%2FReport%20result%20by%20SDK%20-%20version1.png?alt=media&amp;token=1d882107-c489-45f9-a16f-1bbb2a2c797e" alt=""><figcaption></figcaption></figure>

#### Verification by issuer application using an issuer-managed trigger

For the full flow, check the [Token Verification for e-commerce](https://docs.payments.thalescloud.io/tokenization/implement-tokenization/post-tokenization-requests/update-the-digital-card-assurance-method-e-commerce-only-1.md) section.

<figure><img src="https://2043231064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FW6dljaTEEzefPQILRFB7%2Fuploads%2FMTG9828zmo6NqFBFjz5u%2FReport%20result%20by%20SDK%20-%20version2%20-PUSH%20trigger.png?alt=media&amp;token=28a9475a-a934-485d-986a-56b8217f5e37" alt=""><figcaption></figcaption></figure>

### Sample code


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.payments.thalescloud.io/tokenization/implement-tokenization/post-tokenization-through-mobile-sdk/token-verification-for-e-commerce.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
