Let customers remove saved cards alongside Braintree Drop-in: it has no built-in delete

TL;DR

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.

Steps

1. 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.

When to use

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".

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 #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