Answer
“CVV test tokenization v6” is not a public payment standard. It is a versioned sandbox term used by a payment processor or gateway. The token replaces a test card number. The CVV is a separate test value. No token holds the CVV. Version 6 is vendor specific. Check the processor sandbox docs for the exact token request format.
What a test token does
A test token is a placeholder for a test card number. It maps to a sandbox card record. The processor controls the mapping. A token can pass through an order flow without exposing the test card number to every system. Test tokens work only in sandbox mode. They do not authorize live payments.
CVV Test Tokenization v8: What It Covers and How to Test
CVV in a tokenization flow
CVV is verification data. PCI DSS rules bar storage of the CVV after authorization. Tokenization does not change that rule. A test CVV is a fixed sandbox value from the processor. Send the test CVV in the authorization request. Do not put the CVV in a token, a database column, or a log line.
Version 6 checks
- Confirm the token endpoint and API version in the processor sandbox docs.
- Use test card numbers and test CVV values from the processor.
- Check that the token response has a token ID, card brand, and expiry data.
- Confirm the CVV field is absent from stored token records.
- Run a decline test and a success test with separate test cards.
- Check idempotency keys for retry cases.
Limits
The public record does not define “v6” as a common tokenization version. EMVCo publishes a payment tokenisation spec. Card networks publish tokenization guides. Processor sandbox versions can differ from both. Treat “v6” as a local label until the processor docs confirm it.
CVV Test Tokenization v5: Sandbox Token Guide
Do not use live card data in a test tokenization flow. Use sandbox credentials. Keep test CVV values out of logs. Rotate sandbox keys on a set schedule.