> ## Documentation Index
> Fetch the complete documentation index at: https://developers.pcibooking.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Duplicate a Token

> Create a new token from a card you already hold, optionally adding a CVV. Covers when to duplicate, the CVV, the CVV retention policy and cleaning up the original token.

Duplicating a token creates a new token from a card you already hold. The card number, expiration date and cardholder name are copied to the new token. The original token stays unchanged.

Duplicating is a tokenization: the new token is a separate card record, and it is billed and stored like any other token. Until you delete one of them, you pay storage for both.

## When to Use It

* **Add a CVV to a card you already hold.** For example, the card was tokenized without a CVV, or its CVV was cleared by the retention policy.
* **Replace a token whose CVV retention policy is wrong.** A policy cannot be changed once it applies to a token. Duplicate the token with the CVV, set the policy you want on the new token, then delete the old one. See [CVV Retention Policy](/capture-cards/cvv-retention-policy).
* **Transfer a copy of the card to another customer.** Duplicate the token, then [transfer ownership](/api-reference/manage-tokens/transfer-ownership) of the new token to the other PCI Booking customer. You keep the original. See [Duplicate, Then Transfer](/concepts/working-with-third-parties#duplicate-then-transfer).
* **Store the card under a new reference, property or region.** The new token takes the `ref`, `merchant` and `loc` values from your request.

## The CVV

The CVV is optional.

* **With a CVV in the request**, the new token stores that CVV.
* **Without a CVV**, the new token has no CVV. The original token's CVV is never copied, even if it still has one.

If you need the CVV but do not have it, ask the cardholder to enter it. The [CVV Capture Form](/capture-cards/cvv-capture) and the [Card By Link CVV-only capture](/capture-cards/card-by-link#cvv-only-capture) do exactly the same thing as Duplicate Token with a CVV: they create a new token with the card details of the original plus the CVV the cardholder entered. Choose by who has the CVV:

| Who has the CVV | Use |
| - | - |
| Your system | [Duplicate Token](/api-reference/manage-tokens/duplicate-token) with the `cvv` parameter |
| The cardholder, on your page | [CVV Capture Form](/capture-cards/cvv-capture) |
| The cardholder, by email or SMS | [Card By Link CVV-only capture](/capture-cards/card-by-link#cvv-only-capture) |

## CVV Retention Policy

When the new token stores a CVV, the same rules apply as for any newly stored CVV. You have 60 minutes to set a per-token policy with [Set CVV Retention Policy](/api-reference/manage-tokens/set-cvv-retention-policy). If you do not set one, your account-wide default applies, or the system default if your account has none.

The new token does not inherit the original token's policy. See [CVV Retention Policy](/capture-cards/cvv-retention-policy) for the policy levels and how to plan them.

## What Is Copied

| Data | On the new token |
| - | - |
| Card number, expiration date, cardholder name | Copied from the original |
| CVV | Only the CVV you send in the request |
| CVV retention policy | Set for the new token, not copied |
| Creator reference (`ref`) | Only the value you send in the request |
| Property association (`merchant`) | Only the value you send in the request |
| Third-party permissions | Not copied |
| 3D Secure authentication data | Not copied |
| Storage region (`loc`) | The value you send, otherwise the original token's region |

You become the owner of the new token. This also applies when you duplicate a token that another customer owns and has shared with you.

## Delete the Original

When you no longer need the original token, delete it with [Delete Token](/api-reference/manage-tokens/delete-token). Otherwise both tokens stay in your account and both incur storage fees. See [Delete Tokens](/manage-tokens/delete-tokens).

## Next Steps

> **[Duplicate Token API](/api-reference/manage-tokens/duplicate-token)**
>
> Parameters and code samples

> **[CVV Capture Form](/capture-cards/cvv-capture)**
>
> Have the cardholder enter the CVV

> **[CVV Retention Policy](/capture-cards/cvv-retention-policy)**
>
> Set how long the CVV is kept

> **[Delete Tokens](/manage-tokens/delete-tokens)**
>
> Remove tokens you no longer need


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.