#jwerre
1 messages · Page 1 of 1 (latest)
Hello! No, you should use a Setup Intent instead of directly attaching: https://stripe.com/docs/payments/setup-intents
I'm adding additional cards to existing customers though
You should still use a Setup Intent for each one.
That ensures the cards in question are set up properly for future use.
So what is the purpose of the PaymentMethod?
The Payment Method object represents a payment instrument, like a card or bank account. You still get a Payment Method at the end when you use a Setup Intent.
The Setup Intent is only used to set up a Payment Method for future use. The Setup Intent, once successfully confirmed, is not used again (the Payment Method it set up is what you use going forward).
Attaching a Payment Method directly to a Customer does not set it up for future use, which increases the chances you'll have trouble using that Payment Method in the future.
So when I'm creating a new customer with a subscription for the first time do I need to create a setupIntent, paymentIntent, or paymentMethod
No. When you create a Subscription that doesn't require an initial payment the Subscription actually creates a Setup Intent for you: https://stripe.com/docs/api/subscriptions/object#subscription_object-pending_setup_intent
No, it needs an initial payment
In that case the Subscription's first Invoice will generate a Payment Intent that should have setup_future_usage set, which performs the same setup as a Setup Intent, but with a payment: https://stripe.com/docs/api/payment_intents/object#payment_intent_object-setup_future_usage
At what point does the customer enter there CC information?
That depends on what you're building. Can you tell me more about what you're doing and what you want to make?
I have been using stripe for over a decade and I'm trying to upgrade to SCA. I typically collect CC info and retrieve a token via Stripe.js then submit that token and create a new Source, Customer and Subscription in one request.
Gotcha. Have you read through this guide? https://stripe.com/docs/billing/migration/strong-customer-authentication