Austin_Rowe

[pulsar fossil]

Hello 👋
When you say you create a PaymentIntent for a connected account, do you mean you're using direct charges?

[jaunty owl]

I think so, my terminology might not be 100%. If by direct charges you mean we would basically create the payment intent and pass in the stripe account id of the 3rd party seller and collect our fees only, then yes we're using direct charges

That is what direct charges are, right?

[pulsar fossil]

That's correct yes
So if you use setup_future_usage parameter for direct charges, it will create a payment method on the connected account which can be re-used later (assuming the charges that you're creating later are direct charges for this specific connected account)

[jaunty owl]

Ah I see, we have been saving the payment methods on the customer that's associated with the platform, and then at transaction time cloning them to the connected account so that the user can use the same payment method with all the 3rd party sellers. In order to follow this pattern we'll have to just have the user go through a flow that saves the payment method, then clone the pm and create the payment intent, correct?

[pulsar fossil]

In order to follow this pattern
Can you clarify which pattern exactly?

[jaunty owl]

Basically we want to save the PM as the user checks out so that they can use it for any future payments

But we use connect with direct payments, so I assume what we'll have to do is save the PM and then clone that PM for the connected account and then create the payment intent with the payment method

[unreal salmon]

Correct, with connect if you want to use a PM across multiple accounts, you need to save it to the platform and then clone it down before using.

[jaunty owl]

Ah, ok. Thanks for confirming!