#dooks-subscription-threshold
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.
- do0ks, 4 days ago, 17 messages
I mean its upto you on how you want to model it.
Once you set up the card for future usage then you can charge it whenever the user runs out
https://stripe.com/docs/payments/save-and-reuse
I'll have a look at that, thanks
But what if I want to create a subscription and at the same time, add the intent setup? can this be done?
What do you mean by "add the intent setup" ?
In the link you sent me: "To collect customer payment details that you can reuse later, use Checkout’s setup mode. Setup mode uses the Setup Intents API to create Payment Methods."
I want to be able to charge after the first payment when the user runs out of credits
sorry I don't follow that.
Are you trying to create a recurring payment subscription for X number of credits and charge the users one-off if they run out of them during the cycle?
dooks-subscription-threshold
Yes, that's basically it
If I am reading your ask correctly, you're looking for this
https://stripe.com/docs/billing/subscriptions/usage-based#thresholds
According to that link, I should make the flow like this:
1- Subscription creation with let's say 1000 credits (1000 threshold).
2- Every time the user performs an action in my platform they use credits, so I have to update this subscription threshold?
3- Once the user runs out of credits it will charge for another 1000 credits at the moment
4- The susbscription anchor will remain the same as long as I keep false the reset_billing_cycle_anchor