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.
- Transfer a copy of the card to another customer. Duplicate the token, then transfer ownership of the new token to the other PCI Booking customer. You keep the original. See Duplicate, Then Transfer.
- Store the card under a new reference, property or region. The new token takes the
ref,merchantandlocvalues 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.
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. 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 for the policy levels and how to plan them.What Is Copied
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. Otherwise both tokens stay in your account and both incur storage fees. See Delete Tokens.Next Steps
Duplicate Token API
Parameters and code samples
CVV Capture Form
Have the cardholder enter the CVV
CVV Retention Policy
Set how long the CVV is kept
Delete Tokens
Remove tokens you no longer need

