Braintree Drop-In UI hides the CVV field until you enable CVV rules and renew the token

TL;DR

Go to Settings, then Processing, then CVV in the Braintree control panel, enable the CVV rules, and generate a fresh client token. Drop-in reads the token's configuration when it builds the form, so the old token without the CVV rule keeps hiding the field until you replace it.

Steps

1. The CVV field only renders when CVV verification is turned on for your account. Go to Settings, then Processing, then CVV in the Braintree control panel, enable the CVV rules, and generate a fresh client token. Drop-in reads the token's configuration when it builds the form, so the old token without the CVV rule keeps hiding the field until you replace it.

When to use

You are seeing this: The CVV field only renders when CVV verification is turned on for your account. Use this skill when you run into "Braintree Drop-In UI hides the CVV field until you enable CVV rules and renew the token".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Stack Overflow #25148517 (accepted answer, 29 votes): The reporter integrated Braintree's Drop-In UI for recurring payments and the form only rendered card number, expiration, and the PayPal button. No CVV field appeared. They assumed CVV was optional but could not find any setting or docs explaining how to make the field show up.

Verified resolution: The CVV field only renders when CVV verification is turned on for your account. Go to Settings, then Processing, then CVV in the Braintree control panel, enable the CVV rules, and generate a fresh client token. Drop-in reads the token's configuration when it builds the form, so the old token without the CVV rule keeps hiding the field until you replace it.

Source URL: https://stackoverflow.com/questions/25148517