#k3davis-paymentmethod-attach
1 messages · Page 1 of 1 (latest)
k3davis-paymentmethod-attach
@kindred spindle I'm going to side-step the question and mostly say: don't, just use SetupIntent and that will attach the PaymentMethod for you and do the right thing
It's highly discourage to create say a card PaymentMethod and then attach it without having done a SetupIntent (or a PaymentIntent)
OK, that was my reason for asking, it seems like a "risky" option to provide a payment method id for a new customer unless it's doing the intent for you somehow.
it's not really "risky" and more that you have a problem with your integration/logic
I think I get your overall point, but can you do a setupintent for example without having a customer first? So this field looks like a shortcut, but it isn't.
Yes there are exceptions which are rare. And yes in that case you attach yourself after the fact (which is allowed because you did the SetupIntent already so in that case it is mostly just a database "linking" step)
OK. I think the api docs could be improved on this point, but thanks for the extra insight.
Yeah SetupIntent shipped after PaymentMethod Attach and setup_future_usage with the "automatic attachment" came after that
so there are a "lot of ways" to integrate
i see. well i'm doing a new integration so i'll skip some of those ways, thanks to you, lol.