Support

December 24, 2015 at 10:06 am

Hi there,

Our Event Espresso Pro Developers are likely less responsive due to the holiday season. Please let us know if you do not hear from them in the next week.

While we trust that our Pro Developers will do a great job, we cannot dictate what they charge for their development work, and Event Espresso does not make any guarantees for their services. They are third party developers.

December 28, 2015 at 4:49 pm

Hi Cindra,

The problem is that the relatively ‘simple’ features have many hidden problems that need to be addressed in order for them to work correctly (and as expected for users) which is likely why you are receiving higher price estimates.

We’ve spent some time discussing this feature and found that unfortunately this is not something we can provide via sponsorship.

Modifying the Stripe payment method to create customers is possible however in order for it to work correctly within Event Espresso we would need to track each of the recurring payments and store those payments within the transaction, this also requires partial payments support and the ability for users to monitor/cancel the payment plan they have been added to within Stripe.

From the details previously provided it seems you are wanting to add Stripe customers to a payment plan similar to a membership to access the events, is that correct? One issue is that by simply adding Stripe customer support to the payment method there is no way to prove consent of the user to signing up to a payment plan.

If you are looking for a membership type of payment I would recommend using one of the many members plugins available, setup a recurring payment through that and you can then make your EE events free for users that have a specific capability assign to them using the WP Users Integration add-on. That add-on allows you to set tickets to only be available for users within a specific capability so you can create a free ticket only available for ‘members’ who are logged in.

This would allow the membership payments to be handled by the membership plugin and the EE events by Event Espresso.

Would that work?

December 28, 2015 at 5:21 pm

I do understand.

When a user registers for an event you want the Stripe payment method to create a Stripe customer when the payment is taken. So that when you go to Stripe -> Customers you see details of the user that just registered and can view the payment within there.

You then want to be able to add that customer to a Stripe ‘plan’ (recurring payment), you currently do this manually by adding the customer details from that same page, but to do so you also need to request the users card details again (which also implies consent from the user to sign up to a recurring payment plan), which is what you are trying to avoid.

The problem is that the recurring payment would not be a part of Event Espresso, it’s a custom additional plan with no tracking at all in that case. This would not be suitable for Sponsored development, the purpose of sponsored development is to add additional features to EE at a discounted rate as both the sponsor and other EE users benefit from the development. In this case the feature would not be suitable for sponsorship as it is a use case specific for your site (and so would fall under Custom Development for your specific use case).

December 29, 2015 at 5:24 am

Not currently.

In the case of simply adding Stripe customers that would be completely independent from Event Espresso you can use any developer familiar with Stripe. The payment method is unique to Event Espresso, but the calls to Stripe itself are the same, it would not be too difficult for a developer to work out how to create customers when making a payment with the Stripe add-on.

December 29, 2015 at 12:57 pm

18 hours sounds about right for building a complete payment method however as you have purchased our Stripe payment method add-on they may be able to use that and add in the customer functionality within the Stripe calls.

It depends on what they have been asked to do and how they would go about it. Creating a new payment method would mean the code they are working on is their own and would be easier to manage in the long run, adding functionality into an existing add-on can be a little more difficult to manage as your then working with someone else’s code.

There’s more than one way to do this so I would recommend contacting the developer for a breakdown of the costs and the reason for the chosen path.

They may also be taking into consideration the tracking of the payments made within EE that are made on the Stripe plans set on the customer, so again I would recommend a breakdown of functionality from them and check it is what you are looking for.