Evan

> in the context of a customer that has already vaulted payment methods Just to clarify, I'm seeing this behavior even when the customer doesn't have any vaulted payment methods.

@crookedneighbor - Thank you for the responses. In the meantime, I was testing out calling `clearSelectedPaymentMethod()` on the dropin instance and that seems to kind of reset things and display...

Here's what I did that seemed to resolve the issue. Basically instead of adding a new button to the DOM with every instance, just look for an existing button and...