#Bernard Paulet

1 messages · Page 1 of 1 (latest)

sullen orioleBOT
twilit iron
#

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 ?

cloud merlin
#

Ah... ok...

#

No...

#

I am using flutter with the flutter_stripe package and I use a payment sheet

twilit iron
#

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

#

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.

cloud merlin
#

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.

twilit iron
#

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

cloud merlin
#

OK ! 🙂
Thanks a lot for your help !