> ## Documentation Index > Fetch the complete documentation index at: https://docs.enfuce.com/llms.txt > Use this file to discover all available pages before exploring further. # Change the status of a token > Change token status Change the status of a token linked to a card. This endpoint allows you to manage the lifecycle of an individual token when more granular control is required. The `tokenId` value uniquely identifies the token to update and can be retrieved from the [Get tokens](#operation/getTokens) endpoint. This functionality is supported for both Mastercard and Visa tokens. By default, token status follows card status changes. This endpoint does not replace that default behaviour. Instead, it allows you to explicitly manage a specific token when needed, independently of card status updates. Typical use cases Temporary block of a single token A cardholder reports a device issue, but the card itself should remain active. You can suspend the affected token without blocking the entire card or other tokens. Once resolved, the same token can be resumed. Correcting a token status inconsistency In some situations, a token may remain inactive or suspended due to a prior event, technical issue, or external update. You can explicitly activate or resume the token to restore its usability without changing the card status. ## OpenAPI ````yaml wallet put /v1/tokens/{tokenId}/{action} openapi: 3.0.3 info: version: '1' title: Wallet operations contact: name: Enfuce Financial Services url: https://enfuce.com email: info@enfuce.com x-logo: url: resources/enfuce.svg altText: Enfuce logo description: > Wallet API enables getting needed data for tokenization and enablement in programs like Apple Pay and Google Pay, and Visa Click to Pay. #### Terms used
Term Definition
Customer End customer using financial institution's mobile application
In-app activation Wallet provisioning using financial institution app as authentication method
In-app provisioning Mastercard's term for push provisioning
Push provisioning VISA's term for pushing card details from within mobile application. This term will be used in this document
Wallet provider Such as Apple Pay, Google Pay or Samsung Pay
It's called in two cases: - *Push provisioning* - this is usually done within issuers own application and card holder does not need to enter any information. Then the different endpoints for push provisioning must be used. - *In-app activation* - activating a card by manually adding information, then endpoint for generate activation data must be used after authentication of end customer is completed. ![ Provisioning example ](https://enfuce-public-resources.s3.eu-central-1.amazonaws.com/public/wallet_push_prov.svg) In above case the difference between push provisioning and in-app activation is which endpoint that is called in step 3. Note that diagram above is a simplification of full flow in order to explain it from a developer point of view. servers: - url: >- https://integration-api-cat2.{{environment}}.ext.{{realm}}.cia.enfuce.com/wallet - url: https://integration-api-cat2.live.ext.prod.cia.enfuce.com/wallet description: Live environment security: [] tags: - name: Push Provision - name: Activation data - name: Get tokens - name: Visa Click2Pay Enrol and Manage - name: Token Management paths: /v1/tokens/{tokenId}/{action}: put: tags: - Token Management summary: Change the status of a token description: > Change token status Change the status of a token linked to a card. This endpoint allows you to manage the lifecycle of an individual token when more granular control is required. The `tokenId` value uniquely identifies the token to update and can be retrieved from the [Get tokens](#operation/getTokens) endpoint. This functionality is supported for both Mastercard and Visa tokens. By default, token status follows card status changes. This endpoint does not replace that default behaviour. Instead, it allows you to explicitly manage a specific token when needed, independently of card status updates. Typical use cases Temporary block of a single token A cardholder reports a device issue, but the card itself should remain active. You can suspend the affected token without blocking the entire card or other tokens. Once resolved, the same token can be resumed. Correcting a token status inconsistency In some situations, a token may remain inactive or suspended due to a prior event, technical issue, or external update. You can explicitly activate or resume the token to restore its usability without changing the card status. operationId: changeTokenStatus parameters: - name: tokenId in: path description: > The token id to update. You can retrieve this value from the [Get tokens](#operation/getTokens) endpoint. required: true schema: type: integer format: int64 - name: action in: path description: The action to perform on the token required: true schema: $ref: '#/components/schemas/TokenAction' - name: auditUser in: query description: The audit user to log the request required: true schema: type: string responses: '200': description: Token status updated successfully headers: X-Correlation-Id: description: Unique identifier for tracking this request schema: type: string content: application/json: schema: $ref: '#/components/schemas/TokenOperationResponse' '400': description: Bad Request '401': description: Unauthorized '403': description: Forbidden '404': description: Token not found '500': description: Internal server error components: schemas: TokenAction: type: string enum: - activate - deactivate - suspend - resume x-enumDescriptions: activate: enable a previously inactive token deactivate: permanently disable the token suspend: temporarily prevent token usage resume: restore a suspended token TokenOperationResponse: type: object properties: status: type: string description: Status of the token after the operation ````