Replies: 1 comment
-
Yeah, you're using Stripe incorrectly I'd say. If you're charging per seat, you need to use See the Stripe docs: https://docs.stripe.com/billing/subscriptions/quantities |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Scenario:
Customer is able to subscribe additional users as they're created within a host application (adding new users to an account). The subscription is recurring and a per seat subscription. Thus, the current approach to subscribe users.
When a customer decides to cancel their plan on the host application, I'd like to execute
subscription.cancel
.However, that only cancels a single subscription. Is there a way to cancel all subscriptions without iterating over
payment_processor.subscriptions (plural)
?Conversely, for handling adding users as they are created within a host application, would you suggest incrementing the quantity instead?
Note: I'm using the Stripe processor.
There also appears to be a bug with resuming subscriptions. After syncing, the previous paused state returns
Beta Was this translation helpful? Give feedback.
All reactions