#WedFoo
cursive solstice
naive mortar
There's a couple of different ways to do that:
- You can do this with a custom radar rule (https://stripe.com/docs/radar/rules/supported-attributes#card-info)
- You would need to create the PaymentMethod first, then inspect the PaymentMethod/check it's fingerprint and continue with payment based on that
digital quest
I am already able to retrieve this information using the PaymentMethod. However, I now want to take immediate action by creating a Radar rule if we suspect that the user is attempting to use a stolen credit card
I can't find how to do it with an api request, reading the documentation
naive mortar
You can't do that with an API request - radar rules are somethign you set through the dashboard
digital quest
I see, any other way to block the card then?
naive mortar
It would be the second way I mentioned - you keep track of the fingerprints you want to block yourself and then check them in your own code before continuing with payment
digital quest
OK, I got it, so I will create an internal database, thank you (Maybe it is a good idea to integrate this api to share stolen cards with your entire system and other stripe users).
naive mortar
Actually! I just found something that would help
We do actually have an API for managing Radar "lists" - which in your case you'd create a list of all the fingerprints you'd want to block
Completely forgot we had this - sorry about that
naive mortar
You'd create a Radar Value List (https://stripe.com/docs/api/radar/value_lists/create) with item_type: card_fingerprint and you can add additional fingerprints to that list by creating value list items (https://stripe.com/docs/api/radar/value_list_items/create).
In the dashboard you'd create a BLOCK radar rule that would reference the list you created
Here's an example of what those rules would look like: https://stripe.com/docs/radar/rules/reference#lists
digital quest
Ok, I think I understood how to proceed, thank you for your help