#bebourdain
half canopy
quartz marsh
Hello, SetupIntents are the current recommended way to save a payment methods without a payment intent. We have this guide for that https://stripe.com/docs/payments/save-and-reuse
That guide doesn't use connect, but you can use the stripe account header to make these same calls on the connected account https://stripe.com/docs/api/connected_accounts
slender socket
Yes.
It does not advise on how to do it Directly onto a Connect Account
Is there a precise and clear document that explains this in detail.
This https://stripe.com/docs/payments/payment-methods/connect#create-payment-method and https://stripe.com/docs/payments/save-and-reuse provide conflicting information and examples.
quartz marsh
We don't have a guide specifically on that but the two docs that I sent showed how to do that together
Use the save-and-reuse doc, but include the StripeAccount header as per this API reference section https://stripe.com/docs/api/connected_accounts
slender socket
Our engineering team is reporting that it will not work.
quartz marsh
How so? I use that exact code myself and it creates a payment method on the connected account
quartz marsh
That code is for creating a payment method directly, if you use setup intents you don't need to use that code
Basically, setupintents were created to track state on the process of creating a payment method. That section of the doc basically shows an older flow for how to create payment methods. It will still work but is less flexible and doesn't support things like 3DS
slender socket
That code is for creating a payment method directly, if you use setup intents yo...
The Description is: "Creating PaymentMethods directly on the connected account" that does not mention anything about doing a PaymentIntent and the ABOVE section, "Create and attach a PaymentMethod when confirming a PaymentIntent" explains how to do it with a Payment Intent. So 1. Why even have the section "Creating PaymentMethods directly on the connected account" when the above section has "Create and attach a PaymentMethod when confirming a PaymentIntent"?
quartz marsh
Like you said, sometimes there are situations where you want to save a payment method without taking a payment
slender socket
Yes. Which is what we want.
quartz marsh
The two ways to do that now are to create the payment method with a setup intent, or create it directly
slender socket
Okay. What is the difference between the two?
To confirm, it would be something like this:
quartz marsh
Correct, transfer that line in to those calls in the second doc
slender socket
You guys have got to remove all of the outdated documentation. They cause a huge problem because on Search, they're the ones that have been used so much in the past, that the new documents which are more correct, are the last ones we see.
quartz marsh
Duly noted, I will create feedback about that. We do try to update older docs as new info becomes available
quartz marsh
Okay. What is the difference between the two?
The SetupIntent is a tool to help create payment methods here. It keeps track of the status of setting up a new payment method and it enables you to do things like settings up payment methods that require more than one step
slender socket
Yeah man, 4 times in the last 8 days outdated documentation sent us down the wrong path and we wasted 4 full engineering days. Not a great experience and is expensive