#_nerder
1 messages · Page 1 of 1 (latest)
Hello! Not really, why would you want to do that?
I want to let the customer insert the payment method and pay directly
instead of, first setup the payment method and then pay
So you want to save the payment method during a payment?
yes basically
Use setup_future_usage with the Payment Intent
ok!
But then since I'm using it with connect, it's possible to save the payment method both on the platform and the connected account?
Hmm, no. Where are you creating the PI? On the platform?
umm, not sure
the customer is purchasing a product of the connected account at the end
Ok, is it a direct charge? Destination charge?
It's a subscription creation most the time
so the customer, purchase a subscription from a product of the connected account
I want to be able to save the payment method in the PLATFORM at first payment as well so that I can reuse it in other connected accounts
Yeah from what you describe you're doing a direct charge/subscription on the connected account so all the API objects must exist on that account. If you used s_f_u that would save the payment method on the connected account and prevent cloning to other connected accounts
Your approach now of Setup Intent on the platform and then cloning it to connected accounts is the only way
Ok I see then, and actually only for cards or us_bank_account i can do the cloning
Yes
Ok then, let me recap, the experience for the customer will be the following:
- When they try to purchase anything for the first time, we prompt them with a page that asks to attach a payment method
- On that page we ask for cards or others
- If they select cards, we create the setup intent in the platform, otherwise in the connected account directly since will not be reusable
- Then they can go ahead and purchase anything
Then in the scenario in which they want to purchase something from another connected account, if we have a clonable payment method on file we use that, otherwise we prompt again the "attach a payment method" page
Is this correct?