#Bernard Paulet
1 messages · Page 1 of 1 (latest)
yeah these docs are terrible for the most part
ignore what they say about tokens and sources, that is all legacy stuff that shouldn't be there
do you know already how to have a Customer with attached PaymentMethods pm_xxxx, like e..g using a SetupIntent or a PaymentIntent with setup_future_usage ?
Ah... ok...
No...
I am using flutter with the flutter_stripe package and I use a payment sheet
well start there, because you need to first collect the card details from the customer on your platform account and save to your Customer there
so for example https://stripe.com/docs/payments/save-and-reuse?platform=react-native&ui=payment-sheet to accept and save the card, and then after you have that working,
https://stripe.com/docs/payments/payment-methods/connect#cloning-payment-methods is the right doc to clone a saved PaymentMethod to a connected account
going to warn you, it's very likely this will all be a massive pain and possibly impossible depending on the exact flow needed(you are putting yourself at the intersection of a third party library we don't support, and a feature in Connect that is badly supported in our products and badly documented), I'm so sorry.
Thanks for the info and the warning!
I will try and see what it gives...
just one more question... what about apple pay? I think there is no change but, better to ask.
what specifically about Apple Pay? You can accept that though the PaymentSheet(if set up for it), but in terms of cloning it works the same, as it creates a PaymentMethod object pm_xxxx
OK ! 🙂
Thanks a lot for your help !