#heka6
zealous dawn
wheat oracle
Hi 👋 yes, that is a possiblity, if the pm_A is created and is not set up on the Platform account, then 3DS challenges could be encountered when processing a payment from the Platform account using cus_A/pm_A.
When creating pm_A on the Platform account, if you want to later process payments using that payment method then you can use a Setup Intent to collect those details. When doing so we will try to optimize the saved payment method for future payments.
https://stripe.com/docs/payments/save-and-reuse
So I would recommend trying the following flow:
- Create customer on platform cus_A
- Save payment method on the platform using a Setup Intent pm_A
- Clone both to the Connected Account
- Process an off_session Direct Charge on the standard account
Let me know if that doesn't work as expected during your testing though.
solar wedge
Ok so the payment intent should set off_session=False,
or you meant we should do setup_future_usage="off_session",
wheat oracle
Neither
solar wedge
in the 4 steps I don't see the Setup Intent
ah
So I did not get what you meant here: Process an off_session Direct Charge on the standard account
wheat oracle
Setup Intents don't use setup_future_usage, so when leveraging the Setup Intent in step 2 to collect payment method details, you would set the usage field to off_session:
https://stripe.com/docs/api/setup_intents/create#create_setup_intent-usage
I was then thinking that when processing the Payment Intent in Step 4, you could set off_session to true since the Payment Method is already set up, but if the customer will still be on your site (therefore on session) then it should be fine to leave off_session as false.
wheat oracle
Any time!
solar wedge
When we do the setupIntent, does that trigger a 3DS
or would the 3DS only triggered for the direct charge at step 4?
wheat oracle
The Setup Intent will likely trigger a 3DS challenge.
As long as you have the setting on this page enabled:
https://dashboard.stripe.com/settings/radar