> 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/classic-tokenization/use-cases/card-enrolment/generic-enrollment-flow/step-5-activate-the-token/option-b-activate-with-sms-or-email-otp.md).
# Option B: activate with SMS or email OTP
Use this option when the issuer backend returns `levelOfTrust=yellow`. The end user completes step-up authentication using an OTP. The OTP is delivered by SMS or email.
Token activation using SMS or email OTP.
### Flow
{% stepper %}
{% step %}
### 1. Return OTP methods
Return `idvMethodList` in `requestCardDigitization` (step 4). Include SMS OTP and/or email OTP methods.
{% endstep %}
{% step %}
### 2. Deliver the OTP
Tokenization Service calls `sendOTP` on the issuer backend. Send the OTP to the end user using the selected channel. Do not transform the OTP value.
{% endstep %}
{% step %}
### 3. Complete activation
The end user enters the OTP in the wallet application. The token requestor and payment network **TSP** validate it. Tokenization Service activates the token.
{% endstep %}
{% endstepper %}
### Issuer backend responsibilities
* Send the OTP to the end user quickly.
* Apply your fraud and rate-limit controls before sending.
* Return an error when you cannot deliver the OTP.
See `sendOTP` in the [API reference](/classic-tokenization/api-reference/issuer-gateway-api/outbound-to-issuer.md).
### notifyVirtualCardChange on completion
Tokenization Service sends `notifyVirtualCardChange` after successful activation.
See `notifyVirtualCardChange` in the [API reference](/classic-tokenization/api-reference/issuer-gateway-api/outbound-to-issuer.md).
#### notifyVirtualCardChange parameters
| Parameter | Description |
| ------------------ | --------------------------------------------------------------------------- |
| `x-correlation-id` | Contains the same value provided in `requestCardEligibility`. |
| `virtualCardId` | Identifies the updated virtual card. |
| `action` | Is set to `ACTIVATE`. |
| `tokenInfo` | Provides the DPAN and expiry date at activation (when provided by the TSP). |
| `isPrimary` | Is set to `true`. |
---
# 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/classic-tokenization/use-cases/card-enrolment/generic-enrollment-flow/step-5-activate-the-token/option-b-activate-with-sms-or-email-otp.md?ask=&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.
