#Jkas
1 messages · Page 1 of 1 (latest)
Hi there, if you are using PaymentMethods then no this won't happen.
If you are on our older Sources API, then yes this would happen: https://stripe.com/docs/api/customers/update#update_customer-source
Mostly you should be using PaymentMethods and then you should trigger the invoice payment after the PaymentMethod is updated
So, if we're using both (we are), then this is a confusing situation.
Yeah I can understand that.
I'd mostly recommend migrating completely to PaymentMethods.
No real way to "turn off" this functionality for Sources
Nor "turn on" for PaymentMethods.
You either have to account for both behaviors or migrate
Ok, I think we will have to account for both behaviors for now. Has there been any discussion around deprecating Sources? Hopefully not 🤞
Nope no plans to deprecate it
We would give you a lengthy heads up if that ever were the case
Excellent. Thank you for your help!