#golan.shay-radar-express-directcharges

1 messages · Page 1 of 1 (latest)

thick raptorBOT
north bear
#

What type of Connected Accounts, and which of our Charge structures are you using?

worldly hedge
#

I use Direct charge. What do you mean by type of connected account?

#

These are my current rules, does this cover all transactions?

image.png
north bear
#

We currently offer three types of Connected Accounts; Standard, Express, or Custom. If you're using Direct Charges, then you should be using Standard accounts.

In that case, I believe those settings are controlled by the Standard account and don't think you as the Platform have control over those.

worldly hedge
#

I've found it, the accounts are Express accounts

#

Can I force 3DS on any transactions for Express accounts?

north bear
#

You should not be using Direct Charges with Express accounts. When using Direct Charges, the settings of the account that the payment is being processed against will be used, but Express accounts don't have access to the Stripe dashboard so they can't interact with those rules settings. I believe you may still be able to adjust those settings through the Stripe dashboard for them (not entirely certain as we aren't the most well-versed in that dashboard), but you will need to manually do so for each account and it will be tedious.

It sounds like Destination Charges may be a better fit as they'll be processed based on the settings of your Platform account which you do have control over.

worldly hedge
#

I can’t use destination because of my use case, I have 3 connected accounts with high volume transactions so it’s crucial to force 3DS for them

north bear
#

Direct Charges aren't intended to be used with Express or Custom accounts, so I strongly recommend you consider changing either the charge structure that you're using or the type of Connected account's that you're leveraging.

You might be able to do what you're after by manually logging into each of your Connected Accounts from the Stripe Dashboard for your Platform, and adjusting their rule settings.

Another approach that might work, is for you to bypass Radar rules by using payment_method_options.card.request_three_d_secure:
https://stripe.com/docs/api/payment_intents/create#create_payment_intent-payment_method_options-card-request_three_d_secure
That approach is explained further here:
https://stripe.com/docs/payments/3d-secure#manual-three-ds