We have a ticket type for our events that allow someone to simply pay at the door. I am using the “check” payment option for that and simply use a button that says “Pay at Door” The issue I am having is that if someone chooses that option and gets through a registration, they are then able to click to view the “invoice”. Our invoice has information on it such as the mailing address that is not appropriate and is actually confusing our pay at the door attendees. So my question is if there is a way to display a different “invoice” if their payment type is check rather than Invoice? Or is there a better way to manage these pay at the door tickets so the invoice can not be displayed showing them the incorrect information?
To be clear, it is confusing because we only use the “invoice” option for one event a year and for that event the purchaser must send a check to an address different than our organization. So the address and payment instruction would be different for that event than any of the others we put on throughout the year. We need to keep that address for the invoice option, but use our standard organization address for all other events if they view the invoice.
Josh, following ticket selection and then collection of the registration information, the system shows a “Thank you” page which gives the option to “View Full Order Confirmation Receipt”.If the user clicks that, they see a copy of the invoice language which shows the address which is only on the “invoice” settings as far as I can tell.
You can go to Event Espresso > Messages > Default Message Templates, then go to edit the Receipt template. There you can edit the information included within the receipt and remove any links to download an invoice as well.
Viewing 4 reply threads
The support post ‘Collect Payment at Door’ 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.
Support forum for Event Espresso 3 and Event Espresso 4.