|
Adam Bowie
|
August 18, 2016 at 1:43 am
We process with Braintree, who does not require any address fields to accept payment. We processed $200,000 in ticket sales this way using Tribe’s WooCommerce Tickets. However we are shifting our ticketing to EE4.
Is there a way to remove these fields? I understand with some processors they are required, but not with Braintree.
Thanks for the help!
|
|
Josh
|
August 18, 2016 at 11:37 am
Hi Adam,
Great question. Someone is looking into this and we’ll get back with you when we find an answer.
|
|
Adam Bowie
|
August 19, 2016 at 3:18 pm
Great! The only restriction is that Event Espresso is requiring it. If we could remove this with a function and still have Event Espresso process the payment, it WILL clear with Braintree and work fine.
The huge advantage of this is that not requiring these fields can massively boost conversion on ticket sales, especially for visitors on mobile.
|
|
Josh
|
August 19, 2016 at 3:45 pm
I understand.
|
|
Adam Bowie
|
August 24, 2016 at 3:53 pm
Hey Josh – just checking back on this. We have an event that does $150,000 in sales and I would LOVE to use EE4 for it…but this will probably be a factor. Any updates or news?
|
|
Tony
|
August 25, 2016 at 4:35 am
Hi there,
There is a filter within EE that allows you to remove the fields from the form, however the Braintree add-on itself checks for those fields internally so we will need to push an update that will allow it.
The changes are currently under review, once tested and confirmed working we can push the update live.
|
|
Oguzhan Altun
|
August 25, 2016 at 3:27 pm
I would love to hear about this when this update is live.
|
|
Adam Bowie
|
August 25, 2016 at 6:46 pm
Awesome. This would be a great update. You think you can push this in the next 2 weeks? If so, we will wait and use Event Espresso. Thank you so much!!
|
|
Tony
|
August 26, 2016 at 6:04 am
I’d expect we can push the update to the Braintree add-on early next week and will update this thread as soon as the update is pushed.
The changes allow you remove any of the fields requested by the add-on currently and leave just the card details using a custom filter. We may also include a setting for this within the payment method itself if we find there is more demand for it but for now this allows for either option if needed.
|
