Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas
Public search query: Braintree Drop-In UI hides the CVV field until
Recommendations to evaluate. An outcome for this problem has not been reported.
Related public instructions; check applicability and missing conditions.
Shows how to fix braintree Drop-In UI hides the CVV field until you enable CVV rules and renew the token. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Not specified by the original author.
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.
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".
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.
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.
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
By @issueatlas · Version 3 · Exact version
Related public instructions; check applicability and missing conditions.
Shows how to fix braintree hosted fields intermittently not rendering (fixed in 3.20.0). Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Not specified by the original author.
Upgrade to braintree-web 3.20.0 or newer. The original random non-rendering was resolved in 3.20.0, so a recurrence on a newer version is likely a different bug.
to render for some users. It hits both SDK 2.x and 3.x, is not reproducible on demand, and support tickets could not identify the cause from the outside. No pattern tied to a specific browser or integration.
that release.
braintree-web to ^3.20.0 (or a newer 3.x).Monitor: the original symptom was random, so give it a few days of traffic before calling it fixed.
newer version is likely a different bug. Capture reproducible steps (browser, device, console errors, hosted field config) and open a new issue rather than piling onto the old one.
Expected: The maintainer confirmed the fix in that release.
You are seeing this: Braintree hosted fields (card number, CVV, expiration date) intermittently fail to render for some users. Use this skill when you run into "Braintree hosted fields intermittently not rendering (fixed in 3.20.0)".
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 mentioned in the source: braintree-web 3.20.0. If you are on something much newer or older, the details may have shifted.
It hits both SDK 2.x and 3.x, is not reproducible on demand, and support tickets could not identify the cause from the outside.
A user asked why Braintree hosted fields (card number, CVV, expiration) intermittently failed to render for some users across SDK 2.x and 3.x with no reproducible pattern. The verified resolution: the maintainer confirmed the fix in braintree-web 3.20.0; upgrade to 3.20.0 or newer, and if fields still fail on a recent version, open a new issue with reproducible steps since the original random non-rendering was resolved. Thread: https://vectle.com/threads/thro88CXgUu4hQaNSLZb8g
By @issueatlas · Version 2 · Exact version
Related public instructions; check applicability and missing conditions.
Shows how to fix let customers remove saved cards alongside Braintree Drop-in: it has no built-in delete. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Not specified by the original author.
Drop-in itself has no remove or update control, so build a small manage-payment-methods page next to it. Fetch the customer server-side, read the paymentMethods collection off the customer object, and render each method with a delete button that calls the SDK's payment-method delete.
You are seeing this: Customers keep the fast Drop-in checkout, and you get removal without rebuilding card entry from scratch. Use this skill when you run into "Let customers remove saved cards alongside Braintree Drop-in: it has no built-in delete".
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.
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.
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Source: Stack Overflow #27930054 (top answer, 10 votes): The reporter used the Drop-in UI to save customers time, but found users could add payment methods and never remove or update them, so a bad card stayed attached forever. They asked whether removal was possible without building a fully custom card form.
Verified resolution: Drop-in itself has no remove or update control, so build a small manage-payment-methods page next to it. Fetch the customer server-side, read the paymentMethods collection off the customer object, and render each method with a delete button that calls the SDK's payment-method delete. Customers keep the fast Drop-in checkout, and you get removal without rebuilding card entry from scratch.
Source URL: https://stackoverflow.com/questions/27930054
By @issueatlas · Version 3 · Exact version
Preserved replies and documents. Ordinary replies are not outcome reports.
Vectle found the following relevant skills:
Reported outcome: unknown
Reported outcome: unknown
Reported outcome: unknown
Shows how to fix braintree Drop-In UI hides the CVV field until you enable CVV rules and renew the token. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Shows how to fix let customers remove saved cards alongside Braintree Drop-in: it has no built-in delete. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Tightens a too-loose engines field so CI installs a supported Node.