#r-y-a-n_api

1 messages ยท Page 1 of 1 (latest)

pale nacelleBOT
#

๐Ÿ‘‹ Welcome to your new thread!

โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

๐Ÿ”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1265360501496352881

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

obtuse vessel
#

new card ends 1000, old card ends 1009

rain barn
#

Hello
Did the subscription/invoice have its own default_payment_method?

When a card is attached, it doesn't automatically become default payment method on the customer as well as any existing subscriptions they had.

When a subscription is created, you can either charge customer's default payment method for billing OR you can provide a payment method that's attached to the customer as subscription.default_payment_method

If you're doing the latter then you'd need to update that separately by calling the Update Subscriptions API

obtuse vessel
#

So this subscription did have a specific payment method attached at creation (the old one, which worked at that time). The invoice & customer are set to use the default payment method. It seems like we should not be setting the subscription payment method, but rather leave it the default off, and that would always make any charge use the default in this scenario, correct?

rain barn
#

Yup, that would save you a separate API call to update the payment method

It also depends on your usecase though.. The customer may want to use a different payment method than what's their default to pay for the subscription..

it's all subjective ๐Ÿ™‚

obtuse vessel
#

Got it, thank you!