#shawn_api

1 messages · Page 1 of 1 (latest)

mint ospreyBOT
#

👋 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/1344019333378080779

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

hushed island
#

hi! our team doesn't work with radar a whole lot so i'm not super familiar with it. i might need to poke around a bit and check with some colleagues to confirm a few things.

mystic surge
#

Radar is severely underdeveloped imo.

#

Here is a point form of what i see are issues:

  1. It's almost given radar doesn't work on block rules for 0-dollar charges (which I think was a big mistake) based on radar rules blocking by various rules, including countries/billing address - however chargeable amounts does block correctly.
    Very dodgy decision, almost like the person making the decisions is not experienced with dealing with actual use cases.

  2. There is no API for radar -> that's usually the first thing you do in development, get your api working, as in the development process, you want to do partial and end-to-end testing, and a lot of that should use API level calls.
    It seems this was not properly developed. We can't use radar rules (single source of truth) from stripe in our own backend because we can't pull the rules via API call. We have to maintain two lists of blocking rules, one for stripe radar, and then one for post stripe additional checks on our own server due to rules being skipped for 0 dollar charges.

#

@hushed island Thanks for you help.

hushed island
#

also fyi i am bouncing between a few different threads so my response might be a little delayed. but i have not forgotten you!

mystic surge
#

Yeah, no problems.

hushed island
#

ok sorry for being a little slow on this thread - i've been looking into this and running this by a few colleagues, and unfortunately we don't support radar rule configuration on the discord server since it is (as you mentioned) a dashboard exclusive feature, and our team only supports our APIs.

#

but yes i very much agree that it's unfortunate that we don't support configuring rules via the API at the moment. i am checking around to see if that's a part of the roadmap (in part just to satify my own curiosity).

mystic surge
#

Okay, thanks. sad but understandable. hehe.

hushed island
#

but yeah, as far as your configuration question goes, would you mind if i send you a link that will guide you to filing a support ticket? that team will be better prepared to help you out with this kind of question

mystic surge
#

That would be great. Thanks.

mint ospreyBOT
#

We wish we could help, but you need to talk to Stripe support

We can only help on Discord if all of the following are true:

  • 🧑‍💻 You must be a developer
  • 🛠️ Your question must be about building a Stripe integration
  • ⚙️ Your question must be technical/developer focused
  • ⏱️ You must be available to respond in realtime
  • 👥 You must be comfortable receiving help in public (this is a public server)

If any of those aren't true please contact Stripe support.

If all of those are true we may have misunderstood your question; please provide more details below.

Note that using an inappropriate button or submitting inappropriate information is a violation of our rules. You will be removed from this server if you repeatedly create invalid threads.