#sai_rez-confirmCardSetup-confirmCardPayment-diff
1 messages · Page 1 of 1 (latest)
Whether you are confirming a SetupIntent or a PaymentIntent. SetupIntents are for saving a card without payment, PaymentIntents are for taking a payment and can save a card
Also I don't know if you saw from our thread from yesterday but I initially missed that we have a setting for subscriptions where we automatically send your customer's an email when their payment fails or they need to authenticate via 3DS https://stripe.com/docs/billing/subscriptions/overview#recurring-charges
Yea I saw that thanks
I had another question, does the payment Intent object come from an invoice or can it be retrieved another way?
Invoices do have underlying Payment Intents, but they can also be created as standalone objects (separate from Invoices)
Can they be retrieved separately from the invoice?
What do you mean? Like are you starting with a Payment Intent ID (pi_xxx) and you just want to retrieve it w/o also retrieving the invoice?
Yes, or does an existing payment intent have to be part of the invoice?
You can definitely retrieve a Payment Intent by itself - https://stripe.com/docs/api/payment_intents/retrieve
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
I'm guessing that's not possible through the client sdk?
On the client side, is it possible to update the default payment method after running confrimCardPayment?
You can also retrieve a Payment Intent client side if you have it's client secret (https://stripe.com/docs/js/payment_intents/retrieve_payment_intent)
it is not possible to update the default payment method client-side - it has to be done server-side\