Posted: December 1, 2020 at 7:37 pm
Hi, just wondering if anything has changed with regards to this – I saw in one of the forums that you guys are working on this but that was a few years ago. Is there a way to create a recurring payment for an online group? We need to have a page for an online group that expires after 12 months and charges their credit card at that time.
If not, do you have any recommendations as to how to do this? If I were to install a membership plugin on this same website, would it conflict with Event Espresso?
Currently, nothing has changed with regards to recurring payments within Event Espresso so unfortunately, we don’t support recurring payments at this.
However, it does sound like a membership plugin may work better for you here and no, using a membership plugin should not conflict with Event Espresso. I should note that EE does not ‘integrate’ with any membership plugins, they can be used together and work just fine but EE doesn’t have any functions specific to specific membership plugins. So as an example registering onto an event will not set a user up through the membership plugin.
Can you add some details of your use case here? (You can mark the reply private if preferred) I may be able to give more specific pointers if I know how you want this to work a little more.
Do users then log into the site as part of the ‘group’?
If so then yes, I would likely use a membership plugin, there are other options (not within Event Espresso) but if users log into the site already it sounds like a membership plugin may be the easiest to set up.
Events would be totally separate to the membership (although you can then restrict tickets to specific member types if needed) but the subscription could be handled/managed through their member account.
I generally don’t give recommendations for specific plugins as each has their own feature set but to list a few you can look into:
Or check an article such as https://kinsta.com/blog/wordpress-membership-plugins/
They do all of their meetings and stuff on Zoom, so we don’t necessarily need a membership site. We mainly need the recurring payments. I have used membership plugins before but we’d like to keep it as simple as possible.
We are dealing with a separate problem, though, which is that some of our events have a country limitation because of business agreements (set in the country limits within EE) and aren’t taxed, and other events need to be taxed within Canada only, so we currently have a rather unsophisticated method of showing a different price for every province in Canada with the taxes added (like this example) which we don’t really want to use for the long run. So we’re trying to sort that out as well but I don’t think we’ve gotten an answer on that yet. That’s why we were thinking we could possibly put a membership plugin on there too and move the ones that need to be taxed over to that plugin for payment.
If there was a way that we could do all of this within EE that would be great. Do you know if we could hire a developer at EE to help us with this code? We’d need a payment method that limits certain countries for one set of events (no tax) and another payment method that allows us to collect taxes for Canada only.
Thanks so much for your help.
Problem is you also need a method of managing those recurring payments, EE doesn’t support any form of recurring payment currently so whatever you do use for it will need to be able to manage those. Membership plugins do all of that and more, so you’ll likely find that trying to work around this using something else actually complicates this more than using a membership plugin.
Unfortunately, we don’t have the capacity to take on custom development right now. I’ll double-check this to confirm but as far as I am aware we aren’t taking on any custom development at this time.
There’s actually a fair bit more to this as the payment methods are the last point of call for the transaction, most need you to have set up all taxes etc prior to sending the details over to them. Some do support calculating taxes on their end etc but that also needs to be taken into account within the payment method itself. So to do this isn’t as simple as allowing specific payment methods as far as I can tell.
Josh created a snippet to add taxes based on the selected location in the registration form HERE which I believe I’ve sent over before, however, to use it requires you to collect the address information on your registration form.
Does that snippet not work for you?
“Josh created a snippet to add taxes based on the selected location in the registration form HERE which I believe I’ve sent over before, however, to use it requires you to collect the address information on your registration form.”
I am aware of that snippet but we’ve got the address question turned off so that first method will limit the countries available in the dropdown menu. Maybe I misunderstood, but I thought we had to have the address question turned off to make that work. And the Canadian taxes snippet would rely on having the address question turned on, no? Is it possible to limit the snippet to just work with one payment method and not the other, so we could have the address question off for the country-limiting payment method and have it on for the Canadian taxes method?
Also, another quick question. If we do decide to implement a membership site, I should develop it on a staging site on my localhost. Would the EE plugin still work on a copy of the site or would we need a second license while making these changes?
Yes, that snippet requires the address questions to be on to work.
So you’re still using my snippet here:
Or another? (I remember Josh provided a different method for this, are you still using that?)
My snippet was intended to allow you to control the active countries shown on the Stripe payment method easier as you asked for a way to add/remove countries from it and at the time doing so with the EE admin worked fine. It sounds like that is no longer a good fit for you as you need the ability to allow worldwide registrations, apply taxes based on location (without using tickets) and limit payment methods based on location. All of that can’t be done when managing everything through the EE countries admin.
What I think would now be a better solution is to switch the snippet to force the ‘limited’ Stripe payment method to load only specific countries via code (which does mean you would need to update the code if you wanted to change the countries loaded) and use the country field as normal on the registration form, which then allows you to use Joshes tax snippet.
If you mean the Canataxes snippet, then no, as it doesn’t apply to the payment method, it applies to the Registration Form as that is when the tax ‘surcharges’ need to be added (before the payment options/payment methods load).
Your support license is used to provide support and one-click updates for a single site, it does not limit Event Espresso functionality in any other way. So for your development/staging site, you can load Event Espresso without any key set and it will work as is, it won’t do one-click updates but you can update manually there.
Now, I said we only provide support for a single site with a license and that is true but we are also aware that users may need to develop/test on a another site and may need help with issues on that site, so we do help but use our own judgment on whether or not the site should have another license.
In short, if you send requests for multiple sites that aren’t linked to a license key we’ll require a license key those sites before we’ll provide support. If its obviously a development site for the current license site we’ll help as best we can as ultimately that going to be the licensed site after new development/test etc.
It sounds like it would be possible to use your snippet (which I am not currently using because it was limiting the countries without it). I’d need to know where and how to edit that code to include just the countries we can sell to. I’d be happy to use that method, IF we can turn the address question back on for the other payment method to deal with the taxes. I was under the impression that if the address question was off, it was off for everything. It that worked, it would solve most of our problems.
However, some of our courses require taxes and some don’t, even for the Canadians, so if it will apply taxes to Canadians across the board, it probably won’t work so I’d need a way to turn the tax thing off on the one that is limiting countries. Unless I could apply it to a specific payment method only, which it doesn’t sound like I can.
Then we could add the membership plugin to deal with the recurring payments issue at our leisure.
If it’s possible and is a simple fix, we would try that.
The support post ‘Recurring payments’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.