|
Chris Eklund
|
December 30, 2015 at 5:49 pm
Hi,
We’re using EE4 Premium and need to add 3 new payment methods for our client. These methods work similar to the Invoice Payment Method since no currency is exchanged but, the registrant will need to provide additional information if they select one of them (account number, sale persons’s name and purchase order).
We successfully created one using the examples provided here: http://developer.eventespresso.com/docs/ee4-payment-method-development/
However, when you use the generate_new_billing_form method, you can only add additional fields after the standard billing form fields (name, address….)
All we want to show is the 2 additional fields since they’ve already entered that information on the previous screen (I know it’s pre-filled but a significant visual load to process and completely unneeded.)
Is there a cleaner way to only collect the form fields we need for these new Payment Methods?
Thanks!
Chris
|
|
Lorenzo Orlando Caum
|
December 31, 2015 at 7:25 am
Hi Chris,
The reason why they are pre-filled and shown is because the registrant may not necessarily be the person that is paying for the registration.
For example, the billing or hr department may be paying for an employee registration to a conference.
Authorizenet AIM which is part of Event Espresso 4 core has an option to exclude fields from the billing form. You could take a look at the sample coding there to see how its setup.
If you get stuck, then please create an issue on our core project on GitHub and a developer will follow up with you:
https://github.com/eventespresso/event-espresso-core/issues/new
—
Lorenzo
|
|
Chris Eklund
|
December 31, 2015 at 9:31 am
Thank you, Lorenzo! We were solving for contact/billing info using Reg Form questions. Now it makes sense for us to use our own payment gateway.
Now, we have to solve for having the payment related emails sent to the billing email entered and the registration emails go to the primary reg and attendees. Anyone done this? I see the billing info is stored as serialized data in the Post Meta table. I suppose we could pull that using the get_post_meta method but could we get those into a shortcode for the message templates?
|
