You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
From time to time, we see in our own site that a member somehow ends up at checkout to purchase the same level they currently hold.
In the case that they have the level and an active recurring subscription, this can be problematic. For one, it will charge them (without a proration Add On active) their full price again for membership the day of checkout and set up a new subscription.
This can be a way people do things like change from Credit Card to PayPal or another payment method. Or even swap PayPal accounts they are using to fund the membership.
But, it isn't always done intentionally. Let's consider whether core should show some warnings for this.
We don't get this issue too often, but when it happens it causes issues / unnecessary refunds / confusion.
Describe the solution you'd like
A popup / warning at top of checkout page: "You are about to make a duplicate payment for the same level."
A setting "Do not allow members to sign up for their same level when it is active"?
Let's keep discussing this and ideas around it. Whether its just a recipe or something we support in core.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
From time to time, we see in our own site that a member somehow ends up at checkout to purchase the same level they currently hold.
In the case that they have the level and an active recurring subscription, this can be problematic. For one, it will charge them (without a proration Add On active) their full price again for membership the day of checkout and set up a new subscription.
This can be a way people do things like change from Credit Card to PayPal or another payment method. Or even swap PayPal accounts they are using to fund the membership.
But, it isn't always done intentionally. Let's consider whether core should show some warnings for this.
We don't get this issue too often, but when it happens it causes issues / unnecessary refunds / confusion.
Describe the solution you'd like
Let's keep discussing this and ideas around it. Whether its just a recipe or something we support in core.
The text was updated successfully, but these errors were encountered: