#cmarston1500 - radar
1 messages · Page 1 of 1 (latest)
OK thanks. We are moving to Connect Express. We are told we need to re-create all the Stripe services again other than sign up and KYC, yet there seem to be no API's for half the services.
if you're using Express, then you should be using destination charges, and there's no need to set radar rules on the connected accounts if you're using destination charges. Destination charges occur on the platform and would use the radar rules set on the platform
How do we allow merchants to setup exception rules when there is no access to the Stripe dash baord?
Is there a team at Stripe we can speak to for integrations. Our Stripe architect tells us we need to recreate all of Stripes products again from scratch. It seem crazy we can't use Stripes tools and dashboards given we are a secure card capture service for MOTO.
Can you share your account id so that I can take a closer look at how your integration works? You can find your account id by logging in to https://dashboard.stripe.com/settings/account. It'll be in the upper right hand corner and looks like acct_123
acct_18vkMLIKG4ViPe3d
is there a reason why you intend to switch to Express accounts?
Yes we need to maintain the Stripe charge rates and still make money. The only option we had was to become a Stripe connect Express partner so we could set the rates from IN ++. However the way Connect Express works is limiting us because we have other Stripe Connect Express partners who also want to use our secure payment service for Stripe.
We are happy we can make that commercial part work now, but we are really struggling with the gap between a platform service and Connect Express in terms of the merchants use of Stripe. Our customers are Stripe customers already in most cases.
If you're using Radar with Express and direct charges, it's not going to work at all. You cannot set Radar rules on an Express/Custom connected account.
I don't have full context on the discussion so i would really recommend you reach out to your Stripe contact to continue this discussion.
Suppose the platform account has set up the 3 radar rules for three different connected accounts.
But we want connected1 only to use radar rule 1., connected2 can only to use radar rule 2 and so on.
Do we have to manage this or stripe is providing some feature to handle this.
to clarify, are you using direct or destination charges first?
OK I start my day on week 6 of that discussion then. And so the circle continues.
checking your account, you're using direct charges
so what i said still applies -It's not going to work because you cannot set Radar rules on an Express/Custom connected account.
and since a direct charge occurs on the connected account, it will use the default radar rules on the connected account
Yes currently, but we have both models implemented and are moving to destination charges; if we ever get this scope agreed. So far we have the onboarding working, we have payment processing working, we are working on pay outs at the moment and then we are onto dashboarding and fraud management.
We ae already being asked by customers how they collect a payment for a product stored in Stripe Connect Standard, but the issue will be they won't even be able to use that service any more when we transition to Stripe Connect Express.
it sounds like there're a lot of decisions that need to be made, and it's probably best to continue the discussion with the team that has full context on this. Sorry that I can't be of more help here.