mubashar-connect | Stripe Developers | Page 1

sly phoenix Jan 31, 2022, 10:28 AM

#

Hi! Could you share a bit more information about your current implementation? For example:

Are you doing direct charges, destination charges, or separate charges and transfers https://stripe.com/docs/connect/charges
The payments that fail are done on-sessions (with customers on your website) or off-session (customers not on your website)?

#

Also, could you share the ID of a failed PaymentIntent (pi_xxx)

mighty dew Jan 31, 2022, 12:48 PM

#

Hey Soma,
1- I'm not sure but I believe we are doing direct charges.
2- These are off-session.
3- Account ID: acct_1HGssBGNWtoZCM79
Payment Intent: pi_3KExMVGNWtoZCM790pVTihWw

eternal condor Jan 31, 2022, 12:50 PM

#

so what's the issue exactly? That the payment required 3D Secure? That is normal and can happen and you handle it by asking the customer to come back and authenticate. (https://stripe.com/docs/payments/save-and-reuse-cards-only?platform=web#web-create-payment-intent-off-session)

#

you do a SetupIntent on the platform and then do https://stripe.com/docs/connect/cloning-customers-across-accounts to clone the card to the connected account right?

mighty dew Jan 31, 2022, 12:52 PM

#

yes

#

exactly

#

While doing so we are facing authentication failed at the time of PaymentIntent creation. The reason is while creating SetupIntent authentication is not required in US but while creating PaymenIntent authentication is require d in EU.

eternal condor Jan 31, 2022, 12:54 PM

#

then yeah, you're not going to get any exemptions from 3D Secure that way, since the merchant setting up the card is your US account and the one charging it is the SE merchant, so from the bank's perspective it's two separate things and it's quite expected they will ask for 3D Secure since it's a legal requirement.

Options are

don't do the SI + cloning thing, just create everything on the connected account
pass on_behalf_of to the SetupIntent on the platform https://stripe.com/docs/api/setup_intents/create#create_setup_intent-on_behalf_of which is the closest answer to your original questions
handle the outcome and get the customer to authenticate when this happens, per my link above(you need this anyway since you can't guarantee never needing 3DS)

mighty dew Jan 31, 2022, 12:57 PM

#

The reason we can't create a setup intent using merchant account is Locally is a marketplace and we are authenticating card for customer's complete order which could contain items from multiple merchants.

#

If we will create SI for each merchant we need to get authorization exactly the number of items we have in cart which is not a good approach.

#

That is why we created a SI once and cloned PM to create multiple PIs.

Is there any option to mention location while creating SI?

eternal condor Jan 31, 2022, 1:02 PM

#

my second bullet point(on_behalf_of) is how you make it so the SetupIntent runs on the same merchant the payment will run on so you have the best chance for 3D Secure exemptions.

#

but if you have a multi-basket approach where you don't know where on which specific Stripe account you're going to charge the card then this is just how it is! The other way to avoid it is to not do Direct Charges at all, just do the complete payment once, on your platform account, and then transfer funds to the individual accounts(https://stripe.com/docs/connect/charges-transfers) but that is a different integration path.

mighty dew Jan 31, 2022, 1:06 PM

#

Charge Transfer sounds interesting. Let me go through it.

eternal condor Jan 31, 2022, 1:08 PM

#

note your platform is then liable for refunds and chargebacks etc

fallow badge Jan 31, 2022, 1:37 PM

#

Hey taking over from @eternal condor – let me know if there's any specific questions I can answer

#mubashar-connect