#digitaltiger_docs
1 messages ¡ Page 1 of 1 (latest)
đ 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/1384431655103631464
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi!
Can I reuse a Stripe PaymentMethodId, initially created through Checkout in subscription mode, for payments unrelated to subscriptions?
Yes you can
possible to stop using Stripe's built-in subscription system (canceling all existing subscriptions) and manually manage recurring payments later through PaymentIntentService using the existing user PaymentMethodIds.
Can you explain more about what you intend to do here?
So it will act in the same way as if I would use setup intent, no limitations?
What do you mean by this?
I want to start with using Stripe Subscriptions, initially utilizing Checkout in Subscriptions mode. If later my requirements change, I may need to cancel all Stripe Subscriptions, create custom forms, write my own background job and do my own subscription management system. To charge user with my own logic, I am planning to utilize PaymentIntentService to create payment intents. My concern right now is that if user used Checkout in Subscriptions mode, which saved his PaymentMethod, it may have some limitations for future use that will affect use it in non Stripe Subscriptions context when I try to charge it with PaymentIntentService
Is the question if you can use the customer's payment method once you cancel the Subscription?
The question if I can use customer's payment method, created in Checkout in Subscription mode in non Stripe Subscription context. Is there a limitation that PaymentMethod created during checkout can be used ONLY for Stripe Subscriptions
No there isn't such a limitation.
However, you need to take note of India: https://docs.stripe.com/india-recurring-payments
Thanks! That means Checkout in Subscription mode creates PaymentMethod for future use that can be used for any type of charges (not only Stripe Subscriptions) even if Stripe Subscriptions cancelled, thus user will not notice if I switch off to my custom background job + Stripe PaymentIntentService
thus user will not notice if I switch off to my custom background job + Stripe PaymentIntentService
I need to confirm this.
To provide more context, we are aiming to use Stripe as well as some other local providers in future. We want to start fast that's why I though it made sense to use Stripe Subscriptions. In a year we may add few local providers thus utilizing Stripe Subscriptions will not be beneficial for us and we may want to manage subscriptions in our system and use Stripe just to pay with PaymentIntentService. If that transition happens, I do not want users that were previously subscribed with Stripe Subscriptions to subscribe again in case I am not able to use PaymentMethods they entered during Stripe Checkout in Subscription mode.
I understand that Checkout in Setup mode attaches PaymentMethod in a way it can be used for any scenario but it's not an option for us right now in our user flow, that's why I am asking if Checkout in Subscription mode attaches PaymentMethod with some differences as Checkout in Setup mode does in context of ability for future charges
Hey! Taking over for my colleague. Let me catch up.
I do not want users that were previously subscribed with Stripe Subscriptions to subscribe again in case I am not able to use PaymentMethods they entered during Stripe Checkout in Subscription mode.
You should be able to reuse these PaymentMethods even if you decide to not proceed with Stripe Subscriptions..