#kingrichie_best-practices
sly nymphBOT
👋 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/1217090533554520106
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
potent orbitBOT
charred grove
Hi
The guide you were referring to is very relevant yes. What issue are you facing exactly ?
opaque helm
The main issue were facing is that we want to have a catch all rule checking for MetaData we're sending across
Request 3DS if ::PurchaseType:: = 'GiftCard' , however, this doesn't appear to be working.
Secondary to this, we were hoping that a guide or best practice doc has already been made regarding recommended radar rules that are good to use for this specific use case given the fact that Gift Cards purchases are some of the highest risk when it comes to fraud.
We've also tried
Request 3DS if :statement_descriptor: = 'store name giftcard' but this doesn't appear to catch the payment either.
See we also accept payments for other types of orders which we don't wish to challenge as strictly.
frank quartz
Hi there 👋 jumping in as my teamamte needs to step away soon. My team and I in this forum are not familiar with writing custom Radar rules. I would recommend following up with our Support team on this matter if my limited insight below doesn't help you progress.
https://support.stripe.com/?contact=true
I don't see the PurchaseType attribute that you're trying to leverage as one of our available attributes, but it seems to be wrapped in double colons so I'm guessing that is metadata that you're providing to us? You may want to be looking at the card_funding attribute instead:
https://docs.stripe.com/radar/rules/supported-attributes#:~:text=particular card number.-,card_funding,-Case Insensitive String