#mario-sub-questions
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- mariocto_83746, 5 days ago, 10 messages
- Yes, as long as the payment method is correctly saved for future usage you should be able to reuse it
- They would first have to make a paymetn that specifically saves the payment method. Payment made for Subscriptions do this automatically (they have
setup_future_usageset)
- Yes
Which property on code can I set when creating a subscription that can automatically charge?
Subsriptions will automatically charge by definition - there is no additional property you need to set
mario-sub-questions
Does Stripe not automatically save customers' payment information at the time of payment to be used in the future?
Let's back up because I think we're talking past each other - have you already tested out/tried subscriptions in the API? Are they not working as you expect?
it creates the subscription for the customer, but it does not charge automatically without requiring user action
Can you share an example subscription ID that's doing that?
it creates an invoice in the subscription, but I need to manually enable the option to activate automatic billing
Can you share the Subscription ID? Should be like sub_123
sub_1OOeWDGS9eyEVyBI9qFtOhn3
Okay, so the issue here is that you create the Subscription through the API, but then pivoted and used the hosted invoice page to complete payment - was that intentional? Is there a reason you're not using something like Payment Element or Checkout to colelct payment details?
We use checkout for payment, we just want to understand how to automatically renew this payment.
These are recurring payments or a single payment for a product
We don't know the best approach to doing this, whether creating a subscription or how we use payment information from a product.
At checkout we thought that payment information such as credit card was automatically saved in stripe for use in automatic renewal in the future
Yes, that's how Checkout works - it collects as many details as possible so that the Subscription can be charged for automatically in the future. But the example you gave me isn't using Checkout, it's using something else
With Checkout there may be some situations where additional actions are still needed (like sometimes bank issuers may decide to still require 3DS), but those should be exception. not the norm
the example I showed was trying to do this subscription renewal approach
but we use the stripe checkout as payment in the customer's first contact when purchasing the product, we are just trying to understand how to renew and what is the best approach after 1 year of purchasing the product.
Checkout is your best option - it can create a subscription for you that automatically charges after a year
Is there a reason you moved off it?
We still use the checkout and as a payment method there is the option of priceId in the recurrence as one of the payment types for a product.
I did a test by purchasing a product in the test environment with a single payment, not a monthly payment, and then I would like to simulate the renewal of that user, but on repeat, didn't I use the best approach? If I didn't use it, what could I do to automatically charge the recurring fee, since the user paid for a product at checkout and theoretically would have saved the payment information?
They told me to create a subscription, but this approach, as I said, is not charging automatically and requires action from the customer.
The best approach is to create Checkout Session in subscription mode - doing a single paymetn and then separately do the renewal isn't the best approach.