> 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/nfc-wallet-sdk-android/implement-nfc-wallet/tokenize-a-card/digitize-a-card/green-flow-digitization.md).

# Green flow digitization

## Overview

Green flow is a Tokenization flow where the issuer backend approves Tokenization without step-up authentication.

This flow is common when the NFC Wallet SDK is integrated in the issuer application and the end user is already authenticated in-app.

## User experience

See Green [flow user experience](/nfc-wallet-sdk-android/implement-nfc-wallet/tokenize-a-card.md#green-flow).

## Sequence diagram

<figure><img src="/files/OKivmeylr83mgX30soLK" alt=""><figcaption></figcaption></figure>

## Integrate SDK

After you [Check card eligibility](/nfc-wallet-sdk-android/implement-nfc-wallet/tokenize-a-card/check-card-eligibility.md). Implement `MGDigitizationListener` to track digitization progress and then:

1. Call `MGCardEnrollmentService.digitizeCard(...)`&#x20;

   Include an `authenticationToken` generated by your digital wallet backend.

   You should provide a reference of your `MGDigitizationListener`&#x20;
2. If Tokenization is approved with no conditions (green flow), the SDK emits theses callbacks:
   1. `onCPSActivationCodeAcquired`

      You receive the `activationCode` to start the secure provisioning.

      See [Trigger provisioning](/nfc-wallet-sdk-android/implement-nfc-wallet/tokenize-a-card/trigger-provisioning.md).
   2. `onComplete`

      Digitization steps is completed successfully.
3. The **Tokenization** is completed when the provisioning session is completed

   Check callback `EnrollingServiceListener.onComplete(`) as described in [Trigger provisioning](/nfc-wallet-sdk-android/implement-nfc-wallet/tokenize-a-card/trigger-provisioning.md)


---

# 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/nfc-wallet-sdk-android/implement-nfc-wallet/tokenize-a-card/digitize-a-card/green-flow-digitization.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.