#Tony - collecting payment methods
fathom citrus
No inherently, no 🙂
We document a flow like this for collecting payment method details when you expect to charge a customer later: https://stripe.com/docs/payments/save-and-reuse
If you can tell me more about your use case & needs I might be able to share more detail.
warm solar
Hey, thanks for responding! I'm basically planning on rolling out a new product, and we want to start collecting card details prior to the release as a sort of waitlist. Then the plan is to add the subscription to those accounts once it's ready. I already have code for collecting payment info and creating customers and subscriptions that has been working for a year or so now. I would like to basically use the same flow, and just not add a subscription right away.
Is there a way to do it safely without the SetupIntents API? I'm asking because I'm looking to change as little code as possible in the current flow if that's an option.
warm solar
Currently, we have a payment form that hits a backend route that creates a new blank Stripe customer with the email they inputted in the form. Once their customer is created, I run stripe.PaymentMethodAttach, then I modify the customer to set that as their default payment method. Last, I create a subscription on their account with stripe.Subscription.create. I'm basically just looking to do that same thing but not add the subscription at the end.
Once the product they are looking to purchase is released, the subscription will be added to their account.
fathom citrus
Yea there's issue with that. Setup Intents would allow you to go through 3DW with the customer at the time you collect the payment details, but is not required. You can handle that 3DS authentication as part of the first payment for the subscription if you prefer.
warm solar
I think doing the authentication at the beginning would be the best. That way, they can start using the product right away vs having to go through another layer of authentication after the initial card information input.
There's no way to make them go through 3DS through my current form without using the SetupIntents API? From my understanding, 3DS is used automatically if a provider that requires it is detected
fathom citrus
Setup Intents are the recommended way of doing this, or using Checkout in setup mode if you want to simplify your integration
Note that future payments are still subject to potential authentication requirements (the bank can request this for any transactions, technically, even if authenticated previously)
warm solar
Okay, sounds good! Thank you for your time!
fathom citrus
No problem, good luck with it!