#manu-savingcards
1 messages · Page 1 of 1 (latest)
if you have to use on_behalf_of then there's no clean solution as far as I know!
I assume your problem is you do the setup entirely on the platform account, and then later do the payment on_behalf_of specific connected accounts, so those payments might not qualify for exemptions since from the bank's perspective the setup and payment were on different merchants. There's nothing really you can do there except either not use on_behalf_of, or just handle it robustly if 3D Secure does get required on the payment, unfortunately.
Ok, I ask you because some time ago I ask the same question to email support and they told me to create PaymentMethods on my platform and clone them to a connected account to create direct charges as explained here: https://stripe.com/docs/payments/payment-methods/connect#cloning-payment-methods
But I didn't quite understand how to proceed. Are you sure there is no way to do this?
I'm not sure really
it's really hard to answer with no context on what exactly you're building and the models involved (Direct or Destination charges, account types) and what the exact problem you are concerned about is, so I'm quite lost
ultimately, as far as I know, setup and payment have to be on the same merchant, from the bank's perspective. The merchant used depends on how you do the API request(it's your platform if you use just your API keys, it's the connected account if you use the Stripe-Account header, and it's also the connected account if you do on_behalf_of with just your API keys) so for best results you have to make them match, but there's not going to be a 100% perfect solution unfortunately for every single possible set up of a marketplace since it's the nature of how this SCA regulation implementation works
In my platform I have a different sellers, for each one I create a stripe express account.
I have also different buyer with saved payment methods. when the buyer try to pay I need to set seller as settlment merchant, and I capture my platform fee, so I guess to use destination charge.
I completely understand the bank's perspective, but because of my payment method may be already authenticated I search for a sort of workaround to avoid repetition if exist
not aware of one ! like I said, there's not going to be a perfect solution for every use case