Yep. You can either write code for it or use Radar to block the charge by fingerprint (write a rule once in your Stripe dashboard to block cards on a blocklist, add a fingerprint to the list when you identify an abusive customer, done). This lets you block a card without ever contaminating yourself with knowledge of its number (we expose the fingerprint in a variety of places to you, like API responses or on the charge detail page in the Dashboard).
Appart from the obvious benefit of not storing the credit card yourself, I imagine if a user switch cards, the number change and we are back to the same.
