Posted: February 21, 2016 at 1:51 pm
|
Hello, I possible workaround could be to give the opportunity to my client to pay only with paypal. The problem is that I cannot specify the payment method per event. It’s only a global configuration. Any suggestion to workaround? |
|
I tested paypal too. Again another approval email arrives. The problem is that the email don’t verify if the booking is already approved. |
Hi Antonio, If you are using the pre-approval option (default registration status of not approved), then a registrant won’t be able to pay for their registration until you have set their status to registration pending payment. You don’t want to move from not approved to approved directly as payment would not be required here. — |
|
|
Hi Lorenzo, My data flow start from a pre-approval going to approval (in order to reserve the seat). If I set pending payment, then all registrant are required to issue a payment. Could be useful as feature to give the opportunity to make a payment regardless the registration status. |
The reason for this is you are using the Registration Approved message for something it was not expected to be used for. The Registration Approved message is sent when the user applies to the event, if you are using that message to send Payment intructions you could include some text that says: ‘If you have already applied a payment please disregard this section’ {payment instructions}
Do some of your registrants not pay? If you are setting them to approved you grant them access to the event without payment.
The registration status should have no effect on the users ability to pay (unless set to Not Approved) so this should already be available. |
|
|
Hi tony, The status approved help me to reduce the number of available sits. An intermediate state that reduce available sits could help me. Thank for your help |
If you are using Pre-Approval (setting the default status to Not Approved) you control the number of bookings so you can not overbook the event, as you just do not approve registrations. However there is another solution that is already built into Event Espresso. If you remove the payment information from within the Registration Approved message you can continue to set your registrations to Approved, only this time you can also use the ‘Payment Reminder’ message. You can alter this to show up as something different if you prefer but here are the steps for how this could work: Set the Default status to No Approved. When a user register you log into the admin and view the registration, at this point you would Approve the registration. After you manually Approve the registration look within the Transaction, you’ll find a ‘Send Payment Reminder’ button – http://take.ms/SMyfO Use that message to inform your users that they have the option to pay online if they prefer, the email contains a link the user can use to pay by default, but you can change the wording to inidicate that the user can either pay online using the link or pay cash on checkin, the choice is up to them. That way your users receive the registration Approved message that does not contain instructions to pay but then also another email with instructions to pay if they prefer.
We have an open ticket to discuss this, I’ll add this thread to the ticket however this is not something that will be added within the next few releases so the above is the best method for this to work currently. |
|
|
Thank for your suggestion. |
The support post ‘EE4 – Payment Method and Duplicated Messages’ 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.