Jangus

[wind mantle]

Hi. Can you share a subscription id where you're seeing this behavior still?

[young gyro]

Here's the most recent with the change applied: sub_1MFk7UCdDL2ItXJ9zeXWlk5d

[wind mantle]

There's no failed payments on that sub though

And I see the payment method was successfully set as the default

[young gyro]

Really?!

To clarify, this is a test sub that I ran through right after making the change that Support suggested.

Here's a failing sub: sub_1M4WNdCdDL2ItXJ9schFkGqv

How do you see that the payment was set as default? I've been looking for the little "Default" tag on the payment method and I don't see it on that customer

[wind mantle]

That's because it's not set on the customer level it's set on the subscription level. Customer level payment method defaults are another concept. So you can see that it's the default if you retrieve the subscription with the api. It will be here: https://stripe.com/docs/api/subscriptions/object#subscription_object-default_payment_method

That takes precendence over the customer's

Recommend reading that description

[young gyro]

Ooo, I think I see the difference.

On the new subscriptions (post-change), it says "Billing Method: Charge specific payment method" whereas on the old subscriptions, it says: "Charge default payment method".

[wind mantle]

Yeah it can be a bit confusing. But for default PM's we prioritize the one set on the subscription, customer default is second to that

And if you don't set a default at all, you'll see failed payments like you did intitially

[young gyro]

Awesome. This helps a ton. Thank you so much for the help.