#geekcorner_paymentmethod-new

1 messages ¡ Page 1 of 1 (latest)

scenic pulsarBOT
#

👋 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/1276603923142021222

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

tulip epoch
#

geekcorner_paymentmethod-new

#

@manic rover what we recommend is to use a SetupIntent to collect the new payment method details (such as a card). Once that's done, you can decide to delete the old one (or keep it as a backup) and if you use Subscriptions/Invoicing you can decide to make that new PaymentMethod the new default by setting invoice_settings[default_payment_method] on Customer or default_payment_method on Subscription.

We don't yet have the concept of "make that card the new default everywhere and delete the old one" because while it can be useful, it really couldn't handle edge-cases well and would only seem like a great idea early on when you never have more than one PaymentMethod

manic rover
#

which edge cases are you talking about?

tulip epoch
#

Well what if you have a special customer in the future that wants a specific back up card for a certain Subscription?
What if the new card ends up not working on the next payment?
How do you handle cases where you expand to Bank Transfers based on the amount owed and now you have more than just one card saved?
Those are just examples to drive my point where the "default behaviour" you're looking for is totally reasonable at first but doesn't always scale well and bites you later if we do the wrong "replacement". While with our current flow, it's more steps to think of but it pushes you to carefully think about what you really want to do.
Does that make sense?

manic rover
#

it indeed makes sense

tulip epoch
#

With all of that said, I wish we had a prebuilt solution even if you had to read through some "gotchas" before using it because for the 99% of cases it'd make things much easier

manic rover
#

hmmm? did I missed something in the docs?

tulip epoch
#

Not really we don't cover this today in details.

#

In a way, we recommend using the CustomerPortal as the easiest way to manage this since we offer a simple prebuilt hosted UI where the Customer can manage their payment methods (and many more features: https://docs.stripe.com/customer-management

manic rover
#

oh i thought it was some way to say that i missed something in the docs

#

yeah i checked out the customer portal but it kinda lacks the ability to disable some features and so

tulip epoch
#

like what? This product is well cared for internally so I'd love to hear feature requests/feedback because I can definitely raise those

scenic pulsarBOT