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 How to offer Purchase Order payment option to selected customers/attendees? | Event Espresso - Staging Server
Our client provides training sessions that can be booked by individuals or by a corporate rep for their staff. The client needs to be able to offer Purchase Order as a payment option ONLY for selected corporate clients, not to all attendees/applicants.
Please advise how this can be done. This is a deal breaker! All suggestions appreciated.
How are you distinguishing between the corporate clients and the rest? Is it a question on the registration form or are they logged in as site members?
Our client (they’re a Registered Training Organisation so lets call them RTO), wants to limit the Purchase Order (PO) payment option to selected corporate clients so the attendee customer will have to be an existing site member and will need to complete a form to apply/register for the option of using Purchase Order as a payment option. RTO will then approve the request.
The next part is unknown – how the attendee customer is recorded as having Purchase Order privileges. Suggestions? All welcome with thanks!
PS Thanks also for the super quick response! We’re in Australia so we don’t usually get such awesome turnaround due to time difference.
Thank you so much for your assistance and clear instructions with implementing this solution, worked like a charm.
Keep up the great work
Regards
Robbie
Viewing 6 reply threads
The support post ‘How to offer Purchase Order payment option to selected customers/attendees?’ 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.