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 Using a third party invoice provider? | Event Espresso - Staging Server
We want our users to pay mainly using Paypal, but there are situations in which we’ll need to perform an offline registration (cash or credit card). In which case we’ll need to have an invoice sent to their email address (a digitally signed one, using a 3rd party service provider).
Is there a possibility to have the offline payment gateways to actually produce an invoice using the service provider’s API?
I’m not necessarily referring to an out of the box solution, but checking if it is possible, even at an additional cost.
Is it possible? Probably. It would depend on the setup of the third party service.Event Espresso doesn’t actually send an invoice to the attendees, it provides a link to the site where it is dynamically generated and the attendee can print or download it, or just show it on their phone/tablet.
I would say a good developer could modify the gateway to send the invoice but it would either have to be as a separate email or if the invoice provider stores the files, you could add a link to it. Like I say its difficult to advise without knowing the third party system.
The support post ‘Using a third party invoice provider?’ 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.