#daniele-de-benedetto_api
last boneBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- daniele-de-benedetto_api, 1 day ago, 11 messages
- daniele-de-benedetto_api, 1 day ago, 7 messages
blazing flameBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1258005904633233410
đ Have more to share? Add details, code, screenshots, videos, etc. below.
warped cliff
hi! there's a card_bin predicate you can use in a Block rule if you know the BINs of that cards you want to block https://docs.stripe.com/radar/rules/supported-attributes#card-info
warped cliff
no
banks can have many different ranges. You'd need to find some data source to map BINs to specific issuers or banks. We don't really provide such mappings ourselves. Or only add BINs you have directly observed causing fraud in your previous payments.
We don't have a Radar rules for something like card_issuer or card_bank, it's a backlogged feature request right now.
sorry, there isn't really a good answer here
weak creek
ok clear thankyou, you know if i can insert a custom 'middleman' between the payment_intent and the charge in order to block the payment ?
warped cliff
that doesn't make a lot of sense to me.
weak creek
i'm looking for something that can expand the radar feature, making my own code that for example check the issuer or something else
warped cliff
you can for example integrate like https://docs.stripe.com/payments/finalize-payments-on-the-server where you can inspect the details of the card that's going to be used, and then decide to not process the payemnt/don't create the PaymentIntent.
weak creek
ok clear, the problem is that actually i'm using the checkout form that you provide, i imagine that for this kind of integration i need to change the component
warped cliff
what is the "the checkout form that [we] provide" , is that Checkout(the hosted page) or PaymentElement(form embedded on your site)?
weak creek
payment element form embedded
warped cliff
then you can use the flow I linked to
warped cliff
no, that one does not work.
weak creek
ok understood, i need to use the payment elements for more flexibility
warped cliff
if you use Checkout then Radar is the only way to implement a block like this. If you use Elements/PaymentElement you can use the manual flow I linked to have more control over how/if things are blocked.
weak creek
clear thank you