# Activate a Card
source: https://developer.mastercard.com/mastercard-processing-core/documentation/use-cases/card-lifecycle/activate-a-card/index.md

## Overview {#overview}

This use case describes the process in which a cardholder receives a physical card and activates the card. You must unlock the new physical card because it is produced and set to `Locked` status by default to prevent unauthorized transactions during physical delivery.

## Sequence diagram {#sequence-diagram}

Diagram activate-card-new

### Explanation {#explanation}

1. The cardholder requests to activate their card.
2. The mobile application or e-banking service sends a request to the server to activate the card.
3. The server sends a `PUT` request to the `/cards/{card_contract_id}/active` endpoint by passing the `true` value in the `activated` field in the request body.
4. The card is activated in the CMS. Note: The value in the `productionStatus` field of the card contract changes from `Locked` to `Ready`. The `status` field value of the new `Plastic` object changes from `Locked` to `Active`. In the case of activation of the renewed card, the old card plastic will get the value `Closed` in the `status` field.
5. The API returns HTTP `204`.
6. The server sends the response to the mobile application or e-banking service.
7. The mobile application or e-banking service notifies the cardholder that the physical card has been activated and is ready for use. Tip: The virtual card is active upon creation by default. This can be changed during onboarding configuration. Refer to [Sandbox testing](https://developer.mastercard.com/mastercard-processing-core/documentation/sandbox-testing/card-lifecycle-management/activate-card/index.md) for information on how to execute the use case in the Sandbox environment.

## Endpoint {#endpoint}


API Reference: `PUT /cards/{card_contract_id}/active`