#jwerre-invoice-alternativepaymentmethod
hallow canopy
Hi 👋
You use Setup Intents to save new Payment Methods without charging them.
https://stripe.com/docs/payments/save-and-reuse
static onyx
Would that be an acceptable backup in case the default payment method expires or fails for some reason?
hallow canopy
Sure, you could try charging the other card in the case where the default fails
static onyx
With the card/source API it is automatic. Is that not the case here?
hallow canopy
What do you mean? What is automatic?
A Subscription will not automatically change what Payment Method is charged. That is something you would need to do
static onyx
The charge should be automatic. For example:
- Customer is created
- Subscription created with PamentIntent.
- Invoice collection
- Customer adds a new card (with PaymentSetup api I think)
- Invoice created (the following month) but payment fails on default card.
- Invoice collected with backup card created (step 4)
hallow canopy
You would need to handle step 6 in your integration. It's not something Stripe automates AFAIK
static onyx
This is the way it works with the Source API
hallow canopy
Unfortunately it is not a part of the Payment Methods API AFAIK. The Sources API was considered deprecated before I started with Stripe
static onyx
Let me just clarify my question. I would like a customer with a subscription to be able to add additional cards in case there default card fails. What is the best course of action here?
hallow canopy
I would use the Setup Intents API to add additional payment methods to the Customer record. i would listen to webhook events related to payment failure and respond accordingly in my code
static onyx
ok, thank you.
hallow canopy
Specifically this event: https://stripe.com/docs/api/events/types#event_types-invoice.payment_failed
It will contain the data for the Invoice and Customer
dim beaconBOT