#aby_docs
silk oarBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1395453929093070894
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
velvet patrol
Hi there
rose pasture
Hi! Thanks for taking a look at our issue 🙂
velvet patrol
The easiest way to do this is to track the fingerprint of these Cards: https://docs.stripe.com/api/payment_methods/object?api-version=2025-06-30.basil#payment_method_object-card-fingerprint
Sure thing
silk oarBOT
velvet patrol
So when you detach a Card you can note the fingerprint and then you can check against that when a new card is added.
I don't think there is an easy way to do this with Radar... but let me check for a sec
rose pasture
Sure, take your time. So then we would need to wait until the customer provide a new payment method, and before attaching that card check its fingerprint to see if it has already been deatached or not. I assume this needs to be done on our end, and there
velvet patrol
Yeah the only way with Radar really would be to do a similar thing but add these fingerprints to a rule list each time but there is no API to do that.
velvet patrol
Sure, take your time. So then we would need to wait until the customer provide a...
Yep
rose pasture
there's no direct option for directly blocking it from being attached, right
rose pasture
completely understood. Thank you very much!