#mo223-radar-connect

1 messages ยท Page 1 of 1 (latest)

zinc pike
#

Hi ๐Ÿ‘‹ thank you for providing those request IDs, taking a look at them now.

lost sundial
#

hi, ok thanks!

zinc pike
#

Going to talk out loud a bit while I get a feel for your layout. Please let me know if I say anything that doesn't sound.

#

So the latter request you referenced (req_qgJDihb0JEfVRz) was made for and by a Standard account that appears to be a platform account. And the block cvc rule is explicitly configured on that account.

lost sundial
#

not quite, the first request (req_m1n1BFaisv8aBK) was made for a standard account . the second request (req_qgJDihb0JEfVRz) was made for a custom account

#

we have the block cvc rule configured on both (standard and custom) accounts

#

although for the standard account, it is configured on our platform account and the charge was made to one of the connected accounts

zinc pike
#

For req_qgJDihb0JEfVRz it looks like the request was made directly by the account (ending in q9o) and that that account is a standard account. I'm not seeing any evidence that a stripe-account parameter/header was provided.

lost sundial
#

๐Ÿ˜• hmm i just double checked and confirmed that account ending in q90 is our custom connect platform account. we only pass the stripe_account param for our standard connect requests.

zinc pike
#

Oohh, okay so that was a request made by a platform for itself?

lost sundial
#

yep!

zinc pike
#

Gotcha, and the other request is for a different platform and its connected account?

#

And the block rule is set up on that platform but on the connected account.

lost sundial
#

yes - block rule is set up on the platform, not the connected account

zinc pike
#

Perfect, thanks for bearing with me through that.

lost sundial
#

np! thanks for confirming

zinc pike
#

My initial thought is that since the validation is happening on the connected account, that the rule would need to be there in order to apply but am digging looking for confirmation on that.

#

Yeah, based on what I'm finding it looks like connected accounts will not inherit rules from their platform. So if validations/payments are happening directly on the connected account, then the rule will also have to have been configured on the connected account for it to apply.

lost sundial
#

gotcha, thanks for explaining that! could you point me to any documentation about how connected account owners can update their radar rules? i'm not seeing radar in the list of available products on my test connected account

short oyster
#

catching up here one sec

#

the Standard accounts have to do that on their end