Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Partial Payment for EE4? | Event Espresso - Staging Server
I’m looking into setting up EE for swim lessons. One feature we’d very much like is the ability to take downpayments online to hold people’s spot in the class and allow them to pay the remainder in person or online later.
EE4’s codebase is pretty well entirely different than EE3’s with respect to what you want to do.
Our current development branch of EE4.3 supports entering partial payments from the admin and then allowing registrants to pay the rest online using any of the supported payment methods. Maybe we could get you involved in BETA-testing that to get it released sooner?
I assume however, that you want registrants to themselves to make the initial partial payment online, and then another payment for the rest. That would mostly require changes to the single page checkout module. However I’m less familiar with that part of the code and can’t give you much instructions on where/what/how to change things in there. Another developer will need to comment on that.
I’d be interested in testing if possible. Partial Payments (Deposits) are a BIG feature of all transactions in the service sector, folks just don’t always want or are able to make one-off payment when the costs are in £££’s…! People need to be able to make a deposit.
Registrants would need to be able to make all the payments though, I can’t see why the payee would make a payment on the registrants behalf..?
At the moment I am using EE 4.2
Viewing 5 reply threads
The support post ‘Partial Payment for EE4?’ 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.