If you wish to get hold of a beta copy of Event Organiser Pro 3, please get in touch here. Breaking changes Below are the details of changes made in 3.0.0 which might require third-party code to be updated in order to continue to function correctly. Minimum requirements In line with WordPress 5.2 dropping support …
What is Strong Customer Authentication Strong Customer Authentication is a new European regulation coming into effect on September 14 2019, which will require that customers authentication themselves for many online payments. This will be done by asking the customer two of the following: Something you know (e.g. PIN or password) Something you have (e.g. card …
Versions 2.1.2 and earlier incorrectly charged customers when used with a zero-decimal currency (such as the Yen). For such currencies, the customer would be charged 100 times the intended amount. This occurred because an adjustment that needs to be made for currencies with a decimal amount (e.g. the dollar and the pound, which have cents …
This is a minor bugfix update which addresses the following: Adds support for translations Adds Swedish translation Fixes a bug where the ‘book now’ button was not locked during Stripe API calls
With most payment gateways you receive payment almost immediately – and so its pointless to send an e-mail reminding users of their booking / how to pay, if they will receive another moments later thanking them for their payment. However with the ‘offline’ gateway, it could be hours or even days before their payment is …
If you have a payment gateway that you want to see supported by Event Organiser, you can request it with this form. Out of the box, Event Organiser supports PayPal and ‘offline’ as means of selling tickets. There is also the stripe extension, for accepting credit card payments on your site (without sending them to …
The 1.5 update added the filter eventorganiser_booking_form_gateways, this allows you to filter the gateways that appear on the booking form (and also to do so by event). Lets suppose you have multiple events and want to accept offline payments on some, and PayPal on others. You can do that from 1.5 with a bit of …
Gateway settings (merchant account details etc) must be the same across all events – but it is possible to restrict which gateways appear on which events – for instance to allow PayPal purchases only on some events To do this we use the eventorganiser_enabled_gateways hook, which filters the enabled gateways. Step 1: Specify which gateways …
As mentioned in this article on enabling auto-redirect, setting the return url [in PayPal accounts] will not affect the url they are redirected too as the plug-in specifies the return url when it sends the user to the gateway. By default users are returned to the booking page with a thank you noticed displayed at …
By default auto-return is disabled in your PayPal account: when a user completes their purchase they remain on the PayPal site, and presented with a link back to your bookings page (which will display a thank you notice) – but they are not automatically redirected. Event if users do no return to your site, the …