#stephchl_radar-block-rules
boreal cometBOT
👋 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/1385033602974089249
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
golden stump
Hi 👋
The bit mentioned in the doc is a little confusing. Essentially it means that you should only use payment_intent if you want to trigger additional authentication. If you want to Block or Allow or Review, you should use charge
Since all Payment Intents create Charges (under the hood), your Block rule would still get applied even though you're using Payment Intents API
deft granite
ahhh okay that makes sense as to why the block rule works when I change it to charge, thank you for clarifying!
golden stump
Sure thing, happy to help 🙂
deft granite
As for when to use :transaction_type: = 'payment_intent', by additional authentication do you mean an Authentication Rule?
golden stump
I mean like triggering 3DS
The doc on supported attributes calls it a Request Credentials rule but if you review the available rules in the reference doc, it's labeld as Request 3D Secure
deft granite
Oooooh okay so unless I want to include an additional 3DS auth check, I wouldn't want to include :transaction_type: = 'payment_intent' in my block rule?
deft granite
Got it, I'm clear on when to use what now! I also see Request 3DS conditions under the Authentication Rule section of my radar rules dashboard so things are clicking now haha. Thank you so much!
golden stump
Great 🎉 I'm glad I was able to help 🙂